Summary

In this chapter, we considered the main reasons behind the lack of backward compatibility between AngularJS and Angular. We saw that the design decisions implemented in Angular were fueled by two things: the evolution of the web and the evolution of the frontend development, with the lessons learned from the development of AngularJS applications.

In the first section, you learned why we need to use the latest version of the JavaScript language, why to take advantage of web components and web workers, and why it's not worth integrating all these powerful tools in AngularJS.

We observed the current direction of frontend development and the lessons learned in the last few years. We described why the controller and scope were removed from Angular, and why the architecture of AngularJS was changed in order to allow server-side rendering for SEO-friendly, high-performance, single-page applications. Another fundamental topic we took a look at was building large-scale applications, and how that motivated single-way data flow in the framework and the choice of the statically typed language, TypeScript.

In the next chapter, we will take a look at the main building blocks of an Angular application, how they can be used, and how they relate to each other. Angular reuses some of the naming of the concepts introduced by AngularJS, but generally changes the building blocks of our single-page applications completely. We'll make a quick introduction to modules, directives, components, the new router, pipes, and services, and describe how they could be combined for building classy, single-page applications.