No
Does anybody like React?
211–220 of 353 posts
Re: Does anybody like React?
#212More than React, I'm interested in the question of how to best write UI through code, in general. Even though I'm a fan of React, and use it for practically every web application I build, my biggest and most obvious issue has been that writing UIs through React doesn't feel as natural as, say, writing command line tools in Go, or live/realtime apps in Elixir. Some languages just feel incredibly natural and frictionle…
As an engineer, it's easy to look at every problem and think to yourself: "There is a perfect solution for this, we just haven't found it yet."
Yet, as the years go by, I find myself accepting a less idealistic answer: Maybe there isn't. Maybe the problem space is just so complex that no one (humanly feasible) general solution exists for all forms of it. If there's one thing that this is true for, UI is probably it.
Re: Does anybody like React?
#213Earlier quoted context omitted.
A bit out of date, but I like the point-of-view of "The single most important factor that differentiates front-end frameworks" : https://mjswensen.com/blog/the-single-most-important-factor-...
> A bit out of date > article just about to turn three years old JavaScript community never beating the allegations lol
I skimmed through it, and I think the only thing that is out of date is the section on `zone` in Angular. In october 2025, they changed to `zoneless` by default, which uses signals just like Vue. This was a long time coming imo, as the major criticism of Angular was how poorly update management was handled. Also Svelte runes aren't mentioned, as that came out three months after this post. Runes are essentially also signals.
Basically every framework now has a concept of * State - change this and the framework automatically updates UI and triggers effects * Effects - functions that run when parts of state change (or triggered by signals)
And almost everyone solves this with signals except for React.
Re: Does anybody like React?
#214As someone who lived through all major waves of JS for the last ~16 years, I do love react, in a sense: React is the worst JS framework except for all the others we've tried. I'd take React over the Angular 1 days any time. I'd take Angular 1's full-bodied MVC over the "build it yourself from scratch every time" approach of Backbone. I'd take Backbone's minimal MVC structure over the classic JQuery Soup architecture.…
[deleted]
Re: Does anybody like React?
#215I like scripting so I like having a and then do everything in JS. No need for Typescript or React, innerHTML=`...` works fine. For a serious project, React and Typescript make sense but it can still be used wrong. The default Laravel project that's generated when choosing React looks really bad to me. Too many files and comments and tests. It's over-engineered.
Re: Does anybody like React?
#216After spending so long writing React code, I'm now working on a large Vue project at work. Everyone used to say Vue was the easier of the two, the more approachable option — but I'm starting to see it differently. React, in its elegance, gives you components that are essentially just functions — and beyond that, there's not much more to it (setting aside the whole Next.js ecosystem). It's the most elegant thing I've…
I never get this take. A react component is not just a function, it's a function plus a magically injected context that is accessed through hooks which requires all kinds of guarantees that you have to be aware of otherwise it will have hard to debug consequences. Imo it's anything but elegant.
I did projects in all major frameworks and am building a huge angular web app currently. In angular a component is represented as a class plus template (plus styles). A event listener is mostly calling a method on the class. A state can be as simple as a property on the class. It's very natural and there are way less caveats (although not zero).
Re: Does anybody like React?
#217I actually like React's virtual DOM approach. It might not be the fastest possible solution, not the most elegant syntax, not particularly concise. but I can at least understand what it does and how data flows. I learned the hard way that with reactive programming (whether you call it observables, runes, signals, whatever) you can lose that understanding and it's a huge pain when that happens.
Re: Does anybody like React?
#218After spending so long writing React code, I'm now working on a large Vue project at work. Everyone used to say Vue was the easier of the two, the more approachable option — but I'm starting to see it differently. React, in its elegance, gives you components that are essentially just functions — and beyond that, there's not much more to it (setting aside the whole Next.js ecosystem). It's the most elegant thing I've…
How long have you used Vue? I had a similar opinion on Vue a few years ago, coming from a background of React as well. But now I prefer it over React, and reach for it in both personal and professional projects. The ergonomics are a bit different; there are things that are easier to do in React, and things that are easier to do in Vue, but the fact that it uses signals is a huge plus for me.
Re: Does anybody like React?
#219I actually like React's virtual DOM approach. It might not be the fastest possible solution, not the most elegant syntax, not particularly concise. but I can at least understand what it does and how data flows. I learned the hard way that with reactive programming (whether you call it observables, runes, signals, whatever) you can lose that understanding and it's a huge pain when that happens.
No Server Components though, they are the pinnacle of too clever to be a good idea.
Re: Does anybody like React?
#220Earlier quoted context omitted.
It does, if you care about ergonomics. The reactivity model is simpler and arguably less error prone. It does have its own templating syntax, which is trivial to learn. No more cumbersome to learn than JSX, which is a templating language designed by the React team. Not sure why you chose to make the distinction between JSX and Vue’s DSL as if JSX wasn’t developed for the sole purpose of facilitating React’s virtual D…
JSX is a very thin layer of templating logic inside JS. Meaning you have all the language features available while templating. Some arbitrary JS can result in templating. Vue's DSL is whatever language the developer implemented. Which is probably not enough, depends how much effort they put into it and how good they are in language design. Given that they cargo cult HTML tags to organize components in a pseudo-famili…
While I understand the advantage of using the built-in language features (and I know why it is required to be done that way), I still think using
{enable && }
{collection.map(x => }