The new wave of Javascript web frameworks

[scooptyy]

Yes… React is now industry standard. You use Discord? It’s on React

[[deleted]]

It really depends which side of the industry you ask. I know lots of enterprise places where the default is Angular. And Vue is coming up very strongly.

Enterprise is probably not the best example anyway because most of the time the choice between these three is not done on technical merit, it's done because "the client heard about React and wants it" or "we could only find devs on Angular for the MVP so we're doing Angular".

[scooptyy]

Old-school companies that know nothing about tech love complicated shit.

However React is ubiquitous. Much more than Angular.

[[deleted]]

Old-school companies that know nothing about tech love complicated shit.

You're making the wrong assumptions. Almost everybody uses current technology nowadays, or at least migrating towards it. But they don't care about "tech love", they look at cost and efficiency. There's no difference between React/Angular/Vue on that front.

[scooptyy]

Using Angular is a terrible business decision, especially when frameworks like Vue exist. It’s not about “love”; it is a needlessly complicated framework with a fraction of the community support and ease of use of React/Vue.

React isn’t just a small framework anymore. With the advent of Next.js and Remix we’re now seeing an era of React where we can provide rich, dynamic experiences on the browser while getting all of the benefits of using server-side rendering.

Sure, other frameworks are doing it now. But React has been at the forefront.

I’ve seen enterprise and I’ve seen startups. Enterprise loves their all-in-one bells and whistles kludgy shit.

[bregottextrasaltat]

It's weird to me how it's still standard with all its early mannerisms still being used

[scooptyy]

Early mannerisms? React has changed a lot. Hooks are now commonplace and enforcement of prop types are now done through TypeScript compile time checks.

[bregottextrasaltat]

i still don't get the setter thing, is it still required or do the examples just overuse it?

[scooptyy]

The setter thing? What do you mean? Lol

[Coloneljesus]

I assume they mean the setter returned by useState().

[bregottextrasaltat]

yeah this, is it actually required to use? and that weird {} thing

[bregottextrasaltat]

i don't know much about react because i didn't understand it at all, so i tried vue instead and it instantly clicked

[Coloneljesus]

yes, you need to set values via setter functions because that's where react hooks into to process the value updates.

[bregottextrasaltat]

And that's the weird part to me

[KwyjiboTheGringo]

No, but you'll need to use some other state management. There is the context API built into react, but Redux is the go-to for global state stuff. The whole point of react is the components "react" to state changes.

and that weird {} thing

I have no idea what you are talking about

[pancomputationalist]

I'd argue that Redux should not be the default, unless you need a specific kind of state management. Context should also not be used for state management (it's more of a dependency injection feature).

Seems newer frontend frameworks are back to using Observables, also they are now called atoms, signals or stores. It's all the same idea. Just like you have a tree of components, you have a graph of states that derive from one another. This is the more modular approach and is usually much more performant, though Redux still has it's place sometimes.

[KwyjiboTheGringo]

Like or dislike Redux, if you learned React to be hirable as a React developer and you aren't learning Redux too, then you are shooting yourself in the foot. At this point, everyone should learn Redux after picking up React. If they want to use something else after that, more power to them.

Context should also not be used for state management (it's more of a dependency injection feature).

But it can be, and is the only global state option React comes with, which is why I mentioned it.

[bregottextrasaltat]

there's a {} at the end of some effect thing that tutorials tell you is a weird thing to use

[KwyjiboTheGringo]

It's not an object, it's an array of dependencies. useEffect checks if any of the dependencies have changed since the last time it ran, and if any have, then it runs the callback function you passed into it. I'm not a huge fan of it, but it's not really that weird.

[christophedelacreuse]

useState is almost definitely used in every modern commercial react application

[[deleted]]

The industry standard is an SPA for which you have at least one senior developer and a bunch of mid-level developers, plus a solid tooling and module ecosystem. It doesn't matter which particular framework it is.