3 ms·
For the record, at dotCloud we are big fans of 0mq but a lot of these comments are legitimate. The doc is not always clear or up-to-date, the code is extremely
by shykes 15y ago
For the record, at dotCloud we are big fans of 0mq but a lot of these comments are legitimate. The doc is not always clear or up-to-date, the code is extremely opaque to outsiders, and as a result a lot of the "20+" bindings are in fact wrappers around the reference C++ implementation - which is a problem for asynchronous runtimes such as NodeJS.
This doesn't necessarily justify an incompatible fork - but seeing these issues addressed in such a dismissive fashion is a little worrying.
- spekoded 15y agoI can count the number of active projects that have absolutely up-to-date documentation on one hand. Opaque to outsiders who don't understand C++. What do you think "binding" means? This doesn't approach a fork. This is just a plea for a rewrite of 0MQ in Python with EXTRA BONUS FEATURES. Very much not the Unix way.