I truly believe that many folks in positions of power in web development don’t understand basic progressive enhancement.
Zach Leatherman 3535 replies 115115 likes88 reposts11 quote Original on Bluesky35 replies
We can save the optics of using the term “mind virus” for another time (but, gross)
I was about to say, that term tell you everything you need to know
also its very hard to sell someone vanilla HTML...
HTML is so enterprise scalable that it would win awards. 😅
if that's who I think it is, it's a great example of a CEO managing to *un*evangelise their service
You get the sense that the austerity he's worried about might be in the area of overpriced cloudflare resellers and their slow, proprietary APIs.
Maybe he’s excited for someone’s approach for dealing with the competition by rabble rousing
At the brochure-site level everything is design driven. Progressive enhancement means that sometimes it won't look like what we sold the client. That's a tough thing to explain up.
Yeah—but folks aren’t arguing for HTML *only* as that quote suggested
Oh for sure. Everything in moderation. That's why we have all three languages to use.
Summarizing folks' well-informed sentiments about the measurably poor user experience of react sites as a whole as 'don't use JS' is a pretty lazy read. 🙄
They think "don’t use React" means "don’t use JavaScript" because they never learned or they forgot how to do JS without React. They think React == JS.
I am once again reminded about your sentiments about binary thinking
100% 🫠
same tweet rephrased every day 😅 bsky.app/profile/scot...
it’s only been 15+ years of saying the same thing (correctly) 🫠
Well, the recent changes to popularly prioritize server-rendering tells me the work is working! It's just slow because the message runs counter to so many business and developer conveniences, and genuinely a lot of our industry isn't familiar with working any other way now.
i think they do but it puts their business model at risk, so they gaslight instead
I’m sure it’s unrelated to some survey results that came out today (though I have complicated opinions about those too)
i have not yet looked at the state of the fellas results yet
I’d go further and say there’s a contingent that doesn’t really understand the grain of the web at all. I think there’s a chunk of the industry that came in several years ago from more conventional software backgrounds and never really gained that understanding
What is the grain of the web in 2024? I ask because I want to know if might need to update my definition which I aquired in early 2000. As for that cohort, I won't deny that there is a large pool of developers that don't have that background and to them React is JS, the web is React...
but some are seasoned application developers and they find the 'document-based' web lacking in that context... they think in apps, big, fat apps and not just islands of interactivity.
I don't really think the grain of the web has changed in any significant ways... it's still progressive enhancement, URL behavior (e.g. using links vs buttons), etc.
In many ways, it's an understanding that HTML+CSS+JS+SVG is itself a framework and how to work idiomatically within that framework.
In the context of working in larger organizations that create a lot of apps (B2B) there is a LOT of value in using a popular web framework. If an organization doesn't use one, someone will create their own and at that point, more often than not, you'd want to run for the hills.
Oh I definitely agree.
There is a lot of value in using a popular web framework, but I think part of that *should* be understanding the underlying web framework it’s built on top of as well.
Some (though not necessarily all) of the ire aimed at React, for instance, is really a gripe with devs who use React but don’t fully understand the web framework. These are not strictly problems with React at all, but React becomes a lightning rod for those frustrations.
Yeah, it's the same on the backend side... "hey, I know Django, I must be a great Python developer" :)
Well and all the broken middle clock because the framework is creating links through JavaScript. Oh and it’s slow af.
The framework doesn’t “make links through JavaScript”. It renders whatever HTML the developer tells it to. If the dev is using event handlers instead of native links, the dev’s own fault
It’s what the docs (at least previously) showed in tutorials and made the easiest.
My question: have these people in power ever before openly acknowledged there is a theory of web development other than their own React/whatever one?
Is this sort of snipe at normal web dev new? Or are such snipes becoming more common?
If so ... we're getting somewhere. They're on the defensive.
yeah, definitely has the air of losing control of the narrative
I am getting the same feeling from other things I'm seeing. So ... yay, I guess?