My biggest problem with Angular2 is how restrictive an obtuse the framework can be at times. I've ranted about it in other comments so I'll save space and just say that Angular makes easy things hard and difficult things nearly impossible once you step off the dotted line.

Also the lack of a really solid UI library has caused many headaches. Material isn't very configurable, PrimeNg is okay but somewhat buggy and poorly documented.

Aurelia will give you the flexibility you seek. Some UI toolkits now have integrations as well.

http://aurelia.io

have you looked at https://vmware.github.io/clarity/?

I have, but it has had datepicker as "shipping real soon now" for at least six months. Not confidence inspiring.

Wouldn't it be nice if UI components (and just as importantly, their styling) was decoupled from the JS framework they're implemented with. Some kind of markup language perhaps...

Do you have any example of something that is nearly impossible to do?

Angular its what you get when a bunch of java programmers with bad taste do what hey want. React-redux is really simple i don't understand why people have a problem understanding it. Please just make a little effort and use react. Angular is horrible and dead and if you use it some poor soul its going to have to maintain that legacy java weird mess.

>React-redux is really simple i don't understand why people have a problem understanding it.

I keep experiencing this. JS developers that should have no problem understanding redux's approach, throwing it away because they are unwilling to simply read redux's docs. It's disheartening.

Never tried vue ? I dislike angular hyper engineered DOM-OOP hybrid. Vue also fit the human-sized framework in a way.

Not yet. I've been burned with some JS frameworks before, so now I have the "Nobody gets fired from choosing IBM" mentality. I do hear some good reviews, maybe someday :)

Fair enough. Don't burn yourself for no reasons, if you're happy with ang2 than enjoy.

I think angular just makes more sense in larger projects. Imo, It has quite a lot of overheard that only pays off when working in larger teams.

> I think angular just makes more sense in larger projects.

I remember people saying exactly that with Extjs back in the days, with no proof whatsoever. Can you explain how angular makes more sense in larger projects?

> that only pays off when working in larger teams.

what makes it better for "large teams" ?

It always felt to me that the purpose of Angular was to give a 'large team using Java' type workflow to development, with the idea being that doing it this way you can just slot in a new angular developer when the previous one goes crazy and runs out the building screaming. But I've only worked on one Angular project, so this is a feeling on my part, not a well worked out theory of how it actually is.

I prefer having them decoupled because I can swap things out easily if I don't like them. Never touch Angular though but I imagine it should be possible to use other than the built in ones