I've come to understand what's happening in frontend's decade-long failure to deliver decent user experiences as a sort of epistemic closure. I'm calling it "frameworkism", and the epicenter is now React.

Here's a lot of words on why we should all reject it, and what the post-React world should look like:

https://infrequently.org/2024/11/if-not-react-then-what/

If Not React, Then What?

Frameworkism is now the dominant creed of today's frontend discourse, and it's bullshit. We owe it to ourselves and to our users to reject dogma and embrace engineering as a discipline that strives to serve users first and foremost.

Alex Russell
@slightlyoff Your articles are really interesting, thanks. As someone who is studying and getting ready to get his first job as a web developer I still feel like there's no way of not learning how to build SPAs with React, unfortunately. Just have a look on any jobs ads platform, on each and every job offer for either full stack or front end dev positions. React is always a requirement. From my current point of view, there's yet no way out of it, unfortunately. But it's nice to be aware.