When should AngularJS be used

The 5 main advantages of Angular and TypeScript

Maintainability

I love open source projects, but I can also understand that people or groups who lead such a project have to deal with other aspects of life and that some projects can no longer be sustained. If you have worked with open source software projects for a long time, you may know the relevant backgrounds and stories. Whenever I consider a project for myself, I look at the number of contributors, see when it was last updated, and review the issues to see how regularly they are dealt with. I try very hard to only use and recommend projects, modules, libraries, etc. that are actively supported so that my projects and those of my clients are easier to maintain and up to date.

A dedicated team at Google Building Angular in combination with the open source contributions from the community is a HUGE selling point for me personally. In today's JavaScript world of “Flavor of the Day”, of course, you never know what will come tomorrow, so the solid foundation that the framework supports gives me a lot of confidence. Another bonus is the fact that Google uses Angular within its own company when developing applications. Perhaps by now you will think the same is true of React ... and you are correct. However, I would like to focus on Angular here.

You may also think: “But Dan - the jump from AngularJS 1.x to Angular 2+ was huge and definitely not good for the maintainability of our app!” Yes, that's a valid point - even with upgrade options. The jump between AngularJS and Angular was a direct result of the JavaScript language, which made tremendous advances in ES6 / ES2015 functionality, combined with new features that modern browsers can now support. If the Angular team had NOT made that leap, we would be referring to Angular as the "Caveman Framework" in no time because it would not leverage the latest and greatest of features that support performance, consistency, productivity, maintainability, and overall development. I was happy when the Angular team took this step. Of course, I don't have a crystal ball to look into the future either (if someone has one I'd love to borrow one), but I know that the Angular team knows very well how changes to the framework affect company projects (especially since Angular is also often used by Google itself). Based on what I've heard, I'm confident that releasing new versions will have less of an impact in the future.

In addition to the solid support that Angular receives from the Angular team behind the scenes, the consistency in the code described above also makes it easier to maintain. In my career I've had many years of support (I even used the good old pager for many years), so I understand the importance of consistent and easy-to-maintain code. Of course, a team can use any framework with the right style guide, training and knowledge for uniform application development. This not only applies to Angular, but also to many other frameworks. However, Angular provides a very clear way of writing code, which ultimately leads to simplified maintenance. And when contacts go on vacation (or change jobs), colleagues can easily fix errors they find or process change requests without further ado.

Angular Code can be written with TypeScript (my preference), which has a number of advantages for businesses. In the chapter "Early error detection" I will again go into Typescript and some clear maintenance advantages.

Regardless of whether your team provides support for an application themselves or this is provided by another team, the possibility of creating applications that are consistent and easy to maintain and that use a framework that is supported by a full-time development team in combination with a Supporting a robust open source community are key priorities for most organizations.