The State of JavaScript in 2015
As someone who was drinking the AngularJS kool-aid, the merry-go-round joyride ended abruptly for me and my startup after the Angular team announced a lot of the updates they were planning, including the obsolescence of previous Angular versions at the ng conference in October.My partner and I had about 8 months of dev time into a directory app we were building on the MEAN stack. It just so happens AngularJS was a big part of that architecture.After some long conversations over beers and some teeth gnashing, one thing became clear. If the Angular team just decided to make these huge changes now, what keeps them from doing it again in the near future? If they have no plans now of making newer versions backwards compatible, does this means every new version will be this way? All it did was create huge questions of trust and reliability with using a framework which could dead end your project somewhere in the distant future. This meant continually looking over your shoulder, which is not good for any business.Our final decision was to scrap what we were doing with Angular and now are looking at several options which include:1 - going with a traditional .Net stack / MVC2 - going with Django or other Python framework3 - moving to another JS framework like EmberEither way, We're moving away from Angular. Call me gun shy, call me spooked by the latest change in direction, but I have a bad feeling about how this is going to turn out in the next 18-24 months.