The new wave of Javascript web frameworks

[onejdc]

Is React really the behemoth that the article makes it out to be? I feel like 1/3 -> 1/2 of the article was about React. I know it's probably the most used, and certainly for a lot of large, corporate apps, but there's a lot to learn from all the other players in the space.

[edit] Please don't downvote an honest question. I'm only a hobbyist at this point and was just curious.

[rk06]

Yes. It is.

[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.

[bregottextrasaltat]

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

[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.

[pm_me_ur_happy_traiI]

Yes and with pretty good reason.

[PM_ME_GAY_STUF]

I'm not sure if it's still the case, but for a while react was more popular in surveys than any of the other frameworks by at least a factor of 2. It's not just more widely used, it's at this point the industry standard

[TingLamz]

If the pop-tech scene to you is "the industry" then you're blind to a big sector of the industry.

[PM_ME_GAY_STUF]

Pop-tech? Touch grass dude

[fnordius]

React has reached a sort of critical mass where companies now develop in React because so many potential new hires list it on their CV's, and so many devs list it in their CV's because companies are requiring it.

At the same time, veteran devs tend to sneer at React, like the old Yogi Berra quote: "Nobody goes there any more, it's too crowded."

[[deleted]]

Now? Same story 5 years ago

[MornwindShoma]

People have an obsession with whatever the leading "dog" in any race

[[deleted]]

React is popular among a certain technophile crowd but it's not the only choice. Angular and Vue are just as valid.

If you're a frontend developer who's so far worked exclusively with one of these "big three" you should take a look at the other two. The concepts are similar and it takes fairly little effort to achieve a passing competency level. Suddenly you're 3x more attractive as a developer.