6 ms·
You just reinvented (sort of) Erlang's erl_call [1] in Python: Starts an Erlang node and calls erlang:time/0. erl_call -s -a 'erlang time' -n madonna
by nivertech 15y ago
You just reinvented (sort of) Erlang's erl_call [1] in Python:
Starts an Erlang node and calls erlang:time/0.
erl_call -s -a 'erlang time' -n madonna
{18,27,34}
[1] http://www.erlang.org/doc/man/erl_call.html http://www.erlang.org/doc/man/erl_call.html
- tbatterii 15y agoexcept it's in python. :)
- rdtsc 15y agoI think it is rather typical pattern. You see something in another language/platform, so you copy it to your current one, then keep doing it. However after a while you just have to ask yourself, why am I not using this other technology instead of spending time re-implementing it. So after copying, say supervision trees, RPC mechanisms, distributed system management, actor-based approach, one can ask "wait, am I not just using Erlang then".
- lloeki 15y ago> why am I not using this other technology instead of spending time re-implementing it Because this other technology/platform may lack something that the current platform has. Or you have constraints that lead you to usage of the first platform. Maybe this other platform could take a hint or two about stuff on the "copying" platform too, so that things go full circle and it does not stay up some ivory tower.