Why Angular Made Me Quit Web Dev

The guy's ranting about Typescript with no strong arguments to back up his diatribe.

He also described the experience of writing simple apps that resulted in very poor performance. From my experience, you'd have to really hard to re-create non performance scenarios. Especially if he is only creating simple use cases

In summary he is ranting about fairly superficial points that does not cancel out the benefits angular framework provides for certain types of organizations, when compared to vue or react..

I quite like Angular, it's a bit lite Django with batteries included. Very organized, TypeScript(!), reusable components, easy to write tests, create models, call Rest end-points for data, routing, make lazy loaded modules, scss and so on. Documentation is superb. It took me only a few days to learn and become productive.

I tried React but it felt very incomplete and to get things done beyond the basic tutorial I had to go all over blogs, articles and forums to find instructions (often incomplete or out-of-date). Still it required a complicated process to get data from a SpringBoot server (I was told I need to add Redux, then some other http library for the actual calls. Then try to tie everything together... well, I gave up.)

That was a year ago and I'm sure it's better now, but Angular at that time was very mature compared to the hackish React.

As someone who has been doing web dev for a long time, I find it interesting that I can understand the author's points, but that I don't relate to them at all.

For example, I agree that the angularjs to 'angular' transition was a bit wonky, but I don't understand having resentment or anger build up because I have to be a little more careful about how I craft search queries.

It feels like he's frustrated with a lot of things, and once you get in that mindset, each irritant takes on huge significance.

You don't start doing web dev because you really want to work with Angular, and I think that's the problem. You choose Angular because you think it will help you achieve an end-goal.

I suspect that he started working on a codebase that had already chosen Angular and he had no buy-in. In that case, problems become frustrations, rather than just 'things to learn'. For example, the documentation on the module system is pretty good. It covers the reasoning, shows a basic example, and then delves in for when you need more information: https://angular.io/guide/ngmodules.

Anyway, I enjoy working with Angular, but if something else works better for him, more power to him.