Earlier quoted context omitted.
That's not my experience based on two scenarios: 1. Server-side rendered sites in Python using either Django or FastAPI/Jinja2 and htmx; 2. Dotnet back end with Angular front end. In practice - for the apps I've been involved with - option (1) provides a more than acceptable user experience. There's no doubt Angular can go beyond the capabilities of SSR+htmx. But, in practice, it's in the long tail. Throw in the odd…
Not sure you've solved the complexity when you've just slotted in another front to a general solution that is over-engineered. You could have replaced either scenarios with a single NextJS or SvelteKit solution. Go above and beyond in "complexity", write your Node backend (keeping it one language, JavaScript), and use vanilla HTML and JS to consume that. To me, htmx isn't as revolutionary as people make it out to be,…
But then I would be using only JS. I want a backend to be something else so that I don't go insane.