It’s fascinating to note the turns HTML/CSS and JS #frameworks took

All abstractions becoming popular at around the same time

But while #HTML / #CSS frameworks peaked after the market had been flooded and the specs accommodated everyone’s wishes

#JS frameworks, fewer in number, ballooned into ecosystems, and sustain themselves by partially self-inflicted complexity

“The burden of proof is on you, frontend framework stans, not the vanilla Web!”—thank you, @jaredwhite

https://www.spicyweb.dev/the-great-gaslighting-of-the-js-age/

The Great Gaslighting of the JavaScript Era

The age of frontend JavaScript frameworks eating the web world didn’t happen simply because some well-meaning developers found great DX. It happened because we were fed a line.

The Spicy Web
@j9t thankyou!.gif I have a too much of an impostor syndrome to say this. I have worked on a web application with full state machine and event driven UI and whatnot when a simple <form> should have done the trick.

@jonr @j9t Not only would it have done the trick. The <form> is vastly superior because the <form> is semantic. A human, machine, or any combination of them working together can *interpret* it to interact with it how they need to.

All they can do with the React application garbage is execute it.