Chapter 6. Conclusion

There are many reasons why enterprises love Angular for building large-scale, nontrivial applications, and each organization will have a slightly different set of reasons for why the framework is so effective for their teams. It could be as simple as the Angular in TypeScript feels familiar to someone with extensive experience in Java or .NET. Or maybe the sanity that is restored by using component-driven architecture with state management that actually makes sense is just what the team needs based on previous forays into large-scale applications gone awry.

There are a lot of features that we have not even covered in this guide because, unless you find yourself on the fringes of an outlier use case, you will benefit from them without even having to think about them. For instance, we will probably never need to think about the new change-detection system that is three to five times faster than AngularJS unless we need to do something highly complicated. We will more than likely never need to touch hierarchical dependency injection and override it at a component level, but we could if we had to. Most will never need to write our own custom renderer for Angular, but it is possible and has been done.

The strength of the framework is that so many benefits just feel natural and almost self-evident to enterprise developers that they can go unnoticed. A developer who has never had to wrestle a large-scale ES5 JavaScript application to the ground while overcoming an entire lack of structure at the language and framework level, manual script management, global scope, state in the DOM, tightly coupled HTML and JavaScript, and so on will not appreciate how far the modern web has come. The fact that Angular is starting to look and feel like platforms that have been around for years and that enterprise developers can adopt with very little friction is a huge testament to the fact that the framework has done something remarkable.