Why Angular Is the Better Choice for Long-Term Projects

Thanks for sharing this.

I'd like to hear more from you about the specifics of Angular that work really well in an enterprise (at least, large complex flagship saas webapp) scenario, and how you overcame specific Angular challenges? I hear many negative thing about Angular, but I really just wonder if there is misunderstanding about how things should be done.

If that's not something suitable for a casual HN comment, perhaps something like this would be a good blog article.

Faced with a technology decision, it's been interesting reading what people on HN say about React/Svelte/Angular.

What I seem to read around here is that React is great and simple until it's very large, and you could pay a high price later on if you make poor decisions early. Lots of complaints about complexity in a large codebase, telling me that architecture gets tricky especially with many vendor libraries.

Angular is talked about with disdain mostly, steep learning curve and lack of JSX. That could be a feature or benefit. You don't need to reinvent the wheel or architect everything as there's a strong structure in place, but you have to understand and do everything the prescribed way. What I want to know more about is once you have the right practices in place, how good is it to work with? What compromises and unsolvable issues remain once you get to a significantly large application?

Svelte has a very positive reception, but I'm not sure there are many 'enterprise'-y success stories yet and obviously specialists/talent will be rarer.