I have an Angular 1 app I built in 2015 that's still in use today. Went back to it and it was refreshing in so many ways. A lot of people really hated it but i

I have an Angular 1 app I built in 2015 that's still in use today. Went back to it and it was refreshing in so many ways. A lot of people really hated it but it's opinions and structure helped promote a more maintainable codebase. I don't miss tuning watchers and the digest cycle though. All the React projects I've inherited are nightmares. I'm comfortable working on them but they are harder for junior and mid-levels to hop into. The number of ways to do things in React is a benefit and a curse. We had so much prop drilling early on. The idea that components should only have what they need is nice, but you need some data to flow to children. And when the UI needs to change on a prop drilled codebase, holy shit, refactoring is a major PITA. Luckily we have some alternatives to avoid the prop drilling but it's so fragmented. If something like Mobx was just part of React from the beginning, the ecosystem would be in better shape IMO. I identify with a lot of the issues the author stated. React is just at that place where you need a TON more discipline to produce quality code in a team environment. And because of that, there will be a mountain of shitty codebases in React to inherit, cleanup and maintain over the next 5 years. That being said, I'm still a big fan of React and Vue though.