Is React Having an Angular.js Moment?
marmelab.com
Is React Having an Angular.js Moment?
1–10 of 97 posts
Re: Is React Having an Angular.js Moment?
#2React 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.
Re: Is React Having an Angular.js Moment?
#3It's a good thing. React team needs to keep up and keep fighting on the performance story.
Longer story: I hate ALL-in-one framework/libraries.
I prefer separation of bundling, compiling, rendering,... . It's called the SRP principle.
Re: Is React Having an Angular.js Moment?
#4React 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.
The author is talking about Angular.js, which the legacy version 1.x, and not the modern Angular 2+.
Re: Is React Having an Angular.js Moment?
#5I think this is entirely a documentation and marketing issue at this point. React Server components are very new, probably new enough that most people should not use them unless they're very comfortable working on the bleeding edge.
The problem is that React points towards Nextjs as a default, and Nextjs makes Server Components the new default.
It doesn't actually change anything for anyone that still wants to develop a standard SPA. And these changes also don't seem to make any of the old methods obsolete, they simply add another method that you can use to develop web apps.
Re: Is React Having an Angular.js Moment?
#6I'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 take in their parent data as initial state, then introducing client reactivity on top.
That^ also means that any time you drop into "use client" you drop any SSR benefits anyway. I agree with a lot of this article that the transition feels forced, and I can't help but hope that Vercel commits to supporting pages style routing indefinitely.
Here's an example, the pattern makes it almost impossible to highlight a currently active route in a navbar. Literally a basic building block of web applications: https://github.com/vercel/next.js/issues/43704
Re: Is React Having an Angular.js Moment?
#7I 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.
Re: Is React Having an Angular.js Moment?
#8React 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.
Re: Is React Having an Angular.js Moment?
#9Agree heavily with the article. As an app developer, I actively spend my time walking away from frameworks/languages/libraries that start mashing the server weirdly into client code. Each to their own but I think quasi-RPC implementations are a relic of the past.
Treating the network layer as an explicit abstraction to components just feels a better developer experience in the long run. The data abstractions are easier to reason about, and caching albeit always hard, is a lot easier to think about.
I don't even know _why_ React/Next is pushing Server Components. (Part of me wants to join the conspiratorial bandwagon like the author)
Re: Is React Having an Angular.js Moment?
#10React 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 approach of adding new approaches but maintaining compatibility seems to have been fairly popular.
Maybe server side rendering isn't what everyone wants to do, but you don't have to. I think we can all agree that if they were FORCING everyone to change what they're doing and use server components it would be more of a problem?