Chapter 1. Angular Follows Common and Familiar Enterprise Patterns and Conventions
Just a few short years ago, the rhetoric around frameworks was pretty inflammatory, with the general theme being “My framework can beat up your framework.” This negative dialogue was distracting at best, and at the end of the day, it was the end users who suffered.
There has been a distinct shift in thinking from “How do I make my framework win?” to “How do we make the web win?” This has led to some incredible collaborations between major frameworks and technologies that have produced some very powerful tools for everyone to use.
In this chapter, you’ll learn that Angular follows common and familiar enterprise patterns and conventions that support small teams as well as large organizations with several teams. These patterns and conventions include the use of the TypeScript language, a superset of JavaScript, and aspect-oriented programming using dependency injection. The use of TypeScript cannot be overstated; this is what enables the Angular framework to take advantage of tomorrow’s language improvements today. TypeScript is an open source project by Microsoft, and is created in collaboration with other open source projects and maintainers including Google.
TypeScript
The Angular team was originally going to create its own superset of JavaScript called AtScript so that it could have the tools it needed to create the kind of modern framework it envisioned. After researching the amount of effort ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access