Also, to actually answer your question, the best practices I'm referring to include: - server-side generated pages on demand - a mature set of CSS-stylable HT

Also, to actually answer your question, the best practices I'm referring to include: - server-side generated pages on demand - a mature set of CSS-stylable HTML elements and form interactions that behave in a predictable manner without having to write code - templates that include little or in some cases no logic - the ability to View Source I've actually worked with React, in small bits. I've done several tutorials and they each required extensive Stack Overflow troubleshooting because something evolved. Code reuse can devolve into a holy war. I guess I find myself working on projects where you have your site templates - which is more of a visual/design language concern that isn't going to translate to other sites - and then you have your application functionalities that do the important things that people want to pay you for, and they too aren't going to be endlessly repeated. So I see a lot of journeyman devs putting energy into reusable components that don't make sense to reuse - and the ones that did ended up getting forked anyhow. What I have fallen in love with is Stimulus. It feels like the right amount of structure and interaction/event handling, with no attempt made to reinvent what HTML is. I don't understand why it's not more popular. When I look at what's actually in those button.jsx files, I'm floored by the idea that this is either easy to learn or simpler than just using <input type=button>. We also might have to agree to disagree about what constitutes easier to work with the DOM. I just don't find working with a hierarchy of nodes with properties to be anywhere close to the hard part of building a web application. And I've never built anything that needs to be updated in such a way that it strains a modern device to render it. Maybe if I was building GMail or a spreadsheet, but most people are not building that. People are starting new projects asking which JS framework they will use and not questioning whether they need one at all.