3 ms·

idk; I've been focusing on all things javascript for the past two years, and I can relate to the "alienation" the author is describing. I mostly write vanilla (

by mattxxx 12y ago

idk; I've been focusing on all things javascript for the past two years, and I can relate to the "alienation" the author is describing. I mostly write vanilla (or +underscore) and AngularJS, and it feels like you have to constantly compare things, because so many of the workflows don't feel right. AngularJS scales really well on gigantic applications, and it felt like there was going to be some stability from the corporate-world, but now it's gone. Frontend code is so hard to maintain well (compared to backend), and now it's going to cost companies millions of dollars to migrate: retraining, migration, unit-testing, QA sigh...

Bahamut 12y ago
The stability will still be there - the first evidence of breaking changes was at ng-conf back in January, when Vojta presented about di.js. In addition, Angular 2.0 won't come out for over a year (I'd bet on 1.5 years from now given the tendency for timelines to slip - 1.3 was originally supposed to come out a year ago), and Angular 1.x will be supported for 1.5 years after that. That's at least 3 years of active development in 1.x. Meanwhile, the development ecosystem will probably have finally adopted Web Components and ES6 as the norm for development, and so it would give the perfect opportunity to evaluate options to migrate to then. Web Components looks hugely promising as the path for independent components - essentially what Angular directives were meant to be in the absence of such browser technology.