Hacker News Reader

Angular is too abstract / has a steep learning curve. You need to learn too many design patterns at once (factory, provider, service, singleton, pipes, directives, observable, component, container, dependency injection). Trying something simple is trivial, but trying something more complex is overly difficult.

View on HN

True, but you are learning ubiquitous programming concepts in about as well conceived of an implementation as you will get in a frontend scripting framework.

While none of the extra complexity is crucial to making a dynamic website, it earns its keep when you try to build a big online application. Why not just learn that stuff.

I think all the bundled pre-built functionality, like reactive forms, is the hardest part of Angular. That can be tedious to learn. But then again, so is 3rd party library X, so it's a wash.

Factories are no longer in Angular 2

I understand your point but to be fair, if we cherry pick all the terminology from React it also looks bad:

JSX, components, props, context, error boundaries, forwarding refs, fragments, higher-order components, container.

Once you add in concepts from the other libraries commonly used with React like mobx or redux I think the comparison isn't as clearcut.

Reply on news.ycombinator.com