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

21–30 of 97 posts

Re: Is React Having an Angular.js Moment?

#21

Post by thunderbong »

From the article (italics mine) -

> So why is Next.js so pushy about it? (React server components)

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

Re: Is React Having an Angular.js Moment?

#22

Post by the_third_wave »

There's another aspect to server components and server-side rendering in general: it makes sites less amenable to third-party front ends. The rise of client-side rendered "apps"/SPAs/etc. and the accompanying APIs made it much easier to develop third-party front ends since the data became available in easily-parsed JSON or XML. Server-side rendered sites need to be scraped, a process which is far less robust than API access. Given that many site owners are quite adverse to third-party front ends - just look at the Reddit kerfuffle for an example - this limitation may well be one of the intended features.

Re: Is React Having an Angular.js Moment?

#23

Post by Capricorn2481 »

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…

This move seems like something that pleases nobody. There's a crowd that hates SPAs and a crowd that hates heavy react frameworks, and there's very little else. It seems like the number one critique of React is how bloated it has gotten and how much it reinvents the wheel.

Personally, I've always like React as a library for small interactive parts of your website. It's fairly trivial to make your site mostly static and use something like Asp.Net to handle how its rendered.

Re: Is React Having an Angular.js Moment?

#24

Post by Capricorn2481 »

peer2pay wrote: post #8
hoofhearted wrote: post #2

React is a component library, Angular is a framework. We don’t really compare them apples to apples at work because they serve two different use cases.

This is a heavily outdated opinion. The "default" react experience nowadays is Next.js and that is definitely a framework not a library.

Agreed, although NextJS is still a lot lighter to me than angular

Re: Is React Having an Angular.js Moment?

#26

Post by fabian2k »

vbello wrote: post #19
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.

That's kind of a really "meh" thing if you develop web applications and not websites. The static parts aren't that large, and the app kinda useless until the dynamic parts are there. So that doesn't really justify additional effort.

Re: Is React Having an Angular.js Moment?

#27

Post by [deleted] »

spicyusername wrote: post #7

I think we as an industry underestimate the value of stability. It's easy to always look at what isn't perfect and think, "Hey, we know better now, let's fix that", but what does more damage, architecture that isn't perfect or constant change? It's hard to really get any momentum going when all the tooling changes every few years.

[deleted]

Re: Is React Having an Angular.js Moment?

#28

Post by dimmke »

thunderbong wrote: post #21

From the article (italics mine) - > So why is Next.js so pushy about it? (React server components) > 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…

I’ve had this thought for a while. Companies like Vercel have coined the term “composable” but it really does feel like this is what is actually driving things.

Re: Is React Having an Angular.js Moment?

#29

Post by datavirtue »

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…

What's wrong with a JS back end? Node/Express is awesome.

Re: Is React Having an Angular.js Moment?

#30

Post by datavirtue »

patates wrote: post #16
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...

Horrid dev experience.
Post reply on HN