Angular, TL;DR

2018-10-22 Last modified on 2021-05-24

I have written a few things about Angular in the past here. I have finally been able to work with it professionnaly, so here are a few thoughts about the framework and what is around it.

In the end, working with Angular was interesting, and I think Angular is a contradictory framework.

Angular has everything to be accessible (CLI, TypeScript...) but mixes it with advanced concepts that may make junior devs lose their minds; concepts that are sometimes overkill for nothing (like observables).

⚠️ I write a lot of stupid things.


I followed the SFEIR School training 3 years ago and it was sweet.

Before starting the projet, I read the ebook Become a ninja with Angular, it is an amazing resource.


We can code in Angular using ES5 or ES2015, but it is not easy. The inevitable tool is TypeScript.

I wrote before that I do not understand TypeScript. I changed my mind a little bit and I found that it was nice to use. I am still convinced that there are better tools to answer the problem it is trying to solve, for example Flow, which is in my opinion a way better match for JavaScript lovers.

Modules and components

Today, we can not live without components. All frameworks work like that. Angular allows to create modules to split the application.

Splitting the application is nice. Having to link all components at the root of the module, it is not (even if the CLI does it for us).

I love the idea of Angular Elements, but I have not used them.


The CLI does not leave the choic of the architecture to the developer.

A nice tweet from Dan Abramov is always welcomed. About a discussion about file organization, he released this and here is his advice:

<blockquote class="twitter-tweet" data-conversation="none" data-dnt="true"><p lang="en" dir="ltr">It is a guideline though. It means literally “start by putting everything in one file; when it feels like it’s annoying, start splitting them up; what THAT gets annoying, maybe add some folders”.</p>— Dan Abramov (@dan_abramov) <a href="">August 8, 2018</a></blockquote>

The Angular CLI is interesting to help creating files and linking components in the modules but... For users of react or vue, where a component is imported directly by its parent component without having to declare it at the root of the components tree, it is not natural.

I like schematics though.


Following a tip from some co-workers, we used NGXS to handle our application data.

I have been working with other frameworks — React with Redux[^1] and Vue with Vuex — and I found NGXS being incomfortable. It was complicated to make everything work with the documentation only.

An action corresponds to a class instanciation... Why make things simple when they can be complicated ?

[^1]: I like the idea and pattern Redux leverage, but I am not a fan of the way to use it. I may talk about it later.


I had no problem with that using Angular.js when I was young, even if some co-workers thought is was too « heavy ».

In Angular, it is even worse. Setting up tests is unbearable to keep on respecting the Holy Grail of Dependency Injection. Tests are easier to write when using react or vue.


Observables exist for a specific usage, and Angular uses them for everything.

I often speak about using the right tool for a specific usage, and the Observables for everything is an obligatory « no thanks ».


Forms are nice to do, because Angular makes things easy. Maybe it would have been useful to make things a little more «difficult» and leave more things to be handled by the developer.

Validators are very handy. I used to work with them with Angular.js thanks to this article, and I found the same joy to make weird things with Angular form validators.