So I don't think there will be horror stories with Angular 5 for new projects, unless you just don't like Angular/TypeScript. It's definitely not like "going the wrong direction" from Angular 1.x, although I don't personally have any read on how it compares to Vue, or React, or Aurelia or what have you.

I also haven't gone through a 1.x→modern transition (yet), so I can't really speak to that, but in preparation for doing it I've read everything I can, on this forum, various blogs, etc.

I'm not looking forward to it, but on the other hand part of me thinks of course it's easier, or at least more fun, to move to something like Vue, because it's like a rewrite, or half-greenfield project.

It's almost always more fun to rewrite something, although usually not advisable from any other business perspective.

We don't see as many people talking/blogging about Angular anymore, but I think that's mostly because it's gotten boring. Which can be a good thing.

Thereafter though, they have been just relentlessly polishing, improving, smoothing rough edges, making bundle smaller, making compilation and execution faster, etc. It is really a model of exactly what you would want, in terms of a joint respect for backward compatibility with forward progress.

I don't understand the "haters" in some peer comments. There are certainly interesting things to consider in terms of feature and approach differences between Angular and its competitors. You could certainly find bits where a simpler approach taken by one of the competitors is a quicker learning curve and smaller size.

But at the same time Angular has a substantial feature footprint, it has significant swaths of functionality that the competitors don't address. We've been using (leveraging like crazy!) the Angular forms system. Many enterprise and non-enterprise applications have lots and lots of forms. Not forms in the trivial sense of, some controls on the screen. Complex interconnected behavior. Angular brings a lot to the table here.

I like React because it's easier to set up and get working; you don't need some ridiculous dev environment just to say "Hello world". I think React does one thing and does it really well, and its flexibility makes it easier to mix and match packages to do what you need to do.

Angular is ridiculously opinionated, and very complete. But for big projects or for multiple projects with different people coming in and out of the project this can be a strong asset. We've had some big React projects where you have to go out and get Redux, then start thinking about observables, maybe you want TypeScript but maybe you want Flow, etc. Angular already thought about all of that, made decisions for you, and structured it in a standard way so that once you learn the conventions it's pretty easy to reason about any Angular project.

And as a front-end dev who got started on the Web in the Netscape days, I appreciate that Angular doesn't treat CSS as a bug to be fixed. React (and the kinds of people who work on React) seem to desire a pure JavaScript world, while Angular keeps a more familiar HTML/CSS convention on the template level.

Quite happy so far.

That being said, it's still a big improvement over everything else I've used that isn't React or Vue.

Angular 1.x interop seems like the only compelling thing about it in my opinion.

There are certainly some issues with Angular. For example, starting Webpack Dev Server is really slow (a minute or longer). Running a lot of tests with Kharma can be slow. If you know what the issues are and can either live with or work around them, then it is not that bad.

React and Vue are reasonable options, but as someone using Angular in production I'd urge you to stay far away from Angular and TypeScript.

I was initially very curious about Angular2, but our relationship ended very quickly with the discovery of modules and dependency injection. It feels like some kind of arcane over-engineering compared to React's (and vue's) simple and sufficient import-and-use model.

I work in a large corporation and they're still planning their transition to 1.5 and then to 2. I'm keeping up by building stuff in my off time, but trying to keep a fortune 200 corporation on a six month upgrade track? Not happening.

I've already heard rumblings from upper management of going back to some open source Java frameworks like Spring MVC, Vaadin or gulp Struts because of how fast they are releasing major versions and the time and cost of keeping up.

My fear is Angular will be regulated to startups, medium sized businesses or small autonomous business units within larger companies. When faced with a six month upgrade schedule, many larger organizations I fear are going to balk and just drop it in favor of something they are already comfortable with. . ergo my company wanting to go back to Java since 95% of everything built here is done with Java.