Angular is so much nicer and more batteries-included than React. React somehow manages to be massively yet incomplete: add a router, add state management, add react-hook-form...
In practice, at scale, in an ecosystem instead of a toy project, excessive choice is counterintuitively a bad thing.
It's hugely beneficial to have common ground and shared interfaces when integrating code from third parties, or collaborating across multiple teams.
> You can pick
A golden rule of large enterprise is that there is no "you".
As soon as there are two people working independently, not to mention different business units or teams, different choices will be made. Incompatible choices.
Angular is used a lot in enterprise apps/services when they need a low risk one-way to do things (e.g. Apple's App Store developer portal).
React is used in enterprise when teams need to move fast and break things (e.g. Microsoft Edge's UI after switching from Trident/Spartan/EdgeHTML to Chromium) and tend to be replaced with something else when dev teams / managers realise that they need to rebuild it anyway just to keep it maintained and/or gain more performance. (e.g. Edge "WebUI 2.0" moving their browser UI from react to web components)
