We need a new protocol to replace HTTP and allow for software

(written by lawrence krubner, however indented passages are often quotes). You can contact lawrence at: lawrence@krubner.com, or follow me on Twitter.

About this:

” We do not control the environment executing our JavaScript code, interpreting our HTML, or applying our CSS. Our users control the device (and, thereby, its processor speed, RAM, etc.). Our users choose the operating system. Our users pick the browser and which version they use.”

The original idea of a “browser” was something that was as agnostic as possible about its environment, but somehow managed to deliver a nearly universal experience. The traditional idea of a “browser” does not include any idea of package management. Only developers have to worry about package management, not the average user. But I think, to take the Internet up to the next level, we will need a browser that handles package management. Indeed, that will have to be the main task of browsers in the future. What’s needed is a browser that can implement something like a Gemfile, but on the client side, to deal with the issues raised in the quote that I pasted above. I have talked about the need for a runtime, which is important, but versioning will also be an important aspect of any runtime.

Post external references

  1. 1
    http://modernweb.com/2014/09/22/fundamental-disconnect/
Source