r/webdev • • Oct 18 '18

Angular 7.0.0 released

/r/Angular2/comments/9pbn4f/angular_700_released/
223 Upvotes

148 comments sorted by

View all comments

96

u/thatgibbyguy Oct 19 '18

Why is everyone downvoting people who are questioning Angular's upgrade/versioning strategy?

  • React is currently at 16.5 and the inital "major" release of this version (16.0) was back in September of 2017. So it's been over a year at a single "major" version.

  • Vue 2.0 was released September of 2016 and is currently at 2.15.17. So it's been over two years since a "major" version.

  • Angular 6.0 was released in May of 2018 and is now at 7.0 in October of 2018. So.... five months before a new "major" version?

Considering the debacle of "ng 1" to Angular and that incompatibility, it should be fairly easy to understand why people are side eyeing the release strategy of the Angular team. I mean, generally "major" would mean something pretty majorly different, and that just doesn't seem to be the case here.

78

u/DerpsMcGeeOnDowns Oct 19 '18

It’s just proper semver man. Nothing crazy. If there’s a major breaking change, it’s bumped. Simple.

-5

u/Arkhenstone Oct 19 '18 edited Oct 20 '18

And it's what bad actually. Too much breaking changes, it makes your code legacy in less than a year. Edit : I've been downvoted and I just see that my comment is not that explanatory. It's not really bad as for bad for everyone. In a small where development is not the core activity, a language that introduce too many breaking change is not likely to be a good choice. Because the development will be slow, the app will have an outdated language by the times it goes out. For example, I've got an app which I started to develop a year ago. With Vue, it's still Vue 2, I can deploy the app with the latest version without even caring about about upgrading. It's not about skill or whatever, it's just about cost.

3

u/DerpsMcGeeOnDowns Oct 20 '18

So upgrade it like a responsible human being.