Almost every problem I've seen with Angular involve people not knowing how to implement features correctly or using it for what it wasn't meant to be used for. You know, the same problems people have with all frameworks.

The problem is there's so much you need to know. Angular invented a custom feature with plenty of boilerplate for every task -- and if you want to do something that Angular doesn't explicitly support you'll end up fighting the framework very quickly.

Use things like Svelte. It's a framework that lets you hack. You don't need 'best practices'.

>It's a framework that lets you hack.

Translation: It's a framework that does less.

This isn't a bad thing if the things the framework does aren't terribly useful for what you want to accomplish.

why in the world would I want a framework that lets me hack?

"I've been working with Angular2+ for 3 years and I haven't met any bug."

Give me a break, this isn't true for any code in existence.

I work with GCC since 1996 and I never encountered a compiler bug. Whatever I wrote, the program always ran as it was supposed to run (even if it, more frequently than I'd like to admit, it didn't do what I wanted it to).

There is software that's incredibly solid.

I haven't met a bug related to the angular source code. I've obviously seen bugs in my projects