Abildtoft

I think it is an unfortunate consequence of a new (relatively) poorly managed transition from AngularJS to Angular 2+, the latter of which should probably in hindsight have been named something other than Angular.

The fixed release schedule means that, at times, the "what's new" section is a bit meagre in the major releases, but e.g., the recent release of Ivy highlights that this is more of an artificial issue than a real one.

I'm personally very happy working with Angular and have chosen to use it even when provided the option of moving to React or Vue. Each of the major frameworks have their strengths and weaknesses, but I feel that we've reached the point now where their maturity is such that you cannot really make a fatal mistake in selecting either of them. Your use case and your team makeup is much more decisive.

They use semantic versioning. Their handling of the upgrade process, however, is one is one of their strong suits. In my experience, updating even medium to very advanced apps is often quite simple and well guided.

For more, see:

https://angular.io/guide/releases https://update.angular.io/ https://angular.io/cli/update