I have been a part of quite a few tech stack decisions at various companies and startups. I have literally never heard an argument made for react that included merits of the framework itself. The decision was always based on a combination for familiarity, ability to hire for eng roles, and the ecosystem.

▲

zarzavat 6 hours ago | parent | next [-]

> I have literally never heard an argument made for react that included merits of the framework itself.

That doesn't mean that those merits don't exist. Most of the new React competitors are just reinventions of HTML templating done client-side. React has been dominant for so long that there's a whole generation of frontend devs who don't remember why it was invented in the first place. Writing loops in HTML? We tried that, it sucks!

It's telling that the "new" frameworks have no ideas other than to revert to ideas that were tried in the past. React is so modern it makes its replacements feel dated.

▲

Xenoamorphous 8 hours ago | parent | prev | next [-]

> I have been a part of quite a few tech stack decisions at various companies and startups. I have literally never heard an argument made for react that included merits of the framework itself. The decision was always based on a combination for familiarity, ability to hire for eng roles, and the ecosystem.

Couple of thoughts regarding this:

* A competing alternative would have to have really big benefits from a technical standpoint to outweigh the React advantages that you mentioned.

* When exploring alternatives IMO the burden of proving that something is better lies within the person/people that want to go with an alternative option. React is the de facto standard these days so it shouldn't be a matter of "why React" but "why not React".

▲

noodletheworld 11 hours ago | parent | prev | next [-]

Then why dont you pick jquery?

Its easy and well known, even now.

The answer I see is that react is technically good enough.

Using boring technology doesnt mean using the technically most advanced thing.

It means picking something safe and stable.

▲

_heimdall 9 hours ago | parent | next [-]

Why would you need jquery today? What can it do that native browser APIs can't?

▲

noodletheworld 8 hours ago | parent | next [-]

Jquery is the old default for web apps from before people decided they wanted react.

What can it do that others cant? Literally nothing.

That didnt and does not stop it from being used for connivence sake.

The point is: if its not about the technical quality; why are we not still using it now?

	▲	zelphirkalt 3 hours ago \| parent [-]
		If that is the point, then I feel it is made out of technical mediocrity, rather than excellence. A good team should be able to adapt the technology that best fits the task, and companies should be able to hire for it. Or stay mediocre otherwise. The hiring issue is home made. If companies started hiring for engineering skills, rather than familiarity with existing tech stack, it would change quickly. Experienced engineers are able to learn new languages and frameworks on the job. Of course, if hiring is too petty to give engineers a month of getting familiar with the product and expect readiness from the get go, then they will continue to miss out on talent.

▲

mexicocitinluez 4 hours ago | parent | prev [-]

Jquery didn't provide anything that you couldn't already do with native browser APIs, it was a wrapper around those APIs.

▲

MisterSandman 11 hours ago | parent | prev | next [-]

React is significantly more easier to hire for than JQuery is, especially in this market. Especially if you’re looking for more junior roles.

As a new grad, I would’ve picked a react job over a JQuery job even if the JQuery one paid me 10k more.

▲

isqueiros 7 hours ago | parent | prev [-]

maintaining a large jquery/native js codebase vs a react one is not even in the same ballpark.

even when not being opinionated react foundationally has more structure for complex code.

▲

kamaal 13 hours ago | parent | prev [-]

Im not sure how this is a negative merit for React.

Besides if you are a small company, or a start up, your job is to get things done. Not to embark on a global technology crusade to push your favourite tech.

By and large the best thing about react is the overall ecosystem, libraries, talent and ubiquitousness. And thats a good thing.

▲

_heimdall 13 hours ago | parent | next [-]

It isn't necessarily a bad thing, but it doesn't align with the idea of how good react is or the technical merits of it.

I also am not saying teams I have been on that picked react made the wrong choice. That's all in context and as you said startups are often in the "get things done" mentality where tech debt won't matter if you can't survive long enough for it to matter.

▲

tcoff91 13 hours ago | parent [-]

It’s good enough that the ecosystem outweighs the superiority of something like SolidJS.

React has React Native as part of its ecosystem. That’s a massive advantage. react-strict-dom is going to be a game changer for the development of universal apps.

	▲	_heimdall 12 hours ago \| parent [-]
		We're talking about two different topics here. I agree, the ecosystem around react is huge and there are reasons a team would pick react. Ecosystem isn't an indicator of the technical merits of react itself though, and that's what I was originally responding to here.

▲

fireflash38 3 hours ago | parent | prev [-]

That's a thought terminating cliche.

You aren't arguing on merits. You're arguing on everything else. Why aren't we all still using C? Or B? Why isn't every website on good old PHP?

Things change because people want better or different. Saying "people already use it" is not an argument for something.