On Tue, Mar 22, 2011 at 11:41 PM, Martin Lucina <[email protected]> wrote:
> Why can't we get along, you build all the fancy ROUTERs and funky > abstractions you want in zapi, and the core can support that. Well, here's the core of the issue... My mission with the Guide is to explain 0MQ, and then I stumble across things that simply are unexplainable. Two options: bluff my way through, ignore the obvious pain, and pretend users are just stupid for not getting it. Or, work to fix those areas, and make things work as expected. I'm amazed, to be honest, that you don't get this, and that you insist on making this a personal issue. It's about good design, utterly subjective. No-one enjoys using a bad name. We had the same rather pointless discussion over UPSTREAM/DOWNSTREAM and there I also just stopped debating and forced the change. There are other design problems in the API, but they can be covered up in bindings, and that's one reason I spent today writing, documenting, and packaging several thousand lines of code. However the names can't be hidden, they form the essence of the patterns we explain and share and when they're bad, they hurt at every layer. -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
