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:
@slightlyoff I've being doing this for so long (#webdev). I have an inkling that everytime this conversation comes up and the person doing the "front end frameworks are killing us" cautioning - can't or won't actually recommend an alternative - it's because it will never be possible.
Not until the JS baked directly into the browser stops sucking so badly.
It's bandaids on top of wounds on top of bandaids.
> Not until the JS baked directly into the browser stops sucking so badly.
I've heard this before, and while I don't disagree, the goal post for "good js" always seems to be moving.
Granted it's been ages since I wrote front end, one big issue we had was cross browser compatible. It seems that's mostly a moot point. Yet the sentiment remains.
Alex Russell
Sherri W (SyntaxSeed)
Ukiah Danger Smith
Florens Verschelde