4 ms·

Even with SemVer versions it looks really weird to see a new Angular relase branded as 4.0.0. Angular 1 to Angular 2 made me drop angular entirely, that happen

by aprdm 10y ago

Even with SemVer versions it looks really weird to see a new Angular relase branded as 4.0.0. Angular 1 to Angular 2 made me drop angular entirely, that happened less than 6 months ago I believe. Just reading Angular 4 gives me the creeps. Is 4 widely different from 2? How am I suppose to know if you using semver and already have a really bad history?

robwormald 10y ago
Most developers should be able to simply update their dependencies and rebuild. A few APIs have been deprecated, but they continue to exist and can be removed at a developer's leisure, per our versioning policy [0] http://angularjs.blogspot.com/2016/10/versioning-and-releasing-angular.html?m=1 http://angularjs.blogspot.com/2016/10/versioning-and-releasi...
- moloch 10y ago
  Lol, if only the real world were that simple. I have an Angular 2.4 project that when updated to 4.0.0 produces about 300+ build time errors (guess you can't access `private` members from templates anymore, it'll be fuuuuuun updating every component and template to work with "backwards" compatible v4), but basically every other version of Angular breaks your code so you just sorta have to live with it.
  - Nitramp 10y ago
    That didn't change between Angular 2 and Angular 4 - but maybe you changed your build process and are now running AoT with error checking? That would explain why your templates are now error checked and were not before.
    - moloch 10y ago
      Is that enabled by default in 4? I use and identical AOT build process with 2.4 and 4 (ng-cli) and there's no problems building with 2.4
jneal 10y ago
I've been testing out 4 since it hit beta, and haven't had any issues. Code literally just works after updating to the new version with 0 issues, in my case at least.
- alttab 10y ago
  How big is your code base and how many people work in it and how many paying customers do you have?
eloisant 10y ago
Angular 1 to 2 was a complete rewrite with a change of paradigm, but 2 to 3 then 4 is just because semver (i.e. there may be some breaking changes, it's not 100% backward compatible).
- gldalmaso 10y ago
  Yeah, but why? With all people complaining about Java, we don't have to deal with this shit so often. Most breaking changes I see on the JavaScript ecosystem seem like mostly cosmetic. It has been a rough road trying to make decisions on tech that won't get stale quickly and have support dropped in a 1-2 year frame. Angular is really one of the worst offenders in this regard. What was so fundamentally broken with Angular v1's api that could not just be worked internally and incremented? It also has ramifications which are pretty dire in my opinion. We have an app written with Ionic 1, so I go check out Ionic 2 see what's going on, and oh look such shiny things, how do we migrate? Nope, full rewrite of course. There are some decision makers in these teams which are completely disregarding the fact they are burning through several work hours of people around the globe without real value. Stop breaking things because new. Fine, use semver, but don't you change that first digit lightly, it hurts when you do.
bshanks 10y ago
I propose a variant versioning scheme that bumps the MINOR version for backwards incompatibilities and reserves MAJOR version bumps for subjectively "big" changes. http://www.bayleshanks.com/wiki.pl?proj-sanDiegoVersioning http://www.bayleshanks.com/wiki.pl?proj-sanDiegoVersioning
- robwormald 10y ago
  This is what the AngularJS versioning scheme was, nearly exactly. Everybody hated it. Hence, semver :)
  - bshanks 10y ago
    Huh, thanks for the info! Would you happen to have any hyperlinks to the discussions where people hated on the old scheme? I'd like to read up on this more.

by aprdm 10y ago

robwormald 10y ago

Most developers should be able to simply update their dependencies and rebuild. A few APIs have been deprecated, but they continue to exist and can be removed at a developer's leisure, per our versioning policy [0] http://angularjs.blogspot.com/2016/10/versioning-and-releasing-angular.html?m=1 http://angularjs.blogspot.com/2016/10/versioning-and-releasi...

moloch 10y ago
Lol, if only the real world were that simple. I have an Angular 2.4 project that when updated to 4.0.0 produces about 300+ build time errors (guess you can't access `private` members from templates anymore, it'll be fuuuuuun updating every component and template to work with "backwards" compatible v4), but basically every other version of Angular breaks your code so you just sorta have to live with it.
- Nitramp 10y ago
  That didn't change between Angular 2 and Angular 4 - but maybe you changed your build process and are now running AoT with error checking? That would explain why your templates are now error checked and were not before.
  - moloch 10y ago
    Is that enabled by default in 4? I use and identical AOT build process with 2.4 and 4 (ng-cli) and there's no problems building with 2.4

jneal 10y ago

I've been testing out 4 since it hit beta, and haven't had any issues. Code literally just works after updating to the new version with 0 issues, in my case at least.

alttab 10y ago
How big is your code base and how many people work in it and how many paying customers do you have?

eloisant 10y ago

Angular 1 to 2 was a complete rewrite with a change of paradigm, but 2 to 3 then 4 is just because semver (i.e. there may be some breaking changes, it's not 100% backward compatible).

gldalmaso 10y ago
Yeah, but why? With all people complaining about Java, we don't have to deal with this shit so often. Most breaking changes I see on the JavaScript ecosystem seem like mostly cosmetic. It has been a rough road trying to make decisions on tech that won't get stale quickly and have support dropped in a 1-2 year frame. Angular is really one of the worst offenders in this regard. What was so fundamentally broken with Angular v1's api that could not just be worked internally and incremented? It also has ramifications which are pretty dire in my opinion. We have an app written with Ionic 1, so I go check out Ionic 2 see what's going on, and oh look such shiny things, how do we migrate? Nope, full rewrite of course. There are some decision makers in these teams which are completely disregarding the fact they are burning through several work hours of people around the globe without real value. Stop breaking things because new. Fine, use semver, but don't you change that first digit lightly, it hurts when you do.

bshanks 10y ago

I propose a variant versioning scheme that bumps the MINOR version for backwards incompatibilities and reserves MAJOR version bumps for subjectively "big" changes. http://www.bayleshanks.com/wiki.pl?proj-sanDiegoVersioning http://www.bayleshanks.com/wiki.pl?proj-sanDiegoVersioning

robwormald 10y ago
This is what the AngularJS versioning scheme was, nearly exactly. Everybody hated it. Hence, semver :)
- bshanks 10y ago
  Huh, thanks for the info! Would you happen to have any hyperlinks to the discussions where people hated on the old scheme? I'd like to read up on this more.