I think you made a very convincing argument for the limited and specialized use case that you're describing (building internal apps at a company/enterprise)
Yes, bit it's the by far most common use case I have seen in my life. And 80% of the world's software developers are in similar positions as me, so instead of claiming it's the "special use case", I'd say it's the "general rule of thumb".
as soon as this company is building a public facing app, then the discussion already changes
That's true. I'm not entirely convinced the argument changes enough to justify React, but here I'm on slightly more shaky grounds I admit ...
As to apples versus oranges? Devs typically choose between two things when they start out new projects; React and Angular. Even though Angular is a framework and React a library, I don't really agree here. These are two different competing technologies where users choose one of them when starting out new projects.
You made a (very) convincing argument for the use case that you state, however the title of your post ("Angular is almost always better than React") is of course a little bit click bait, lol ... it should have read "Angular is almost always better than React for building internal enterprise apps", but well that's not going to generate the clicks & views and comments that it generated right now, so I don't blame you haha ;)
What has bugged me about React for a long time (so I'll give you that as well, no doubts there) is that React is definitely NOT "batteries included", and that everyone seems to be endlessly reinventing the wheel.
Case in point: we have Redux as a mature state management solution, but no, we get dozens of articles how it's "better" to build your own Redux using Context and Hooks (hint: false claim, it isn't "better" at all).
That's very telling when it comes to a certain mindset, and at some point it induced huge "React fatigue" in me. I'm now back to being interested again in React, now that it has matured and there's a bit more of "de facto" standards, but please React people, can we stop reinventing the friggin' wheel? It's a waste of time.
P.S. something like Next.js might be a candidate for the 'framework' that we need - another good option is to use Redux Toolkit - I think if you combine these parts then you have a pretty complete and mature solution which could compete with Angular:
Typescript
React Router v6
Redux Toolkit with RTK Query
Just declare it "the React standard" and get it over with, lol. You need SSR then choose Next.js, and again done & dusted.
Yes, bit it's the by far most common use case I have seen in my life. And 80% of the world's software developers are in similar positions as me, so instead of claiming it's the "special use case", I'd say it's the "general rule of thumb".
That's true. I'm not entirely convinced the argument changes enough to justify React, but here I'm on slightly more shaky grounds I admit ...
As to apples versus oranges? Devs typically choose between two things when they start out new projects; React and Angular. Even though Angular is a framework and React a library, I don't really agree here. These are two different competing technologies where users choose one of them when starting out new projects.
You made a (very) convincing argument for the use case that you state, however the title of your post ("Angular is almost always better than React") is of course a little bit click bait, lol ... it should have read "Angular is almost always better than React for building internal enterprise apps", but well that's not going to generate the clicks & views and comments that it generated right now, so I don't blame you haha ;)
What has bugged me about React for a long time (so I'll give you that as well, no doubts there) is that React is definitely NOT "batteries included", and that everyone seems to be endlessly reinventing the wheel.
Case in point: we have Redux as a mature state management solution, but no, we get dozens of articles how it's "better" to build your own Redux using Context and Hooks (hint: false claim, it isn't "better" at all).
That's very telling when it comes to a certain mindset, and at some point it induced huge "React fatigue" in me. I'm now back to being interested again in React, now that it has matured and there's a bit more of "de facto" standards, but please React people, can we stop reinventing the friggin' wheel? It's a waste of time.
P.S. something like Next.js might be a candidate for the 'framework' that we need - another good option is to use Redux Toolkit - I think if you combine these parts then you have a pretty complete and mature solution which could compete with Angular:
Just declare it "the React standard" and get it over with, lol. You need SSR then choose Next.js, and again done & dusted.
Shhh ... ;)
Sure, the header could have been more correct, but it's not incorrect either ...
I suspect that train has left the station, but I might be wrong ...