4 ms·

How is this churn any different to other languages at the height of the popularity? Every other web programming language seems to have it's defining framework (

by yeskia 12y ago

How is this churn any different to other languages at the height of the popularity? Every other web programming language seems to have it's defining framework (whether it be a collection of quality packages or entirely first party code). From Rails to Django to Symfony to MVC, plus not forgetting that each language also has a popular "slim" framework also. I see no reason why that would differ in the JavaScript world - whether it be front-end or back-end. Angular's changes may have burned a lot of developers but it could just be teething problems - learnt some critical lessons on the first round and resolving them before it's too late. I fully expect to see a solid MVC framework on the backend, whether it's Sails.js or something else that comes along.

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.
sramsay 12y ago
Check out http://dailyjs.com/ http://dailyjs.com/ some time. Granted, it's devoted to all things JS (not just frameworks), but the number of libraries and microframeworks and plugins for frameworks is absolutely astounding. I don't remember ever seeing anything like this level of churn, and I've been programming since the early nineties. Not with Java, not with Python, not with anything. Someone above mentioned rolling their own stuff with vanilla JS (which provoked an immediate invocation of Greenspun's tenth rule). My sense is that a lot of people start out this way and say, "Lo, a library! Github!" One hopes that the cream rises to the top, but I'm drowning in milk.

by yeskia 12y ago

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.

sramsay 12y ago

Check out http://dailyjs.com/ http://dailyjs.com/ some time. Granted, it's devoted to all things JS (not just frameworks), but the number of libraries and microframeworks and plugins for frameworks is absolutely astounding. I don't remember ever seeing anything like this level of churn, and I've been programming since the early nineties. Not with Java, not with Python, not with anything. Someone above mentioned rolling their own stuff with vanilla JS (which provoked an immediate invocation of Greenspun's tenth rule). My sense is that a lot of people start out this way and say, "Lo, a library! Github!" One hopes that the cream rises to the top, but I'm drowning in milk.