3 ms·

back when i tried using it (also several years ago), i was pretty disappointed. i can no longer remember the details, but i much preferred erlang (despite pref

back when i tried using it (also several years ago), i was pretty disappointed. i can no longer remember the details, but i much preferred erlang (despite preferring scheme to erlang from a language pov). i looked back through my blog and found this comment - http://www.acooke.org/cute/TermitevEr0.html http://www.acooke.org/cute/TermitevEr0.html "Even when Termite works (and I couldn't get it to work reliably), it differs in functionality compared to Erlang. A single Gambit instance is a single process - its "threading" is implemented using continuations - and so (unlike Erlang) it cannot automatically use a dual core. ... [I]f you want a system that just works, use Erlang.

mononcqc 17y ago
That's okay, though. Concurrency =/= parallelism. The most important part is being able to build independent blocks that can interact. Having them run at the same time is just a nicety on top of it, but it's in no way essential. Erlang worked that way from the 80s until 2006, when it started supporting SMP in R11B.
anonjon 17y ago
lisp flavored Erlang is pretty cute. http://github.com/rvirding/lfe http://github.com/rvirding/lfe If you like lisp, and you like Erlang, I think that it is the way to go. It compiles to .beam files and runs on the regular VM. I have yet to use it for anything 'serious' but in the toy projects that I have used it for it has been quite good. All that it really needs is more people using it.