That's the thing, I HAVE tried vanilla vs. React on the large scale, both in creation and in fixing broken (well, inaccessible) sites for clients. And React, Failwind, and hte rest of thist mental-huffing midgetry is in NO WAY, SHAPE, OR FORM simpler, easier, or promoting "faster time to market"

I have found such claims to be 100% bullshit lies. How is vomiting up two to ten times the code resulting in "less time coding?" How does increasing the depth of the build and deployment process speeding up develpment?

And unless you're blndly vomiting up copypasta of the broken half-assed off the shelf "examples" you're still "writing each line", you're just slopping more code in with all the dumbass presentational classes.

AGAIN, if people stopped spewing out 100k of HTML to do 16k's job, 500k of CSS to do 48k's job, and megabytes of client side scripting for NOTHING -- all because they don't know enough HTML or CSS to do ANY of this stuff -- MAYBE they wouldn't be suckered by the propaganda, bunko, and falsehoods that make these dumbass, broken, slower to develop with, and harder to use systems.

Faster to market my tuchas... and that's BEFORE we talk about what broken garbage they are from a UX and accessibility standpoint.

But then when people talk about "Enterprise web apps" my experience the past ten years says "Don't" because you're telling large swaths of users to go **** themselves, which is why much of my "consulting" involves going in and ripping out 90%+ of that web-facing scripttard JUNK.

Note, there are legitimate cases for such, but most of the time people are throwing it in where it just doesn't belong. Like normal everyday pages of normal content, payment systems, shopping, and so forth. Places that "apps" have not a single damned bit of business even being involved.