> Angular development is reliable. You know what you're getting

You get a product built on top of a framework which does 200+ things you never asked for, can’t disable, and whose the complexity of is reliably causing your simple code to crash in ways which are impossible to analyse, debug and explain.

I’ve been burnt a few times on this, and months down the line, my simple CRUD angular apps still have unexplainable, unfixable issues which is destabilising some of our backend systems.

And we can’t fix it. Because nobody has any fucking idea what goes on with Angular internals when shit blows up like that.

And yes, you can rely on that.

I’ll literally take anything not Angular over Angular at this point. At least I should be able to reason about what I’m shipping and fix bugs once reported.

May it die in a fire.

You'll get there eventually but a quick level up: it's only that way because you don't know how it works at it's base level and nobody will be able to fix it until they do. You have to spend the time digging in and if you don't then don't be surprised if it doesn't work, that's going to be every system you work on though. Not everyone has the time to put in when a new better framework comes out every 6 months. So I use old shit :D it still works and it's still fast and I know it backwards and forwards. Html and Javascript with a backend that generates all the shit so I don't need to make backend calls add socket io for loading stuff after the page is loaded. No framework except the server side, and that depends on the language. If you want to get really frustrated but level up super fast on multiple languages and frameworks? Install JHipster, and then change something. It's amazing how easy it is to break and what a giant pita it is to fix, but i do it all the time because you really gotta get in there and poke and prod until you figure out the problem.

I have none of these problems and I've built a ton of Angular apps. Angular does have a steeper learning curve for new developers but once you get past it, it is much easier to maintain a large application. React is the opposite-- it is very easy to get started but a general lack of opinionation and guard rails means that a project mostly built by junior devs will start to show cracks sooner.

The react app I have seen at my current work seems to use a different pattern per file which makes it nearly impossible to figure it out.

Plus the “any exception makes the screen entirely blank”.

>weird hierarchical "junior/senior" dichotomy

Will this ever end?