amen zwa, esq. on Nostr: npub15fe8s…3x47v npub1qmshc…3wxk4 Mate, so I want to bounce this thought off you. ...
npub15fe8snwf0jsk93au6haj3zrtxx9awz3wcc8lxx6qmypv6tndww6sp3x47v (npub15fe…x47v) npub1qmshcslmwan3erj3ulczepe8q8a8xdyfkndnk8fudgtg8ccwg6zqr3wxk4 (npub1qms…wxk4) Mate, so I want to bounce this thought off you.
I look at Mosaic, Netscape, Explorer, Opera, Safari, Chrome, the lot, and see OS-wannabes. We have HTML static content, JavaScript dynamic content, Angular/React GUIs, V8 engine, and browser OS-like infrastructure. Then, we layer atop this WebWorker threads and WebSocket transport tier. All of this had to crawl through the underlying networking stack and OS services. It's wasteful.
Browsers emulated OSs. Modern OSs now behave like browsers. Why not ditch the web stack middleman, and adapt modern OSs to take on new responsibilities.
I look at Mosaic, Netscape, Explorer, Opera, Safari, Chrome, the lot, and see OS-wannabes. We have HTML static content, JavaScript dynamic content, Angular/React GUIs, V8 engine, and browser OS-like infrastructure. Then, we layer atop this WebWorker threads and WebSocket transport tier. All of this had to crawl through the underlying networking stack and OS services. It's wasteful.
Browsers emulated OSs. Modern OSs now behave like browsers. Why not ditch the web stack middleman, and adapt modern OSs to take on new responsibilities.