Live data from Hacker News

Does anybody like React?

jsx.lol

131–140 of 353 posts

Re: Does anybody like React?

#131
I kinda like react with hooks but I do miss Angular 1 watches. Explicit watch expressions solve a loooot of spurious rerendering nonsense that makes for a lot of churn

Ultimately I think React makes it too hard for the performant solution to be used. And then tries to handwave it all away with “the react compiler solves/will solve it”. Don’t even get me started on “useMemo is not semantics” rationalization. First time runs actually matter when working on a performant UI!

DOM ops are expensive but your little bespoke function component code is also expensive when some hook leads to recalcs all over.

Re: Does anybody like React?

#132

Yes! It is hands-down, the most intuitive interface, that has successfully married declarative and imperative styles together. IMO, nothing comes close to JSX across the length and breadth of UI frameworks across all languages.

Flutter, SwiftUI, Jetpack Compose: a whole lot of other platforms have been implementing React as their UI framework

Re: Does anybody like React?

#133
post #123

As 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.…

React was a major improvement over Backbone + Marionette. Pre-jQuery was a shit-show as they hadn't even standardised the DOM. Before that was XMLHttpRequest (particularly during my .Net WebForm days) and even had to use the ActiveXObject in IE that predated JSON.

Oh boy the ActiveXObject brings back some ~~ptsd~~ fond memories.

Re: Does anybody like React?

#134
post #123

As 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.…

React was a major improvement over Backbone + Marionette. Pre-jQuery was a shit-show as they hadn't even standardised the DOM. Before that was XMLHttpRequest (particularly during my .Net WebForm days) and even had to use the ActiveXObject in IE that predated JSON.

XML, XMLHttpRequest, and XSLT in IE 5 was peak web dev for me. Never been more productive.

Re: Does anybody like React?

#135

I’m not an FE engineer but have found myself working very closely with the whole stack recently, which includes an SPA. We use html, JavaScript, Alpine for reactivity and Supabase realtime subscriptions. It seems … okay? I feel like I can reason about it. But I worry I’m missing something that’s going to come back and bite us later because we haven’t adopted a framework. Roast my stack?

Would be silly to rate your stack without knowing more about what it is and its constraint.

If I had to judge it based on this alone post alone:

Great, seems like a straight forward stack. Would happily work on it.

Only criticism, to get all the ergonomics out of alpine, you sometimes have to lax some CSP or use the CSP build. Not necessarily a deal breaker, it is what it is.

Re: Does anybody like React?

#136
I haven't really deeply thought about frontend JS for many years.

Back then the question we were looking at was whether it would be good idea to move away from SAP UI5. The alternatives back then where React, Angular and Vue.

The conclusion we came to was that it was definitely worth to migrate, but to what was not so easy to agree on.

Right now I am working with a legacy Java codebase that was based on RxJava. And every single day I am cursing the people that made that decision. It seems so obviously a bad idea. And the only thing that lets me keep my sanity is remembering that every decision only becomes obvious with hindsight.

So I guess the only thing I can contribute is that it could always be worse and sometimes making the bold and seemingly innovative decision comes back many years later to bite other people.

Re: Does anybody like React?

#137

> Critical Security Vulnerability in React Server Components RSC isn’t React. > Next.js 15.1+ is unusable outside of Vercel Next.js isn’t React. By contrast to nextjs, React + Vite is quite a nice combo. Maybe Bun or Deno are also good? But nextjs and RSC should be kept separate from the discussion. With React I find there is usually a clear and simple way to achieve what you want, and while it doesn’t perform super…

this a million times. the next.js intermixing of backend / frontend code is a security nightmare.

Re: Does anybody like React?

#138

I’m not an FE engineer but have found myself working very closely with the whole stack recently, which includes an SPA. We use html, JavaScript, Alpine for reactivity and Supabase realtime subscriptions. It seems … okay? I feel like I can reason about it. But I worry I’m missing something that’s going to come back and bite us later because we haven’t adopted a framework. Roast my stack?

I think this is a very sane stack.

Will probably become a hassle when going planet-scale (tm), but I think for most use cases this should be fine.

Re: Does anybody like React?

#139
I loved react in 2013 when it had the life cycle methods. Everything was deterministic, I knew what caused what where and when. Now every framework is a mess and I'm glad I won't have to learn anyone's crap anymore thanks to random code generators.
Post reply on HN