[zeromq-dev] Moving to 0MQ/3.0, yes or no?

[Martin Lucina]

Hi all,

sustrik at 250bpm.com said:
> In the recent month, the discussion about 0MQ/3.0 have shown that the 
> radical "parting with the past design flaws" goal of the endeavour 
> cannot be achieved. Every tweak has its user that will be hurt if its 
> removed. That makes the 3.0 version more or less useless: The flaws 
> won't be fixed while at the same time the backward incompatible changes 
> will hurt everybody.
> 
> Thus, we should revert the 3.0-related changes on master and go further 
> with 2.x version, in a fully backward compatible way.
> 
> Thoughts anyone?

Interesting discussion in this thread. I'd like to put up my hand for not
throwing out work that has been done, but instead improving communication
with our users so that what we arrive at with OMQ/3.0 can really be a
stable API that will last for many years.

After all, 3.0 *is* a major version change. We can explicitly break things,
as long as we don't remove functionality people are using without providing
alternatives, and as long as the breakage has been clearly justified.

Brian, I especially like your analogy with LEGO bricks. This is really what
I think ZeroMQ is about -- being the LEGO with which people can build all
kinds of weird and wonderful distributed applications that those of us who
built the tool didn't even think of.

-mato