TLDR - I should have just written a blog about it. I use Angular a fair amount. I don't think it's any worse than your other UI application options. It certa

TLDR - I should have just written a blog about it. I use Angular a fair amount. I don't think it's any worse than your other UI application options. It certainly isn't great, but I wouldn't call it terrible. I've read through a lot of comments here, and I've also spent many an hour struggling to understand why my application isn't working, both in Angular2 and Angular(1)JS. I wrote a reasonably well-received, and now slightly outdated blog on using Angular2 with docker-compose (that's right, I'm all up on the hip tech). My least favorite part about writing an application in Angular2 is the rate of change in the framework itself. It can call itself stable, but is it really? Hard to say, since it's only been "stable" for a small number of weeks. As others have touched on, however, this is not a problem peculiar to Angular - it's more a broader javascript phenomenon. Everybody in the JS world is bumping versions like their lives depend on it. And it's not without its benefits either: At Angular2-RC1 I tried and failed to use the `ngc` tool for production builds with tree-shaking and minification. Suddenly, when I updated to RC-6, that process began to work. How exciting! This turned out to be mostly for nought, because today angular-cli (ng) takes care of most of this for you. The cli itself is still "beta" (some would argue that so is the framework, if not in name), but it can generate much of the necessary typescript boilerplate, and it does passable builds for dev and production with a single command. All this has happened in the span of about 4 months, so the rate of change has in this case brought welcome improvements. Source maps are generated as well, and error messages are helpful for the most part. I have not used React, so I cannot make that comparison. Angular has many quirks (and problems!), but with angular-cli the learning curve for building and running gets a lot lower. The biggest issue is that the user-base is divided among those who are still using SystemJS, or using Webpack directly (ng uses Webpack under the hood now), and the the rate of change prevents documentation from keeping up. Also, yes it's very slow (angular-cli, not angular itself). It has a million dependencies. But my front-end application is actually organized, and significantly more readable in my opinion than any Angular 1 app ever was. I can't go back to jQuery for DOM manipulation - 2-way binding is like crack to me. And Observable streams make it even better. As ever, I like it well enough, and everyone else is free to have another opinion.