About enshitification of web dev.
Very much true what the author writes, even if the title blames javascript but then in a subtitle he says javascript is not the villain and puts the blame on misuse.
IMHO that possibility of misuse is the reason why javascript needs to have stricter reins.
Yep.
On a rare occasion I hit a website that loads just like “boom” and it surprises me.
Why is that? Because now we are used to having to wait for javascript to load, decompress, parse, JIT, transmogrify, rejimble and perform two rinse cycles just to see the opening times for the supermarket.
(And that’s after you dismissed the cookie, discount/offer and mailing list nags with obfuscated X buttons and all other manner of dark patterns to keep you engaged)
Sometimes I wish we’d just stopped at gopher :)
See also: https://motherfuckingwebsite.com/
EDIT: Yes, this is facetious.
Hahahahhah.
having to wait for javascript to load, decompress, parse, JIT, transmogrify, rejimble and perform two rinse cycles
This is whole sentence is facetious nonsense. Just-in-time compilation is not in websites, it’s in browsers, and it was a massive performance gain for the web. Sending files gzipped over the wire has been going on forever and the decompressing on receival is nothing compared to the gains on load time. I’m going to ignore the made up words. If you don’t know you don’t know. Please don’t confidently make shit up.
EDIT: I’m with about the nags though. Fuck them nags.
deleted by creator
Is “rejimble” a real word for a real thing?
Who’s the genius who named it that?
I made it up, but if be happy for it to be adopted.
Having 2 loads gives the illusion that it’s fast, aka. not waiting staring at something not doing anything for too long.
From a business perspective, isn’t it best to just yeet most stuff to the front end to deal with?
