[zeromq-dev] JeroMQ

Pieter Hintjens ph at imatix.com
Tue Oct 1 23:21:27 CEST 2013

On Tue, Oct 1, 2013 at 11:01 PM, Artem Vysochyn
<artem.vysochyn at gmail.com> wrote:

> Still totaly confused... Why need  to port something on something? Why
> then not create php-port or python-port?

There is a .Net port. I've heard rumours there is a pure Python stack
floating around. There is a node.js stack. I've even seen a Bash

In an open community, at least in the ZeroMQ community, which embraces
diversity of thought, people are free to make what they want, what
they feel is important to them. Your confusion comes from not seeing
the problems and use cases that JeroMQ solves. Try to think about what
those might be, and you will be enlightened. For instance, read

> What bothers most, if this is "a port", then it should mandate "what
> exactly is currently supported and what is not, what is supported with
> limitations", and so on.

If it bothers you, simply ignore it.

> Or should I just believe that one can take a lib and copy that lib on
> another language w/o compromising its original features?

Copying is not theft, it is praise. You cannot diminish the value of A
by making a copy and modifying that, unless you fraudulently call it
A. There can be a million forks and clones and "this time, I promise!"
reboots of a project, without diminishing the value of that project.
The opposite: JeroMQ had a positive impact on JZMQ.

What matters with ZeroMQ are two things, mainly. One, the protocols,
which guarantee interoperability. The more projects implement those,
the more choice a user has, which is only positive. Two, the
community, which drives our progress and makes every day a happy one.
The more projects in the ZeroMQ community, the better.


More information about the zeromq-dev mailing list