erlang? #124
Description
After fighting for a over a year or so to get properly working multiprocessing in python ( and by properly I mean completely user intuitive to the point that it is transparent - no setup.bash sourcing, no traceback disappearing, node crashing, never coming back, etc.) with ROS, I think we should investigate another approach : http://erlport.org/
We still need a pyros ROS node, but the internal pyros communication (what is done with pyzmp) could also be done with erlport. This would allow another layer of fool-proofed concurrent software on top, which would be very useful, as soon as we start thinking of robots as something that doesn't stop/crash/break all the time.
This could also be done, at another level, by writing a UBF / ROS message translator. But it would take care only of the messaging, not about the process control and other details (passing errors, monitoring request failures, etc.)...
Anyway these project seems worth following as well :
- http://lfe.io/ (mostly for autonomous evolving ROS AI - rewriting itself all the time)
- https://github.com/lfex/lsci (mostly for an eventual integration with ROS)