[phintjens]

It is challenging to explain anything subtle, when your viewpoint depends so much on what you already know, your preconceptions, and assumptions.

Sorry for the comic book style. It's how my mind works. Feel free to send a patch. :)

The benefits of 0MQ to me, as a programmer, are:

* Really easy to write utterly solid multithreading code, in a language (C) that has zero support for this; * Really easy to take this same code and make it multiprocess, or multibox, with few changes. * Built-in handling of asynchronous I/O, which I need in any real application. * Speed, meaning I can be lazy and my code still runs very quicky. This is less obvious than it seems. 0MQ's critical path is extremely evil.

It's so hard to explain this with a diagram or a slideshow. The only way to understand is to use it, to write code with 0MQ. Certainly for me, when I started programming 0MQ apps, my understanding of what this library was about, and what it could do for me, totally changed.