Angular 2 and the Problem with Exciting New Technology
Disclaimer: this post will contain technical jargon, so my non-techie readers, I recommend you skip this one. As a JavaScript developer, my favorite working environment for the last 2+ years has been AngularJS -- a framework for building Single-Page Applications (SPAs). Almost as long as I've known about AngularJS, I've known that while the current version is 1.x, the team has been working on Angular 2, which will include many breaking changes. Well over the past two or three weeks, I've been working to make the transition to Angular 2 just in time for the new release. And last Wednesday, it happened. Angular 2 is officially out and this is anticipated to become the new standard for JavaScript single-page apps. On the surface, it's extremely impressive and cool. But it is vastly different. I never could have guessed just how different it would be. Angular 2 uses TypeScript (a superset of ES6) which is compiled to JavaScript, so I'm not touching the Jav
