The revived No JS Club celebrates websites that don't use Javascript, the powerful but sometimes overused code that's been bloating the web and crashing tabs since 1995. The No CSS Club goes a step further and forbids even a scrap of styling beyond the browser defaults. And there is even the No HTML Club, where you're not even allowed to use HTML. Plain text websites!
The modern web is the pure incarnation of evil. When Satan has a 1v1 with his manager, he confers with the modern web. If Satan is Sauron, then the modern web is Melkor [1]. Every horror that you can imagine is because of the modern web. Modern web is not an existential risk (X-risk), but is an astronomic suffering risk (S-risk) [2]. It is the duty of each and every man, woman, and child to revolt against it. If you're not working on returning civilization to ooga-booga, you're a bad person.
A compromise with the clubs is called for. A hypertext brutalism that uses the raw materials of the web to functional, honest ends while allowing web technologies to support clarity, legibility and accessibility. Compare this notion to the web brutalism of recent times, which started off in similar vein but soon became a self-subverting aesthetic: sites using 2.4MB frameworks to add text-shadow: 40px 40px 0px hotpink to 400kb Helvetica webfonts that were already on your computer.
I also like the idea of implementing "hypotext" as an inversion of hypertext. This would somehow avoid the failure modes of extending the structure of text by failing in other ways that are more fun. But I'm in two minds about whether that would be just a toy (e.g. references banished to metadata, i.e. footnotes are the hypertext) or something more conceptual that uses references to collapse the structure of text rather than extend it (e.g. links are includes and going near them spaghettifies your brain). The term is already in use in a structuralist sense, which is to say there are 2 million words of French I have to read first if I want to get away with any of this.
Republished Under Creative Commons Terms. Boing Boing Original Article.
I host my own website, and I decided to rewrite the JS portions in React, in order to learn the framework. Boy was it a learning experience: To do the same thing required 2-4 times the amount of code—and that’s just in the scripts, let alone the all the bloat from the packages and the bundler.
I know this is a bit more radical than cutting out frameworks, but working with the JS ecosystem was such a pain, largely because there’s you need to piece together different software to make a stack work, which may or may not go together well. And since your stack is likely unique, good luck getting help on your problems. It made me miss Rust (albeit most languages do)—in Rust, you have Cargo for everything, and it’s beautiful. Rust has its own difficulties, but they actually feel surmountable compared to the dependency hell of JS.
React is probably overkill for most simple sites. You could still use JavaScript for some cool stuff without needing all the libraries and frameworks
The dependency hell of JS is caused by React. It's an ironic turn because node gained popularity in part because it was one of the first to have a coupled package manager with a massive public contribution model, full of a billion packages that follow the unix philosophy of "everything should do only one thing, and do it well" Dependency hell would disappear if people stopped popularizing competing swiss army knives. It's made worse by people trying to mash these swiss army knives together just to improve portfolio.
We've gotten to the point where you aren't considered a real professional unless you start even the smallest projects with maximum technical debt.
It should never be impressive that you used a tool. If the tool made programming it easier then it's not a mental feat. If the tool made programming it harder, then people should think you are kind of slow for using a tool that made development harder. This is why brag culture over what tools are used makes no sense. Just use tools that make life easier. If it doesn't make life easier, stop using it.
That’s fair, actually: my project had 2 packages in my
node_modules(not mypackage.json, total dependencies!) in vanilla JS, now it has well over 100. Unreal.They're just following the example laid out by the venture capital model, really.