Programming

21192 readers

242 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

108

JavaScript broke the web (and called it progress) (www.jonoalderson.com)

submitted 1 week ago by pylapp@programming.dev to c/programming@programming.dev

54 comments fedilink hide all child comments

About enshitification of web dev.

you are viewing a single comment's thread
view the rest of the comments

[–] luciole@beehaw.org 1 points 1 week ago* (last edited 1 week ago) (1 children)

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.