I hear what you are saying, but I think the big difference between Angular 2.0 and (for example) something like Python 3 is that the goals and direction of Angular 2.0 are directly aligned with the future of the web whereas Python 3 changes were changes just for the sake of changes.
In other words, the world of the web is going to change drastically over the next two years regardless of what Angular does.
Now, I do think there are other approaches. Take Ember for example. They plan on building on top of all the new features coming out, but they are taking a more measured, iterative approach. The thing is that just because it seems like a good idea for Ember does not mean it is a good idea for Angular.
Look at it this way. If nothing else, it is really awesome to have two big front end frameworks taking two drastically different approaches to achieve a similar goal. There are merits to the Angular approach, but it all comes down to execution.
As much as I am rooting for Angular 2.0, it very well could be a train wreck. But, that is why I am planning on being an active participant during the entire process and I will do my best to make sure that doesn't happen.
While, yes, it is awesome to watch two big frontend frameworks take two different approaches, as a production user of Angular 1.x, I am nervous that "my" framework has taken the less iterative approach.
I hear what you are saying, but I think the big difference between Angular 2.0 and (for example) something like Python 3 is that the goals and direction of Angular 2.0 are directly aligned with the future of the web whereas Python 3 changes were changes just for the sake of changes.
In other words, the world of the web is going to change drastically over the next two years regardless of what Angular does.
Now, I do think there are other approaches. Take Ember for example. They plan on building on top of all the new features coming out, but they are taking a more measured, iterative approach. The thing is that just because it seems like a good idea for Ember does not mean it is a good idea for Angular.
Look at it this way. If nothing else, it is really awesome to have two big front end frameworks taking two drastically different approaches to achieve a similar goal. There are merits to the Angular approach, but it all comes down to execution.
As much as I am rooting for Angular 2.0, it very well could be a train wreck. But, that is why I am planning on being an active participant during the entire process and I will do my best to make sure that doesn't happen.