[ihsw]

I live and breathe Angular SPA applications -- the vast majority of developers that work with it cannot comprehend a well-designed and usable Angular application.

Proper error handling, sane state management, and keeping the codepaths short and easily grok'd is very difficult with Angular -- especially for larger applications. This results in blackholes where users find themselves in strange spots that are inescapable other than a full page refresh.

These are either developers dipping their toe into the front end after living in the back end of things their whole career, jQuery dudes hastily breaking into SPA development to stay afloat in an environment the submitted article exactly mentions, or simply lazy developers that couldn't be bothered due to tight deadlines/budget/whatever.

[wwweston]

Angular is popular enough that someone who could distill a reasonable set of concepts and practices for working with it could probably reap some significant rewards in the education/training marketplace.

But if proper error handling, sane state management, and keeping codepaths short are actually "very difficult with Angular," maybe it's not the comprehension powers of the developers using it that are falling short.

A framework should be actively making those things easy.

[ihsw]

That is correct, Angular leaves a lot to be desired. The tooling is just not there and the developer is usually left to do due diligence on their own.

React/JSX and TypeScript are a response to this and it's fair bit more pleasant when either of them are involved.

[rimantas]

I'd say it tells more about Angular than about developers.