3 ms·
Lovely post! Here here! I've toss in cap'n'proto & surely others who let you write messages that talk about still outstanding messages. Still short of referrin
by rektide 7y ago
Lovely post! Here here!
I've toss in cap'n'proto & surely others who let you write messages that talk about still outstanding messages. Still short of referring to full on streams in your messaging.
https://capnproto.org/rpc.html https://capnproto.org/rpc.html
There's hx-uri that allows for referring to other http messages, which I think could fulfill this in http.
https://github.com/martinthomson/hx-uri https://github.com/martinthomson/hx-uri
Here's to expanding the medium! Let the hypertext ever hyper.
- DonHopkins 7y agoThanks for pointing that out! I'd heard of Cap'n'Proto but didn't realize how cool it was. Pipelining promises is incredibly useful! I'll check it out more deeply now. When I first heard of it, maybe I was initially skeptical because of the name, having been traumatized years ago by Cap'n Software Forth on my Apple ][, which John Draper developed to implement SleazyWriter while incarcerated in the Alameda County Jail. https://archive.org/details/EasyWriter_Capn_Software_John_Draper_1979_Program https://archive.org/details/EasyWriter_Capn_Software_John_Dr... >EasyWriter was a word processor first written for the Apple II series computer in 1979, the first word processor for that platform. It was written by John Draper's Cap'n Software, which also produced a version of Forth, which EasyWriter was developed in. >Draper developed EasyWriter while serving nights in the Alameda County Jail under a work furlough program. https://news.ycombinator.com/item?id=14245590 https://news.ycombinator.com/item?id=14245590
- hhas01 7y agoInteresting. Hadn’t heard of Cap’n’Proto. A clever idea, although I do wonder if it’s being too clever for its own good, being unnecessarily restrictive. Dr William Cook (who designed much of Mac OS’s “RPC-plus-queries” IPC model) explored a more generalized approach where whole self-contained chunks of behavior can be sent across the wire for remote evaluation. As I recall, his Batches model uses a “safe” subset of familiar JavaScript operations, but any behaviors could be supported as long as they are guaranteed to terminate. http://www.cs.utexas.edu/~wcook/projects/batches/index.htm http://www.cs.utexas.edu/~wcook/projects/batches/index.htm There’s nothing inherently magical about this: it’s just a carefully-restricted form of remote execution where the client-supplied “code” to be executed is incapable of doing nasty things like access restricted APIs or lock /blow up the server with infinite loops or stack overflows. Beyond that, it’s just a question of whose CPU you want to burn more, and how much time you want to spend bouncing between them. Thinking about it from a JavaScript or C mindset will make your head ’splode, but for Lispers (of which Smalltalkers are a spinoff) it’ll be a big fat “how obvious”. Be nice to see it further pursued.