[ajeet_dhaliwal]

A better approach is to spin off a new system and give it a new name

Great point. I think some developers or teams feel compelled to update the latest even if they are happy with what they have because using an older version number gives the appearance of being behind the standards and practices. In a case where changes take place to the extent that it makes the previous framework difficult to recognize or breaks compatibility in a big way, this pressure would ease if the new version just had a completely different product name, as in a way that's what it is anyway.

[Davertron]

Rich Hickey just did a great talk about this sort of thing at Clojure Conj: https://www.youtube.com/watch?v=oyLBGkS5ICk

[choward]

I agree mainly for googleability. It's really annoying searching for Angular 1 stuff and getting Angular 2 results and vice-versa.

[algesten]

Remember this behaviour is encouraged by the deprecation warning notices of npm. I want my project to compile cleanly, but without me changing anything, from one day to the next, I may face a bunch of warnings because some maintainer somewhere decided they have a fresher version (lodash, pug/jade, node-uuid etc I'm looking at you).

[joshmanders]

Change your npm log info to just errors. Warnings don't mean your build broke, just that the version of a dep you installed is no longer supported and if you want bug fixes to upgrade.

[jdd]

:clap:

[flukus]

It's because being on older versions limits your upgrade options. The further you get behind the more painful upgrading becomes.

You don't want to be in a position were you can't fix a bug because it's in the framework and you're several version behind.

There are also security issues with using older versions.

[joshmanders]

So then you're gonna have people looking at you and saying "ugh, Angular is old and outdated, you should be using ng-not-angular-but-newer-and-shiner!" and everyones gonna be upset that they didn't find out what the new versions name is so that they can upgrade to that.

[rk06]

If people have a hard time googling that info OR angular devs can't communicate that info well, then problem lies elsewhere.

Besides, the one reason, of using a different name is, to convey that it is a different framework just like others.