Reply to post: There are some technical bugs we can certainly fix

There are some technical bugs we can certainly fix

For example the Web has the problem that it's possible to have 3rd party elements on a page. This used to be used for webcounters, but now is mostly abused by advertisers and Facebook.

Same goes for Javascript. It used to be an interresting idea which is now mostly abused. To add injury to insult we now have CPU bugs we cannot fix which can be exploited (in principle) via Javascript. In any case cyber currency miners are a problem.

Imagine a different protocol, one that is more like a terminal protocol. You have your "screen" which in case of traditional protocols is composed out of a grid of character cells, and in a new standard might be more like the browser DOM tree. This "screen" can be manipulated via a single persistent TCP/IP connection. If you just want to display a quasi static document, the DOM tree includes some sort of URL for links and you send that URL when connecting. After the whole "screen" has been transmitted, the connection is dropped or put into an "idle" state from which you can request a new page from the same server if you wish.

If you want to use an application however, the connection stays open and elements of the "screen" can send events to the server. This allows for much simpler "Web Apps" as they can now work synchronously and don't have to string together disjoined HTTP-requests into some sort of session.

The beauty of this is that it's compatible with what we already have. SSH can easily carry such a stream and you can outsource your authentication and encryption to it. One could even create it in a backwards compatible way to ANSI terminals so you can instantly use it as a drop-in replacement for your terminal.