this post was submitted on 02 Dec 2025
266 points (98.5% liked)
Programming
23690 readers
260 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
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
> Uses JavaScript in 2025.
> Complains about enshittification.
JavaScript was built for the web. That's fine. It's corporations that took it out of its comfort zone even when better alternatives emerged.
Eh, it’s fine. It has some bad choices baked into it, but what language doesn’t? And JS in 2025 is miles better than JS in 2005.
I wouldn’t choose it for every project, but it’s a reasonable choice in many cases.
The fuck else am I supposed to make websites with, rust compiled to WASM?
It’s my opinion that the modern web is massively enshittified, and was so long before that term came into play.
Too much focus on flashy (and often obstructive) presentation, constant reinvention of the wheel, and no regard for the actual information being delivered.
I mean, you mention “semantic markup” to your average web developer and they just stare at you blankly. They’re like the seagulls from Finding Nemo: DIV? DIV! DIV!
Useful information structures? Meaningful metadata? Consistent patterns? Forget about it.
HTML and JavaScript are part of the problem. They provide too much freedom and not nearly enough structure or guidance.
And even if you put all that aside, JavaScript is an abomination that is entirely unsuited to the purpose it’s being used for. Ask any JS developer. Or look at how many ridiculous frameworks have been slapped over the top of it in a vain attempt to address its inadequacies.
Ok that’s great but I need to eat
Hey! Sometimes it mostly works, and that's all I can reasonably ask for anymore.
It is only used because it is the only available option on web. Don't bitch me about webassembly when it is missing half of the api and doubles up page load time.
WASM is that much slower? I get that needing a f*** Js wrapper to be able to use the DOM cannot be good, but is there really that much of a difference?