[maclockard]

I don't think this distinction is exactly correct. I've worked on some enterprise projects with larger scale teams that have used React. It offers a bit more control than Angular does in terms of what your frontend 'stack' is comprised of. This level of control can be appealing for large projects.

I kinda see a trend that projects started after x date tend to use React over Angular, but I am unsure of what x is or how universal this is.

[xxffgg557]

Obviously some enterprises have used either. This is not about subjective experience.

Regardless, it should be obvious to anybody that has ever worked in a massive corporation that a DIY approach with react will not be opted for. Talking about the corps where most people get jobs, not the ones that publish blog posts on hacker news

[dragonwriter]

> Regardless, it should be obvious to anybody that has ever worked in a massive corporation that a DIY approach with react will not be opted for.

While it's public sector, I work for a fairly big, boring, enterprise org that doesn't publish anything on HN and for our apps that use a SPA framework, a “DIY approach with React” is pretty much exactly what we are doing,at least in my corner of the org. Never heard of anyone in the org using Angular (there's some shops doing jQuery/Bootstrap stuff, and some at least experimenting with Blazor which isn't surprising given how .NET-heavy the org has been.)

There was a time when Angular was sort of the enterprise Java of SPA frameworks, but I think that's kinda past already, and lots of big boring enterprises missed it completely.

[maclockard]

In my experience bigger companies seem possibly _more_ prone to a DIY approach than scrappy startup. Especially if there is a 'not built here' mentality.