Chapter 2. Get Going with Angular
On September 18, 2014, Google pushed the first public commit to the repository that now contains Angular. A few weeks later, at ng-europe, Igor, and Tobias, from the core team, gave a short overview of what were the expected features of the new framework. The vision at that time was far from final; however, one thing was certain: Angular would be an entirely different framework compared to AngularJS.
This announcement brought a lot of questions and controversies. The reasons behind the drastic changes were quite clear: AngularJS was no longer able to take full advantage of the evolved web and the requirements of large-scale JavaScript applications needed to be completely satisfied. A new framework would let Angular developers capitalize on developments in web technology in simpler, more performant, and productive ways. Yet, people were concerned. One of the biggest nightmares with backward incompatibility for developers is the migration of their current code...