Live data from Hacker News

Does anybody like React?

jsx.lol

141–150 of 353 posts

Re: Does anybody like React?

#141

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

But why over vue? My biggest frustration has been how vue ends up moving in the direction of react. The original component architecture with the html template, JavaScript state and css styles in vue was so nice. Even the data fetching a url in the component was so intuitive.

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

Re: Does anybody like React?

#142
React is fine. The shit people add to it (including the React team!) sucks tho. Raw react is just declarative UI.

Server components, state management libraries, data fetching libraries, routers, etc, are horrible. Same with most UI libraries. They add so much overhead and complexity.

Re: Does anybody like React?

#143

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.

If it is so intuitive, why then does basically every React app contain performance bugs?

What does being intuitive have to do with software optimization? You can write poorly performing code for anything. Most people never touch profilers.

Re: Does anybody like React?

#145
post #130

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

why is RSC not considered react? it is designed by core React team, and heavily recommended by core React team. and needs deep support from react.

Doesn’t mean you have to use it.

Re: Does anybody like React?

#147
post #30

Earlier quoted context omitted.

I was a big Sevelte fan. After writing a sizeable application in Sevelte I realized that React is superior in every way overall speaking and at least you're writing 100% pure JavaScript directly. Or Typescript. Plus the ecosystem. It's huge. Nothing comes closer.

> 100% pure JavaScript directly How did the React community convince so many people of this falsehood? Do that many people just not know what javascript is? It baffles me that one could look at JSX and be like, “that right there is vanilla javascript”.

What people mean is obviously that you use JS primitives for looping, branching, conditionals, etc. over some DSL. Everybody knows that the tags are added syntax, there is no conspiracy here.

Re: Does anybody like React?

#148

Earlier quoted context omitted.

If it is so intuitive, why then does basically every React app contain performance bugs?

What does being intuitive have to do with software optimization? You can write poorly performing code for anything. Most people never touch profilers.

The same kind of bugs don’t happen in Vue because the framework handles them for you.

Re: Does anybody like React?

#149
post #13
post #8

I like React. And I have seriously tried the HTMX/Hotwire camp. I wanted to make a back button use browser APIs to go back if the coming from the inbox, just link to the inbox otherwise to preserve scrolling. I had to wire the actions from the html to call the function that goes back, then in my controller determine the previous page and send the JS enabled back button or the hard link. My logic was spread out over 3…

> I wanted to make a back button use browser APIs to go back if the coming from the inbox, just link to the inbox otherwise to preserve scrolling. I had to wire the actions from the html to call the function that goes back, then in my controller determine the previous page and send the JS enabled back button or the hard link. This is why I hate react spas. They're always trying to find some stupid way to break my bro…

That's not a react thing, it happened before React was even a thing. It's just self-centered website programmer design.

Re: Does anybody like React?

#150
Initially I didn't see the value in React. I thought that the whole virtual DOM compiling on every change was a waste of resources instead of just doing the change itself directly.

But as it turns out it's a great abstraction worth using for the right things (not every part of the web) and one of those are Single Page Applications.

A lot of comments here are about people linking JSX instead of React and that's a good abstraction too. In Mint (https://mint-lang.com/) I'm trying to create a language for SPAs and having HTML syntax helps.

Post reply on HN