license-list-XML VS OZ

The LGPLv3 exception had an atypical feature (for *GPL exceptions) and was possibly misdrafted, see: https://github.com/spdx/license-list-XML/issues/1672

X Doubt

Shortly after, they had the gall to ask for that garbage fire of a license to be included in a catalog of open source licenses. And then claimed to not understand how that request could possibly be denied...

My doubt is if there is some programmatic use of SPDX. If not why they have such a strict syntax as specified here. Also there are multiple extra tools on the github repo for parsing, comparing and even generating spdx files like this. Now if user is just mentioning the license identifiers why do we need all these? And what does it mean to compare licenses as it seems that they're using string comparison techniques to find closest match to license in their catalogue.

Yes, they acted very puzzled when an open source license catalog refused to include their weird thing.

At some point, Daniel Connolly applied for OpenBSV to be included in the SPDX license list, but was promptly rejected due its field of use restriction.

At my day job we run > 50 million messages per day through ZeroMQ, and have been quite pleased with its performance and stability (https://github.com/nyfix/OZ/tree/master#who-uses-it).

But the truth is that ZeroMQ has a steep learning curve, and some rather sharp edges that can leave nasty cuts if one is not careful.

If you're interested in becoming familiar with ZeroMQ, you might want to check out our implementation: <https://github.com/nyfix/OZ/>.

Unlikely, but they seem to be different things altogether. BlazingMQ appears to be a traditional message queue (think ActiveMQ), with message peristence. ZeroMQ is more of a network middleware (think Tibco Rendezvous), and does not include persistence.

BlazingMQ also appears to be more of a "platform" or "service" that an app can use (sort of like Oracle, say) -- ZeroMQ includes libraries that one can use to build an app, service or platform, but none is provided "out of the box".

Which makes it harder to get started with ZeroMQ, since by definition every ZeroMQ app is essentially built "from scratch".

If you're interested in ZeroMQ, you may want to check out OZ (https://github.com/nyfix/OZ), which is a Rendezvous-like platform that uses the OpenMAMA API (https://github.com/finos/OpenMAMA) and ZeroMQ (https://github.com/zeromq/libzmq) transport to provide a full-featured network middleware implementation. OZ has been used in our shop since 2020 handling approx 50MM high-value messages per day on our global FIX network.

At my day job, I manage a number of "friendly forks" of open-source packages (e.g., https://github.com/nyfix/OpenMAMA) as well as hosting our own open-source repos (e.g., https://github.com/nyfix/OZ).