The history of compiling for first-class continuations, first-class environments has shown that a little effort reduces the tax for *not* using them can be fairly low, and the cost *for* using them can be lower than one might at first expect.
I would be willing to be the same is true for fexprs once some experience is gained compiling for them in a modern language with modern compilation techniques.
Hey, how are things on Twitter? I have reduced my commercial social networks down to just Google+. And I am gearing up to build something via unhosted, webrtc, etc. (Although I think xmpp may be necessary to bridge the gap until webrtc for data is available.)
The one downside for the time being is... everyone is holding every conversation on Twitter.
Being off twitter is refreshing, except for the part where everyone else is on twitter. I'll be happier still when I give up G+, but it's my remaining outlet for now.amazing
re: collab on unhosted/webrtc, definitely. At a minimum we can compare notes, and either develop some common bits or at least make sure they can all get along with each other.
If you start a little write up about unhosted/webrtc then I won't have to continue distracting this wonderful llama from paying attention to fexprs.
Oh, and going back a few days where someone was speculating on what an imperative OOP reactive environment would be like: please tell him it was done already. More than once. e.g. ThingLab in Smalltalk, Loops in Lisp.
The history of compiling for first-class continuations, first-class environments has shown that a little effort reduces the tax for *not* using them can be fairly low, and the cost *for* using them can be lower than one might at first expect.
ReplyDeleteI would be willing to be the same is true for fexprs once some experience is gained compiling for them in a modern language with modern compilation techniques.
Hey, how are things on Twitter? I have reduced my commercial social networks down to just Google+. And I am gearing up to build something via unhosted, webrtc, etc. (Although I think xmpp may be necessary to bridge the gap until webrtc for data is available.)
The one downside for the time being is... everyone is holding every conversation on Twitter.
I think you overreacted a bit with leaving Twitter (especially if you continue to use G+) :-)
ReplyDeleteI'm also working on unhosted/webrtc stuff, so maybe we can collab. Need to do a writeup...
Being off twitter is refreshing, except for the part where everyone else is on twitter. I'll be happier still when I give up G+, but it's my remaining outlet for now.amazing
ReplyDeletere: collab on unhosted/webrtc, definitely. At a minimum we can compare notes, and either develop some common bits or at least make sure they can all get along with each other.
If you start a little write up about unhosted/webrtc then I won't have to continue distracting this wonderful llama from paying attention to fexprs.
Oh, and going back a few days where someone was speculating on what an imperative OOP reactive environment would be like: please tell him it was done already. More than once. e.g. ThingLab in Smalltalk, Loops in Lisp.