Not sure how much I agree with the first statement, but I definitely agree with the second. That's not an easy problem, though.
First, we are doomed from the start, because of network effects. The new web will likely never gain any traction whatsoever, because it looks like backwards compatibility is more important than simplicity, performance, and CO2 emissions.
Second, we must agree what that new web is for. We can display text, images, audio and video. We can tweak the layout of the content. We can take input from viewers (text, uploaded files…). We can make entire applications on top of the web.
Once we agree on the purpose of the web, we need to chose how to make it happen. Do we serve content declaratively, or procedurally? Should browsers be readers of a well defined, limited data format, or should they be virtual machines? I personally prefer virtual machines (unlimited functionality on top of a very simple core), but their natural opacity does have its problems: screen readers, dark mode…
---
There may be a way to break network effects: government web sites. Define a new standard that serve those right, make sure this standard is easy to implement pretty much everywhere (including on old computers with a crappy connection), and mandate that all .gov sites move to that. Also maybe rethink the whole security layer, most notably the PKI.
To move things further, we could possibly use regulations. For instance, we could mandate that banks provides an option to use that new web. We could regulate our way into a critical mass, to a point where common folks can realistically ditch the old web.
First, we are doomed from the start, because of network effects. The new web will likely never gain any traction whatsoever, because it looks like backwards compatibility is more important than simplicity, performance, and CO2 emissions.
Second, we must agree what that new web is for. We can display text, images, audio and video. We can tweak the layout of the content. We can take input from viewers (text, uploaded files…). We can make entire applications on top of the web.
Once we agree on the purpose of the web, we need to chose how to make it happen. Do we serve content declaratively, or procedurally? Should browsers be readers of a well defined, limited data format, or should they be virtual machines? I personally prefer virtual machines (unlimited functionality on top of a very simple core), but their natural opacity does have its problems: screen readers, dark mode…
---
There may be a way to break network effects: government web sites. Define a new standard that serve those right, make sure this standard is easy to implement pretty much everywhere (including on old computers with a crappy connection), and mandate that all .gov sites move to that. Also maybe rethink the whole security layer, most notably the PKI.
To move things further, we could possibly use regulations. For instance, we could mandate that banks provides an option to use that new web. We could regulate our way into a critical mass, to a point where common folks can realistically ditch the old web.