Comment by EMM_386

> I think the problem is that SPAs are limited in use, but a lot of devs ONLY build SPAs and that creates a mess.

I am lead on an enterprise Angular project and among the reasons I went for it was due to the fact is is opinionated, but is doesn't get in your way. We're on Angular 16 now with a C# back-end and everyhing is going well, is logical, and performant.

Prior to this I was fully in the Microsoft ecosystesm, from ASP classic, through ASP.Net Web Forms, and through MVC.

This was the first project I decided to use a SPA front-end with, wanting to avoid Microsoft's latest Blazor push. It was too early to risk it.

SPAs have their place, and this is a large and complex system.

I agree that React is overused, it seems like it's the "go to" for many people, such as people who are either self-taught or went to a React-focused bootcamp. I've seen plenty of React sites that could be static HTML ... some of them could probably even get away with no JS.