3 ms·
> However the "exterior" extension seems obvious to me -- why hasn't anyone produced a distributed Lisp? How about Lisp Flavored Erlang?
by phoe-krk 3y ago
> However the "exterior" extension seems obvious to me -- why hasn't anyone produced a distributed Lisp?
How about Lisp Flavored Erlang?
- chubot 3y agoHow does Lisp Flavored Erlang talk to Common Lisp? Probably with a byte stream. The VMs are different. I've noticed Erlang/Elixir also favor interior composition! Parsing is not idiomatic there -- they're actually BAD languages for parsing text. (Though they do have good affordances for parsing bytes) They prefer to pass around Erlang terms, which are copied inside the VM. I get that -- it's more convenient. But it's also a reason why "the rest of the world" has more code reuse -- e.g. Go talks to JavaScript talks to Python. Most projects have multiple languages. Monoglot projects become polyglot projects when they grow bigger. --- So I say - Lisp prefers its own (interior) narrow waist - Erlang prefers its own (interior) narrow waist -- even the Lisp one is second class! - The rest of the world uses the (exterior) byte stream narrow waist, but they complain about it a lot :)