[thm76]

I find the dev experience of Angular very frustrating, and many things seem overly complicated or not very well designed, in my opinion. That's why I would choose something else (anything, really)

However, if it was noticeably faster than alternatives then I would just deal with those frustrations, personally. User experience (including speed) trumps developer experience.

[EugeneOZ]

DX in Angular is great. With Nx is even better.

Prove me wrong with the examples, please.

[cuddlecake]

I'd be more interested in why you think DX in Angular is great (especially with Nx).

[EugeneOZ]

If my opponent will name some struggles - I will try to help, will try to show the way how to resolve them.

[Klaster_1]

As an Angular developer, I find these DX issues mildly annoying:

1. Slow rebuild times.

2. Takes a long while to start a single unit test suite, using the default Jasmine setup.

3. No HMR.

4. Very awkward router API.

[EugeneOZ]

HMR is here since v12, stable since v13.

Test and, especially, builds time issues can be greatly reduced using Nx - give it a try. In one project (~400 components/directives) we’ve reduced the CI cycle (lint, test, build, deploy) from 50-55 minutes to 2-7 minutes. I know it sounds too good to be true, but there is no magic behind it: you can read how “nx affected” and remote cache works. It's basically free to use, we are using a free tier for every project.

One more thing: with Nx, it’s much easier to generate libraries, and you don't need to rebuild them to see the changes. Because of that, most of the code natively and without friction moves to libraries with time.