Ask HN: Why aren’t libraries inter-callable by default?
Lisp is dead. Really dead this time. But it’s not bcs of the language, it’s bcs the libraries haven’t kept pace with, say, Python. But wouldn’t it be easy to write an “interface matcher” that would easily allow Lisp to call python libraries. (Obviously, replace Lisp and Pyhton with L1 and L2 - in fact you don’t even need L2 bcs all libraries could in theory be written to this FFAPI, so to speak, and then any language could call on all the best libraries and people could stop wasting time replicating libraries in every L1!?)
(
7 comments
| 14 points
| on HN
)
the main thing is the data structures need to be compatible, any value you have on one platform needs to be instantiable on all the others, that is the only way to have the libraries call into each other without impedance. the value notation is called EDN and the value interchange mechanic (that manufactures platform specific value instances) is called Transit.
Clojure has a pretty cool network effect if you ask me
what is important in the big picture is that the semantics of the values are the same everywhere, not necessarily that they are memory compatible.
Coconut (https://github.com/evhub/coconut) might be interesting to you too.