Alex RussellNov 30, 2024

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
Show threadnickchomeyNov 30, 2024

@slightlyoff

Tremendous article, as always. Thanks for all you do.

"Graciously accept the resignations of PMs who decide managing products is not in their wheelhouse."

I can understand the devs, tech leads etc who are part of frameworkism. But what role do these sorts of PMs even currently play, given that, in some sense, their role should be framework-agnostic...?

Do I just not have a proper conception of what a PM does? Or did the mass layoffs get the wrong folks...?

Show threadAlex Russell
@nickchomey Being a rubber stamp is easy! And there are always more meetings to go to and decks to construct and offsites to lead and bug backlogs to triage. Those things *could* be part of managing a product, but it's also possible to do all of them and not manage anything affirmatively.
Nov 30, 2024 at 6:12amWeb
Show threadnickchomeyNov 30, 2024

@slightlyoff

gotcha - the issue is not that the PMs are explicitly frameworkists themselves, but that they're not actually managing/holding to account the frameworkists.

(Which, I suppose, makes them frameworkists...)

Thanks!