I agree, I just moved us to Angular 13 and I love every second of it.
I've worked on React projects but will take Angular any day of the week.
Obviously the batteries included nature of Angular is nice. But otherwise I felt less burdened by the amount of code I need to write and read in react.
RxJS is nice though and testing via dependency injection as long as your app isnt a horrible mess and has good decoupling.
Today we still prototype mostly with react. It’s easier to staff junior devs around and empowers them when it comes to trivial logic with cool UX.
Any large scale work, or prototypes going to prod, do so with Angular. Where we’re confident in the Sr level engineers writing that code.
It's under MIT also which is a bonus depending on your use case.
I also think it's worth pointing out that people have very different understandings of what "very big projects" are. I think you mean projects with many different people working on it, in which case I agree, but often people misinterpret these statements thinking that their 1-5 person team working on a web app is a "very big project" because they have a million users.
It's insane to me that websites need to be compiled these days. My websites mostly consist of an index.html and a code.js, and then unzipping whatever goofy template into the js, css, images folders etc. I feel like requiring a fluent understanding of the entire node ecosystem build even the simplest websites is a big enough hurdle that a lot of enthusiastic new people are just going to give up and do something else.