“Why not write Assembly then?”
Oh, here comes the genius motherfucker with the big-brain counterargument: “Well, if HTML’s so great, why not just write everything in Assembly, huh?”. Wow, look at you, you clever little prick. Did you come up with that all by yourself? Writing web pages in Assembly is like using a fucking scalpel to slice your overcooked steak: sure, it’ll get the job done, but you’re gonna look like a complete asshole while you’re at it. HTML just works, you absolute tool. It’s been the backbone of the web since Al Gore flipped the switch, and it’ll still be here long after your trendy framework is rotting in a GitHub graveyard. So take your smartass logic and shove it. HTML’s king, and you’re just a peasant with a keyboard.
🤣
💀💀💀
That’s the thought I always had: When I develop in Node, I stand on the shoulders of ten thousand microbes.
I’d like full stack developers to try something. Next time you have an itch for a personal project, see if you can make it with no frontend JavaScript. Just some CSS and HTML forms. All templating handled on the backend. Just try it and see how far you get. Don’t worry if it looks like a GeoCities page.
Then try finding places where JavaScript would make it more responsive or better UX in some way. Does the back button still work? Is it actually faster? Does it provide any benefit at all?
Maybe it does, but just try.
This can be fixed by switching from npm to pnpm or bun. They use hard links and a package cache.
This does not fix anything. Your final packaged code is the same.
