The Angular Team act like it's a great feature that they don't give "special" support to in-house dogfooding teams, but that just leaves as much an impression that they'd rather just support everyone equally bad. Sure "no special support" sounds great on paper, but it certainly looks like "no support at all" from where I'm standing.
Some Angular proponents will also make excuses that the Google Cloud Console is an amalgamation of components and pages owned by a variety of different teams, like that's a unique situation to Google that no one else deals with bureaucratic scale like that. I guess they haven't experienced much other enterprise development, because that is very common in my experience. If they aren't building Angular for multi-team enterprise applications, what exactly are they building it for? (They are certainly advertising Angular as great for those, even if they are using it as an excuse for why Angular isn't performing well in Google's own usage of Angular.)
Large companies have large company issues regardless of front end framework.
Anecdotally, having to profile the performance of apps I've built on Angular and React I'd much rather be profiling a React app than Angular any day of the week. I got so frustrated with Zone.js at one point I wrote an entire "Component Framework" for Angular to avoid Zone.js as much as possible and try to remove Zone.js entirely as a dependency in Angular apps that I need to profile.
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.