Thanks so much! I was really stoked by yesterday's related post (and your discussion in the comments). I also find it really interesting to see Scheme used in production; I sort of marginalized it (unfairly to myself, I'm sure) after college as being a good toy Lisp for things like demonstrations in SICP.
I sometimes wish there was a language inbetween scheme and common lisp that actually caught on. They're both powerful languages, but to me the little scheme I've done makes me feel like I'm just reinventing common lisp as I go along, and sometimes common lisp leaves me wanting for something a bit "smaller" that doesn't take up 30mb of memory just to open the REPL. This especially holds true in the mobile world.
Funny, I'll be in Redwood City tomorrow. Didn't know you guys were based there. Question for you: did you write your own implementation, or are you adapting something like ECL? Do you have any articles posted on how it works?
What I meant by inbetween is something exactly like CL with a smaller footprint and possibly a smaller library. I believe CL more than covers today's practical needs (real threading, compiling to machine code, calling out to C, etc etc). I might choose Clojure if I was writing something highly concurrent that required a more functional approach, but for any other general purpose app I'll take CL any day. (Disclosure: I've never actually built anything in Clojure).
It's truly inspiring to see a project like this completed. I've been wanting to combine mobile (specifically Android) and some sort of Lisp dialect for a while.
Am I interpreting correctly from some of the other components that doing the programming in a language-once-removed (ie Scheme instead of Obj-C) opens an easier path to compiling for both iOS and Android?
> I listened to this podcast the other day and it was one of the more compelling This American Life episodes I've listened to recently.
Agree. Rarely have I felt so riveted to what was going on. I attribute it to the pace and the chronology. Unlike many TAL shows which are told in retrospect and/or are multi-parters, this one is a single storyline with the actors right there, on air, dealing with the conflict and resolution before our ears.
Great writeup. I always appreciate somebody else doing a down-to-earth overview of something complicated. This post makes me wonder if some sort of flowchart or UML diagram of the docker system components wouldn't be a useful thing.