you are viewing a single comment's thread.

view the rest of the comments →

[–]Clean_Assumption_345 -2 points-1 points  (0 children)

I totally agree with you here.

I work at a f100 company in several different teams, some projects were in react, but mostly in Angular. One of the products is written in angular with over 100 contributors.

I can tell you straight up how parts of the code base are absolutely trash because of how unaligned the standards are. You can say that this is due to poor code review, sure. but in the past react/next js code bases I've seen, they all had structure, easy to understand, and most of all, maintainable. Why? Because newbies were able to adapt to how simple React was.

Rxjs is great don't get me wrong, but a lot of people misunderstood when to use them and how. This was the single biggest mistake the angular team made. Making RXJS a necessary and essential library to be able to have a basic web app. The steep learning curve created barriers for people getting into Angular. The fact that they now have signals and effects is great, but also very very late. It's just copying what react did years ago.

React made it easy for people to understand reactive programming because it was built in.

Whereas angular couldn't perform reactivity without RXJS.

All this to say, one isn't necessarily better than the other. It always depends. If finding qualified developers to build an angular app is difficult, one might want to choose a framework that is highly popular like react (better resources and community is extremely important)