This couldn't be more wrong. The team does a great job handling upgrade paths post 2.0.
First off, Angular versions post 2.0 are nothing like AngularJS/1.x -> Angular/2.0. They are much more incremental and even the two times the entire renderer has been re-written it was an incredibly gradual process over multiple major versions with seemingly few changes to component and template APIs.
Second, upgrading between Angular versions couldn't be easier thanks to angular schematics. The process takes seconds and for specific rarer exceptions the team maintains this fantastic guide here: https://update.angular.io/
> This couldn't be more wrong. The team does a great job handling upgrade paths post 2.0.
The problem isn't how it's handled or how incremental it is, it's that there are so many upgrades with breaking changes, at least that's what they're communicating to me with their version numbers. There's also the lack of any real LTS versions I mentioned, 18 months doesn't cut it.
> They are much more incremental and even the two times the entire renderer has been re-written
Telling me that they've rewritten major components that frequently isn't exactly convincing me of the stability, its validates my previous belief that it isn't stable enough.
When they've got versions that are supported for 5+ years post release I'd consider it stable. It doesn't matter how good your upgrade guide is when you run into a bug or limitation with the current version and realize that you have to upgrade the entire framework and deal with all the breaking changes to get around it.
Compare that to react where you've got at least 3 years (assuming they follow semver) between breaking changes.
React has some really painful breaking changes over the last 3 years - Angular did breaking changes in a far more user friendly way. The last breaking change that happened from 16.8 to 16.9 partially ended up resulting in us calling bankruptcy on our main app and helped make the decision easier to rewrite it from scratch on a team where the core members who worked on the app have over 70 years of experience amongst 4 devs.
Fair enough, but I'm not sure you understand how nice schematics are. You can use them for a lot of things, but one nice use case is essentially update migrations. You literally just run `ng update @angular/cli @angular/core` and a majority of the time you're good to go...
First off, Angular versions post 2.0 are nothing like AngularJS/1.x -> Angular/2.0. They are much more incremental and even the two times the entire renderer has been re-written it was an incredibly gradual process over multiple major versions with seemingly few changes to component and template APIs.
Second, upgrading between Angular versions couldn't be easier thanks to angular schematics. The process takes seconds and for specific rarer exceptions the team maintains this fantastic guide here: https://update.angular.io/