May 9, 2026
Web break-up era
Forking the Web
A rebel plan to rebuild the web has fans cheering and critics yelling “we tried this already”
TLDR: A developer proposed a stricter, simpler replacement for today’s messy web, hoping to make it easier to build and harder to exploit. Commenters split hard: some cheered a clean-slate rebellion, while others mocked it as a repeat of old mistakes that already failed.
A programmer just tossed a lit match into one of tech’s oldest arguments: what if the web got a do-over? In “On forking the Web”, Rodrigo Arias Mallo sketches out a cleaner, stricter, smaller version of the web’s rulebook—one that would be short enough to keep simple, versioned like software, and so strict that broken pages would simply not load. Yes, really. The dream is a web that is easier to build for, easier to understand, and harder for giant companies to quietly bend to their will.
And the comments? Absolute popcorn material. One camp was instantly ready to burn it all down and start over. Supporters called it “magnificent” and begged for a return to a simpler information-focused internet, with one commenter going even bigger and declaring that not just the web, but the entire internet, needs a privacy-first fork. That’s the kind of casual comment that makes a thread feel one step away from founding a digital republic.
But the backlash came fast. Critics basically said: nice fantasy, but successful projects always get bloated, and this proposal doesn’t actually fix the web’s real problems. The spiciest jab compared the strict “invalid pages won’t render” rule to the infamous XHTML debacle—a nerd-history way of saying, “We already tried being purists, and it went badly.” So the vibe is split between romantic rebellion and been-there eye-rolling—with a side of apocalypse humor.
Key Points
- •The document proposes an alternative Web specification, initially focused on reviewing HTML rather than all Web components at once.
- •The author argues the specification should stay simple and short, suggesting a compressed size limit of 1.44 MiB for the complete standard.
- •The proposal calls for strict semantic versioning so published versions remain stable and browser compatibility can be clearly defined.
- •It advocates an unambiguous formal grammar and says non-compliant pages should be rejected rather than rendered with error-correction behavior.
- •The article considers reusing parts of HTML for compatibility but notes that both HTML and XML may be too complex for simple parsing.