Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Is React Having an Angular.js Moment?

marmelab.com

Post reply on HN
Print view View original

11–20 of 97 posts

Re: Is React Having an Angular.js Moment?

#11

Post by marviel »

> React Server components require new generation routers, new generation bundlers. They are officially in alpha, and not ready for production. So why is Next.js so pushy about it? I can't avoid feeling that the new direction taken by Next.js is not designed to help developers, but to help Vercel sell React. You can't really sell a service around SPAs: once compiled, a SPA is a single JS file that can be hosted for free anywhere. But a server-side rendered app needs a server to run. And a server is a product that can be sold. Perhaps I'm a conspiracy theorist, but I don't see another reason to break the React ecosystem like this.

I mean, yeah, I see your point.

React should always be self-hostable, full-stop.

Re: Is React Having an Angular.js Moment?

#12

Post by Merad »

I tend to agree with the article. I've felt pretty frustrated with the direction of react in the last few years. Most of the companies I've worked for that used react did so because they wanted a SPA, in most cases making a conscious decision to move away from older SSR technologies towards the SPA.

It's doubly frustrating because we primarily use C# and Asp.Net Core for back end work. A react SPA is trivial to use with any back end of your choosing... this SSR push they're making isn't much fun unless you use a JS back end (no thanks).

Re: Is React Having an Angular.js Moment?

#13

Post by soneca »

I was ready to dismiss the article because the answer to the title question is an obvious “No”, as server components is not a breaking change. It’s optional. But the author addresses it and then makes a very good point.

> ”The introduction of React Server Components, unlike the Angular.js to Angular 2 transition, is not a breaking change. Existing single-page applications will still work with the latest version of React. Existing Next.js apps built with the Pages router will also work. So, the answer to the question "Is React having an Angular.js moment?" is "No".”

> ”So to the question "Is React harming its community by being too ambitious", I think the answer is "Yes"”

The article is very good and well worth the read. I am inclined to agree that this is a NextJS move, that goes against the interests of React developers, with the goal of locking React developers in their own services. The React team is on board with this and playing along. I think they shouldn’t.

Re: Is React Having an Angular.js Moment?

#14

Post by soneca »

resoluteteeth wrote: post #10

React has already through massive changes with emphasizing classes -> function components -> hooks. OTOH it hasn't broken backwards compatibility. I think Server Components are similar to the introduction of hooks because while they require changes to use, they don't affect anything if you aren't using them. You could argue that it's such a massive change they should make it as a separate framework, but React's appro…

I think, right now, they are nudging everyone to change. And if there is no pushback, like this article, in an year or two they will be forcing.

Re: Is React Having an Angular.js Moment?

#15

Post by [deleted] »

soneca wrote: post #14
resoluteteeth wrote: post #10

React has already through massive changes with emphasizing classes -> function components -> hooks. OTOH it hasn't broken backwards compatibility. I think Server Components are similar to the introduction of hooks because while they require changes to use, they don't affect anything if you aren't using them. You could argue that it's such a massive change they should make it as a separate framework, but React's appro…

I think, right now, they are nudging everyone to change. And if there is no pushback, like this article, in an year or two they will be forcing.

[deleted]

Re: Is React Having an Angular.js Moment?

#16

Post by patates »

Merad wrote: post #12

I tend to agree with the article. I've felt pretty frustrated with the direction of react in the last few years. Most of the companies I've worked for that used react did so because they wanted a SPA, in most cases making a conscious decision to move away from older SSR technologies towards the SPA. It's doubly frustrating because we primarily use C# and Asp.Net Core for back end work. A react SPA is trivial to use w…

Many have switched to a backend for frontend design (BFF). So you have another backend that proxies and/or uses the real backend and makes SSR and other frontend things.

A better explanation: https://blog.bitsrc.io/bff-pattern-backend-for-frontend-an-i...

Re: Is React Having an Angular.js Moment?

#18

Post by patates »

soneca wrote: post #14
resoluteteeth wrote: post #10

React has already through massive changes with emphasizing classes -> function components -> hooks. OTOH it hasn't broken backwards compatibility. I think Server Components are similar to the introduction of hooks because while they require changes to use, they don't affect anything if you aren't using them. You could argue that it's such a massive change they should make it as a separate framework, but React's appro…

I think, right now, they are nudging everyone to change. And if there is no pushback, like this article, in an year or two they will be forcing.

They never made such a forced (big) breaking change. I don't have a reason to think they would in a year or two.

Re: Is React Having an Angular.js Moment?

#19

Post by vbello »

scientaster2 wrote: post #6

I've given server components with Next.js an honest try in my personal projects, and honestly, the pain of using them far outweighs the benefits. I MUCH prefer the pattern of getServerSideProps seeding data on-page-load and working with it via context providers. The fact that data loaded in with server components cannot support reactivity of any kind means you have to litter your code with "use client" wrappers that…

Client component still get SSR benefits. They just happen to be included in your JS bundle. This makes sense in the context of your example – you do expect the active route link to change during a client-side navigation.
Post reply on HN