[blindseer]

> One way data binding that is immutable and has explicit functions for each state transition is a major feature.

> <Tag a="b" x={y+z}>{valid JS expression}</Tag> > is > React.createElement(Tag, { a: "b", x: y + z }, [<valid JS expression>])

If you take the main reasons React is criticized and claim it is a feature, surely you have refute the criticism more thoroughly than "This seems so simple, yet do not underestimate it." or "That is powerful. Do not underestimate this."

Modern frameworks (Svelte / Vue / Astro) are about using the platform. They are performant, efficient, easier to read, easier to write, and easier to understand.

I don't see any reason I would pick React for a greenfield project anymore.

I get that if YOU don't want to use a modern framework and want to stick with what you know, sure, by all means, pick React. But writing even a semi complex application in both React and Svelte should make it immediately obvious that React is antiquated, if you give both frameworks a fair shake.

[whoknowsidont]

>They are performant, efficient, easier to read, easier to write, and easier to understand.

Proof? Source?

>I don't see any reason I would pick React for a greenfield project anymore.

I don't see why you wouldn't. It's stable, performs well, works in every browser, easy to find answers for problems you run into, and almost every knows it (or should, it's 2024, you don't have an excuse anymore).

>I get that if YOU don't want to use a modern framework

React is the modern framework. It's nimble, concise. The other frameworks are regressive -- they make mistakes that older frameworks already highlighted as being problematic over time.

[frfl]

You should read this article, it was quite good, even if you do continue to use React after. It's good to understand the alternatives, even if you never use them.

https://joshcollinsworth.com/blog/self-fulfilling-prophecy-o...

It's been a few months since I read it, but I recall the main thing I took away from this was: React isn't necessarily the best choice, other frameworks provide better performance, development experience and tooling that should also be considered

Of course these are just opinions. Everyone should consider all the facts and come to their own conclusions about what they use and don't use.

Companies will continue to use React of course. But I'm not sure if I would use vanilla React for anything I have complete control of.

[whoknowsidont]

> It's good to understand the alternatives, even if you never use them.

I understand them quite well. I would say I probably understand them better than OP.

[mrcartmeneses]

I’ve done exactly this. Can confirm you are correct. Svelte is also much more performant in the client. But react is great in its own ways and I particularly like the way it tends to point developers towards composition of small components.

[threatofrain]

> But react is great in its own ways and I particularly like the way it tends to point developers towards composition of small components.

But this is so table stakes nowadays it's like saying your restaurant has a bathroom.

[oglop]

I remember thinking I’d like to pick up react for some changes we were planning at work. I spent a weekend with Road to React making a simple web app. I was amazed how overly complicated it seemed and that I was being told “there’s no DSL” but JSX sure seemed like one. I’m a moron and not some special coder so maybe that’s why. I was also using rails 6 at work at the time, but 7 seems to have eliminated any need we thought were were going to have for react so that’s been nice.

Each person that I’ve come across who likes react is super smart and I can’t follow what they are trying to say is so great. So maybe don’t listen to me anyway.