Earlier quoted context omitted.
You're confusing your own experience for the reality of the market. My last three employers use Angular. My current employer just replaced an AngularJS app with a new Angular 11 app for a Fortune 100 client. Go to a job listing site and you'll find just as many positions hiring for an Angular dev (often paired with C#/ASP) as you will React.
FYI there is 10 Angular vs 99 React (# of word occurrences) in a recent "who's hiring" thread [1]. [1] https://news.ycombinator.com/item?id=31582796
Angular v14 is now available
41–50 of 114 posts
Re: Angular v14 is now available
#42Earlier quoted context omitted.
Because of the whole "master" meaning a slave owner thing that the progressive left seems to think it means and it apparently hurt enough feelings to make it a movement (default main branch on Github repos is now also "main" because of this), and then you have companies that desperately try to be hip and cool, and they do this to get social clout. The whole thing is pretty sad if you ask me, but what do I know.
This has nothing to do with left/right. This is a racial issue. People of color exist along the entire political spectrum.
Re: Angular v14 is now available
#43Earlier quoted context omitted.
I've used it on a lot of client projects, my current one included. Angular's batteries-included approach makes it way faster to spin up a new app for a new project, and avoids the problem of picking the wrong dependency for (state/navigation/styling/etc.) that plagues React projects.
Next.js has finally solved React's mess But I can't agree more, Angular has for its whole existence of 10+ years always been more consistent. But it's not always about tech - Facebook's Marketing > Google's Marketing ...
Facebook used React internally before releasing it. Every new web front-end at Meta is written in React. They also had a convincing story of how the runtime expands beyond the web (React Native etc.)
With Angular, you’d be hard-pressed to name a Google service built using it. It seems to be a framework created condescendingly for the ordinary others, not the Mountain View geniuses themselves. That’s not great marketing.
Re: Angular v14 is now available
#44Re: Angular v14 is now available
#45Earlier quoted context omitted.
Because of the whole "master" meaning a slave owner thing that the progressive left seems to think it means and it apparently hurt enough feelings to make it a movement (default main branch on Github repos is now also "main" because of this), and then you have companies that desperately try to be hip and cool, and they do this to get social clout. The whole thing is pretty sad if you ask me, but what do I know.
This has nothing to do with left/right. This is a racial issue. People of color exist along the entire political spectrum.
Re: Angular v14 is now available
#46I'm kind of amazed Angular is still around. I hadn't heard of it for what feels like years at this point & assumed it was already in the graveyard. My company tried using it back in 2017ish but it was a pain for us at the time. Other than Google's own services, does anyone have any examples or experiences using Angular nowadays?
It was succeeded by Angular (versions 2 and up), which is very popular for large complex apps at large companies. I think React, in the form of Next and other frameworks built around React, have finally caught up with the reason that made it so: more stuff "in the box", with decisions already made and already working.
If you have 200 Angular projects, there's a good chance developers can move between them without much difficulty. If you have 200 React projects, they might have 15 different combinations of selections for various accompanying libraries. This makes moving developers around harder (matters a lot in large organizations).
For example, nearly every Angular project uses Angular's CSS isolation mechanism plus Sass for complexities on other axes. Whereas there are various popular CSS solutions that divvy the React user community among them.
There are trade-offs, of course; Angular has so much in the box that so far nothing like Next (convention-based routing etc.) has sprung up around it. So I am quite bullish on React and Angular both - there will be lots of large important projects churning along with these in another decade, and beyond.
Also important to remember that these are just the two most popular; there are a couple of hundred other competing SPA frameworks that work very well for their intended use cases.
Re: Angular v14 is now available
#47I'm kind of amazed Angular is still around. I hadn't heard of it for what feels like years at this point & assumed it was already in the graveyard. My company tried using it back in 2017ish but it was a pain for us at the time. Other than Google's own services, does anyone have any examples or experiences using Angular nowadays?
Re: Angular v14 is now available
#48I'm kind of amazed Angular is still around. I hadn't heard of it for what feels like years at this point & assumed it was already in the graveyard. My company tried using it back in 2017ish but it was a pain for us at the time. Other than Google's own services, does anyone have any examples or experiences using Angular nowadays?
I've used it on a lot of client projects, my current one included. Angular's batteries-included approach makes it way faster to spin up a new app for a new project, and avoids the problem of picking the wrong dependency for (state/navigation/styling/etc.) that plagues React projects.
The atomicity of React makes it applicable in an immense variety of usecases, however this comes at the cost of an ecosystem providing a very fragile dependency graph.
With React you'll almost always have the newest trendy thing available as a tool (and not with Angular)[1]. Which means if someone comes up with a completely new philosophy that might better match your (team's) mental models, chances are it's available for react first.
OTOH this means chances are that the concensus of "how to do things" has changed so much within a short time, that older projects are not only difficult to upgrade, but consist of code that is really, really hard to understand at all.
[1] e.g. there was a time when Google's own Material UI was better implemented for React than for Angular.