October 23, 2018 · 4 min read
Some people may think that being opinionated is a bad thing but it can be a huge productivity booster, especially when working on a team. There is usually an “Angular way” to do things, laid out in the Angular Style Guide. This is invaluable when working on an application. The style guide covers everything from how your project should be structured to what naming conventions you should use. Angular being an opinionated framework goes a long way to reducing decision fatigue.
Speaking of decision fatigue… it can be a real problem when working on a project. While it can be nice having the ability to choose all the different libraries you are going to use in your application it can slow you down significantly while trying to weigh the pros and cons of said libraries. Since Angular is a “batteries included” framework it includes all the pieces you will need to build a significant application.
Forms in Angular just work. There’s no complicated setup and no need to create event listeners to update the values on each input. You just tell Angular what fields are in your form and what validators (if any) the field should have. Yes,it also comes with validation! If you plan on building an application that uses forms heavily Angular will make this a breeze.
A framework is only as good as the community that surrounds it. The ease of finding learning resources or the ability to find help when you get stuck are important considerations when picking a technology. The Angular community is about as robust of a community as you will find. There are countless conferences, articles, books, tutorials, podcasts, and courses covering every aspect of Angular. Community leaders are accessible and willing to help. This can be helpful if you need to get un-stuck.