Rob Eisenberg

He wrote a blog post explaining his reasons for leaving: http://eisenbergeffect.bluespire.com/leaving-angular/ "I am not saying that Angular 2.0 is going to be a bad framework. What I am saying is that it is no longer fundamentally the same thing I was originally hired to help build nor is it compatible with my vision for the future. It is no longer the best path ahead for the existing Durandal community and it also isn't the best choice for anyone who has used my other frameworks and wishes to migrate to the web."

From: http://eisenbergeffect.bluespire.com/all-about-angular-2-0/ > So, it would seem that Google is heavily invested in the current version and will need to support it for a while. In a Q&A session at ngEurope Brad Green said that you can expect at least 1.5 - 2 years of support for Angular 1.3 after the RTM of Angular 2.0 becomes available If I am working on a long term project choosing a technology that will be supported for 1.5-2 years, would make me feel uneasy. But let's just pretend that the 1.x codebase will be so stable that it won't need support. What about the third party libraries that my project will depend on? Should I expect all of those to be maintained after Angular 2 is released? For real projects these are deal breakers. Recommending Angular for any serious project that is expected to be used for years is irresponsible.

I think it is pretty exciting, in a way it is about the migration off the desktop. Over the last year we have transitioned from WPF thick clients to a SOA with a SPA front end using Durandal. Using Durandal along with knockout felt very natural to us. We chose Durandal in a large part because it was written by someone that thought like us and leveraged years of desktop best practices and applied it to what we viewed as the "wild west" that is web development. Glad to see Durandal concepts will be making it into a great project like Angular [0], Hope it is a peaceful revolution. [0] http://eisenbergeffect.bluespire.com/angular-and-durandal-converge/

You're not really adding anything to the conversation. If you even did a cursory search as to the motivations behind why Angular 2.0 was a rewrite you'd learn that it has everything to do with compatibility with web components and ES6 and nothing to do with "money" as you say (I'll save you the two seconds of effort: http://eisenbergeffect.bluespire.com/all-about-angular-2-0/). In fact, it was a huge blow to Angular when they announced they would be introducing such sweeping changes to the framework. Remember that the web is a constantly moving target and assumptions you make today may no longer be relevant two years from now.

> There was a guy who joined the Knockout or Angular team (I forget which) since they had similar ideas for the future of their frameworks. Not too long later, he left them and restarted his project as their vision began to diverge. http://eisenbergeffect.bluespire.com/leaving-angular/

Here's[0] an article from the author of the OP defining the term. It just means "browsers that auto-update without user intervention". [0]: http://eisenbergeffect.bluespire.com/evergreen-browsers/

Just FYI, this post was partly inspired by the fact Angular 2.0 seems to be a mess of JS and Dart support via AtScript... Good reasons or not, the added barrier to contributions, and choosing yet another language that isn't JS still ultimately leads me to the conclusion many at Google don't believe in JS in the long haul, not as a language to write in. http://eisenbergeffect.bluespire.com/all-about-angular-2-0/

And 11 days later... > Several months ago the general direction of Angular 2.0 began to change in critical ways. I found myself fundamentally at odds with certain aspects of the proposed design. Still, I tried to keep an open mind and explore the various possibilities. Unfortunately, I haven't been satisfied with how things have progressed since then. At this point, there are too many irreconcilable differences. The Angular that's being built is not the Angular I signed up to work on http://eisenbergeffect.bluespire.com/leaving-angular

This was posted a few days after he wrote up a fairly long article explaining the direction Angular 2.0 was taking and the reason behind that direction: http://eisenbergeffect.bluespire.com/all-about-angular-2-0/

Also, for anybody who is a fan of Durandal... looks like it'll be combining with Angular: http://eisenbergeffect.bluespire.com/angular-and-durandal-converge/