[rolltiide]

How do you guys keep up with these frameworks?

You get stuck on one project or in one startup for 2 years and Angular has moved 6.5 whole number versions

all while the rest of the job market is confused but kind of tolerating why you jump around jobs so much

if I'm using Angular, my "side project" isn't going to be using a higher version of Angular every 6 months. Its going to be using React or something to see what I'm REALLY missing.

[tashoecraft]

Angular uses semantic versioning and adheres to it very strictly. Most of the time updating between versions merely involves running "ng update --all" and if that doesn't auto update everything you just see which items it errored for and update them. There have been articles showing how very large enterprises have updated their entire codebase in under a day.

If you're on one project or startup using Angular and you haven't kept up with the versioning that's a problem with the developers. There is no reason to be using a version lower then 1 back.

Features marked for deprecation will at minimum take 2 version to be removed, so 1 year after deprecation was marked. This isn't like Angular 1 -> 2 and I hope anyone who pays attention at all to front end will realize this. Complaining about angular versioning at this point would be like complaining that react bumped a patch version.

[rolltiide]

> This isn't like Angular 1 -> 2

I'm seeing that

Organizations are still supporting a transition from 1, "1.5" and 2

[qwerty9876]

Because angular versions are like chrome versions. 1->2 was a full rewrite, now the new major versions always have some small upgrades and even smaller amount of breaking changes, it's not a big deal at all to upgrade.

You don't really have to upgrade every time a new version is out btw.

[ng12]

React really hasn't changed much since React.Component was introduced. Some lifecycle methods were deprecated/replaced, and hooks were added. That's honestly about it.