Angular is also incredibly forward leaning. It has bright future and an exciting roadmap.
But what do you say when your boss asks if Angular is the right choice? What are its strengths? Stephen Fluin, a developer advocate at Google, sums it up well.
We’ve achieved a level of stability and a level of innovation that we feel really, really confident, solves a lot of the people’s problems and we’ll help them build better experiences and better applications for their users.
Specifically, when it comes to our enterprise users, I often talk about five reasons why they choose Angular.
First, we talk about how Angular is opinionated. We make a lot of choices for you. Things like TypeScript. Things like HP client that try and help you build more maintainable, more scalable applications kind of automatically.
Second, we talk about being trustworthy. We have very clear semantics so you know exactly what’s coming and releases. We’re also committed to very smooth update process between versions. This is something we’re spending a lot of time worrying about, all the way to the extent that for example within Google, where there’s more than 300 applications or projects using Angular, every time we make a breaking change, we actually have to go update those 300 applications. So we have an intimate knowledge of when and how breaking changes affect the ecosystem and so we’re highly incentivized to minimize those. But at the same time, we do want to keep innovating.
And it’s this idea of trustworthiness I think is something that we wanted to start building when we shipped version 2.0.0 back in September of 2016 and over the past year or more, we’ve kind of proven that we’re capable of doing that.
Third, we talk about Angular being scaled. We obviously design for solving kind of Google-scale problems. But that’s not just in terms of number of users or number of developers. It’s also in terms of a diversity of team roles. You see when we get large teams, you end up having a shared services org in the company or you end up seeing architects being distinct from developers being distinct from designers. And Angular is really designed with some of that thinking in mind, where you can have architects focusing on the module level. Where should we be lazy loading? How should we be building this platform? Developers more focused on the component level within a module. And then designers focused on the template.
And matches how people kind of want to build software.
So we’ve got opinionated, trustworthy, scaled.
Fourth, we talk about ecosystems. We have a fantastic ecosystem.
Just being at Angular Connect and hearing from people and talking to people, there are so many great companies that not only want to use Angular but want to give back to each other and work together
The last one that we talk about is Angular as being familiar. Whether you’re coming from AngularJS where we have a lot of the same philosophies, declarative templates, dependency injection services layer, even the components now existing in your JS. Or if you’re coming from a Java world or a .NET world, and you’re very used to this application mentality but you’re maybe new to the web, Angular ends up being a very familiar entry point to delivering the kind of experiences that customers expect in 2017, 2018 and beyond. source