4 ms·
"The right graphical client/server model is to have an extensible server. Application programs on remote machines can download their own special extension on de
by XMPPwocky 7y ago
"The right graphical client/server model is to have an extensible server. Application programs on remote machines can download their own special extension on demand and share libraries in the server. Downloaded code can draw windows, track input eents, provide fast interactive feedback, and minimize network traffic by communicating with the application using a dynamic, high-level protocol."
Huh, that's surprisingly prescient.
Applications on remote machines can download their own special JavaScript on demand and share code in the server. Downloaded code can draw windows, track input events, provide fast interactive feedback, and minimize network traffic by communicating with the application using HTTP.
- ddingus 7y agoInteresting parallel there.
- gopalv 7y ago> Applications on remote machines can download their own special JavaScript Depending on what era we imagine writing this, this could be a Java applet or a Flash application or an ActiveX component.
- XMPPwocky 7y agoYeah, but "SPAs" based on Java/Flash/ActiveX weren't nearly as ubiquitous as web-based SPAs are now, were they?
- fiddlerwoaroof 7y agoFlash was
- DonHopkins 7y agohttps://en.wikipedia.org/wiki/NeWS https://en.wikipedia.org/wiki/NeWS NeWS was architecturally similar to what is now called AJAX, except that NeWS coherently: - used PostScript code instead of JavaScript for programming. - used PostScript graphics instead of DHTML and CSS for rendering. - used PostScript data instead of XML and JSON for data representation.
- anthk 7y agoPS was amazing, I've even seen a Z Machine V3 interpreter at rec.games.int-fiction. Enough to run Zork and old versions of Curses!. But writting the interpreter is easier than finishing the last mentioned game.