> It rather makes me worry it is going to be the Python 3000 release all over again in terms of how much is changing.
The underlying technology is changing so fast (ES6, web components, mobile web, etc.) that it's going to make upgrading an obvious choice even if it involves relearning a lot of stuff.
couldn't agree more on the Python example, I think one of the main agendas for the 2.0 release will be to make it more popular on mobile side of things (https://www.airport-parking-shop.co.uk/blog/built-app-2-week... is one such example though not from the core AngularJS team) for which they may have compromised backward compatibility infavour of performance.
and also do you think they'll continue with the 1.x releases? since so many developers have already invested time and effort on their webapps and shifting it to an entirely new framework (read release) is a major cost to pay..
They say the exact plans for how long they are going to support 1.x won't be finalized until after 2.0 gets released, so that they have some idea of how difficult it's going to be to migrate.
The underlying technology is changing so fast (ES6, web components, mobile web, etc.) that it's going to make upgrading an obvious choice even if it involves relearning a lot of stuff.