I agree. The basic interface design seems really neat but it's so easy to run into horrible problems with it. For one it doesn't really deal with errors very we

I agree. The basic interface design seems really neat but it's so easy to run into horrible problems with it. For one it doesn't really deal with errors very well: once you've thrown a message into it there's basically no mechanism to know if something goes wrong with it (and it certainly used to just straight up assert in many, many error cases, which sure made it hard to use the 'reliable central broker' mechanism they advocate in the docs). The implementation is also really brittle: it's basically trivial to cause all kinds of misbehaviour if the other end does not act as expected. The problem is there isn't really many good alternatives that are actually similar. Other 'message queues' are basically big databases, not a library. I feel there's room for something with the same philosophy but better execution.