A Clean Start for the Web
I’m going to focus on one aspect of the article only.<p>&gt; <i>You might want to start with a lightweight markup language, which will ironically be geared toward generating HTML. Markdown’s strict specified variation, Commonmark, seems like a pretty decent choice.</i><p>Markdown of any form would be a catastrophically bad choice for something like this. Remember this: <i>Markdown is all about HTML</i>. Markdown has serious limitations and is very poorly designed in places, but it works well enough despite being so bad specifically because underneath it’s all HTML, so you can fall down to that when necessary. If you go with Markdown, you’re not actually supporting “Markdown” as your language, but HTML. If the user writes HTML in their Markdown, what are you going to do about it? You’re supposed to be able to write the HTML equivalent of any given Markdown construct and have it work, and I find that perfectly normal documents <i>need</i> to write raw HTML <i>regularly</i>, because Markdown is so terribly limited—so your document web is either (a) not actually Markdown and uselessly crippled (seriously, plain Markdown without HTML is extremely limiting for documents), or (a) actually completely back to being a subset of HTML, which is exactly what you said you didn’t want it to be (rule #1).<p>If you want to get away from HTML, you want something like reStructuredText, where you <i>don’t</i> have access to HTML (unless the platform decides to set up a directive or role for raw HTML), but have a whole lot more semantic functionality, functionality that <i>had</i> to be included <i>because HTML wasn’t there to fall back on</i>. I think AsciiDoc is like this too.<p>But the whole premise that “HTML must be replaced because it’s a performance or accessibility bottleneck for documents” is just not in the slightest bit true. HTML is fine. Even CSS is well enough (though most pages have terribly done stylesheets that are far heavier than they should be, e.g. because they include four resets and duplicate everything as well as overriding font families five times). The problem lies almost entirely in what JavaScript makes <i>possible</i>—not that JavaScript is inherently a problem, but it makes problems <i>possible</i>. The proposed variety of document web would be unlikely to perform substantially better than the existing web with JavaScript disabled.<p>All up, Robert O’Callahan’s response is entirely correct. You can’t split the web like this; you will fail. Especially: if your new system is not compatible with the old (which your rule #2 precluded), it will fail, unless it is <i>extremely</i> more compelling for everyone (rule #3), but I don’t believe there’s anywhere near enough scope for improvement to succeed.