preface

When I started my career in the spring of 2016, Angular, as we know it today, did not yet exist; instead, I used to be an Angular.js developer—a long-forgotten framework that has now reached its end of life. While it offered interesting features and an opportunity to build more organized web apps, it did have some glaring flaws. This brings us to September 2016, when Angular 2 or, as it is known now, simply Angular was released.

This was huge! Everything changed at a moment’s notice: we now had TypeScript, classes everywhere, strict organizational rules, and, soon enough, even a dedicated CLI tool to manage over applications. Of course, this was overwhelming at first; however, upon further research, it was revealed that the framework is actually very solid and an immediate upgrade upon anything we had prior, and that was the moment when many frontend developers, including myself, fell in love with it.

Of course, this new Angular, like any other tool, wasn’t without flaws either: so began the process of continuous improvements upon the framework that we know and love. In the few first versions the framework stabilized, then in versions 8 and 9, we got a new rendering engine, and now we get a new phase of massive improvements that are often referred to (even by the Angular core team itself) as the “Angular renaissance.”