4 ms·
Given how often people complain about the modern web being app-centric, despite HTML, CSS and JS being meant for a document-centered model (and JS really only e
by krapp 10y ago
Given how often people complain about the modern web being app-centric, despite HTML, CSS and JS being meant for a document-centered model (and JS really only existing as a gimmick to sell Netscape,) I've been wondering just how well (or poorly) the web model could work with streaming applications.
In other words, instead of hacks that replicate a UI in the browser, have something that isn't a browser but acts like it, and source code repositories at URLs instead of documents which compile and run per request, or session (if you want to "cache" them,) or whatever. This would differ from embedded applets, flash or similar in that you would be pointing to code rather than streaming and running binaries, which would enable the user to view or possibly modify the source code before running.
Probably a terrible idea for numerous reasons, or it more or less already exists and I just don't know about it (which is not unlikely) but it might be interesting to see how it might work, and it would be far closer to the FOSS ideal than the web, for which you can't actually see or modify anything other than the result of requests.
- idle_zealot 10y agoHow is this different from just serving a website that is pure js?
- krapp 10y agoNot much different, but the basic idea is to not be limited to a particular runtime or language, and to get away from transpiling other languages to javascript. Essentially, serving containers or emulators with native code, rather than documents and JS.
- mixedCase 10y agoQML does this, but it trusts whatever it loads. You would have to build some security into it, or at least, around it.
- Jtsummers 10y agoRebol had something akin to this idea.