3 ms·
I think OP is correct for reasonably large projects I've worked on large multi-team Angular/React monorepos. The tooling was lacking for both but Angular feels
by arenaninja 5y ago
I think OP is correct for reasonably large projects
I've worked on large multi-team Angular/React monorepos. The tooling was lacking for both but Angular feels like it actively gets in your way. React has a lot of churn and keeping your dependencies up to date but React itself is incredibly stable and gets out of your way
My educated guess is that this is clear because Facebook actively uses React, where most Google web properties don't use Angular. There's projects where Angular allows a team to define a SPA UI relatively quickly and pain free. But for large projects, I would continue to choose React. Also, CSS encapsulation with Angular is great until it isn't: it can be overridden only with ng-deep which is deprecated with no alternative
- brynjolf 5y agoUpdating Angular is easy, just use ng update and you are done, plus it gives hints if there are manual handling.
- arenaninja 5y agoThis is untrue. Angular has major version changes twice a year, migration is a time sink for our team to handle breaking changes in our growing codebase. Compare to React with far fewer major version updates, and fewer breaking changes (likely from their deprecation usage) Your application is likely smaller or a simpler use-case
- Bellend 5y agoThere is over 500 applications at google using Angular so it isn't a handful of special cases.