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 sent this to my workplace's Slack, in hopes that I'll never have to learn or write anything React in 2025. thanks for writing and sharing it with us!
@joshavanier Thanks, that's kind, but if my losing streak on this front is anything to go by, perhaps pin your hopes on someone else's persuasive abilities. 😅
@slightlyoff actually it's going quite well! the discussion has been opened and the team seems open to the idea of adopting an alternative framework; just gotta look at feasibility as unfortunately we can't stop the train to replace the engine at this point (not without irking clients) 

@joshavanier Remember: the important thing isn't the framework, it's the chance switching gives you to rethink architecture and values.

Bonne chance!