2 ms·
https://elixirschool.com/en/lessons/intermediate/erlang https://elixirschool.com/en/lessons/intermediate/erlang Interoperability makes them very companionable
by photonthug 1y ago
https://elixirschool.com/en/lessons/intermediate/erlang https://elixirschool.com/en/lessons/intermediate/erlang
Interoperability makes them very companionable so it’s not really a rewrite situation. Whichever you have I bet you can code generate your way almost all the way to a fairly complete wrapper of the other. Way simpler than most stuff like FFI, although I’m not aware of all the details of any type conversion gotchas or similar. I’ve never been lucky enough to actually work on this stuff professionally
but rather than a rewrite I think it’s more a question of which representation is first, primary, or at the bottom of the stack. Would be nice to hear more from an expert though
- rdtsc 1y ago> Interoperability makes them very companionable The syntax is different, but they can call libraries from other each. I guess are you thinking from the perspective of someone using this library in their code? Well, that argues for writing it in Erlang, since it is simpler to use Erlang from Elixir than vice-versa.
- arthurcolle 1y agoyeah observer:start() vs. :observer.start()