Live data from Hacker News

Does anybody like React?

jsx.lol

281–290 of 353 posts

Re: Does anybody like React?

#281

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

Have you used Svelte? I can’t see why anyone would like React more. The only upside I think react has it’s the IBM of frontend. No one has been fired for choosing React.

Svelte is cool although I didn't have some big epiphany. I'm not going to use Svelte because "it compiles" and "is faster" when my existing React app performs very well. Plus there are some libraries for my specific use case that didn't exist in Svelte. I know people love things besides React, and I would be happy to see it unseated. Sure I'm part of the problem but it's been good to me and I have bigger fish to fry.

Re: Does anybody like React?

#282

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

Have you used Svelte? I can’t see why anyone would like React more. The only upside I think react has it’s the IBM of frontend. No one has been fired for choosing React.

Currently rewriting nextjs app into sveltekit. It’s going surprisingly smoothly. Don’t know about svelte vs react yet BUT sveltekit is far more straightforward than nextjs has far better DX and is somehow faster

Re: Does anybody like React?

#283
post #40
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.

Could you expand on your experience compared to react?

I had main issue with smaller ecosystem. Very limited components and everything else is geared towards React. Take React Query for example. If you want first class data caching and retry logic etc, then Svelte support was second class at least couple of years ago.

Same goes for component libraries.

Re: Does anybody like React?

#284
post #124

Earlier quoted context omitted.

JSX is abc turns into createElement('div', null, 'abc') and you can use that instead of JSX if you like or you can use something like hyperscript. Everything else like mapping or if statements is pure JS and works just like JS anywhere else in your app. Vue templates mean learning Vue's custom syntax for if statements, loops, dynamic attribute syntax (with its own gotcha), binding dot modifiers, data binding, and wha…

It’s a distinction without a difference. Both need to be transpiled, what happens under the hood is of little concern to anyone. Please explain React’s reactive data binding since it’s apparently much simpler than v-model= ;)

It was explained here: https://news.ycombinator.com/item?id=48274077#48275389

Re: Does anybody like React?

#285

Earlier quoted context omitted.

It is a massive difference. I do not like magic compilers. The JSX transform is trivial and not even necessary, just create a factory function and React.createElement becomes arguably more readable, just not HTML like.

Is it a massive difference, or is it a small difference? At the end of the day 99% of React projects have a transpilation step and utilize some form of “magic compiler” somewhere along the line. The simplicity of JSX is overvalued. It just means more code, and typically uglier code, to achieve the same behaviour as Vue. Which is basically the theme of React when you compare the two libraries.

It is more explicit code. Something only changes when I tell it to rather than being magical like in Vue, not to again mention its proprietary DSL and API.

Re: Does anybody like React?

#286

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

Have you used Svelte? I can’t see why anyone would like React more. The only upside I think react has it’s the IBM of frontend. No one has been fired for choosing React.

More library support for React over any other framework. I also like explicit state change over implicit.

Re: Does anybody like React?

#287
What's interesting to me is that it seems a lot of people got burned by AngularJs (Angular 1) and now swear off Angular as a whole.

Like many, I came from pre-SPA days -> AngularJs -> Angular 2 -> Modern Angular. I tried react a few times, plus React Native but found it hard. I wasn't good with a slightly different render-syntax (whereas Angular uses HTML) and every project I was on was wildly different from each other.

Modern Angular has been wonderful. A lot of the pain points people have are gone, some good parts of other frameworks (signals, single-components vs modules, etc) have been incorporated and embraced.

Re: Does anybody like React?

#288
post #216

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

React uses an algebraic effectful function model which is elegant once one understands it: https://overreacted.io/algebraic-effects-for-the-rest-of-us/

Re: Does anybody like React?

#289

One of the talks I really enjoyed is https://www.youtube.com/watch?v=h9SDuTSy7ps . In my experience, React's architecture is really good and lends itself quite well to making large applications. Unfortunately, React's biggest problem is that it forces you into the JS/TS ecosystem, which is, without a doubt in my mind, a compilation target rather than a system I wish to interact with natively. I'm happy with Elm -- th…

Elm is essentially dead in my experience. I'd rather stick with React and TypeScript with libraries that continue to work. And there have been attempts at making TypeScript natively compilable too.

Re: Does anybody like React?

#290
post #81

Of course people do. No one is forced to use React or any other web framework unlike how they are practically forced to use JavaScript, and yet React wins. This should be enough evidence that people like it enough, at least more than most other frameworks out there. It is also somewhat ironic that until late 2010s a common complaint about web development is how fast it changes and how many new things are coming up al…

What do you mean nobody is forced to use react? What is this brave new world where you can learn lisp and use it for everything you desire, where corporate culture has no sway over your tech choices?
Post reply on HN