derekcollison

We are waiting on the IO abstraction for a supported Zig client (There are others though today), but this is specifically for a new initiative at Synadia that we will share more details about soon!

Would your company be willing to fund the development? Or would you be willing to post a PR? We would be happy to take a look.

We are waiting on demand for it. We have a bunch of folks using MQTT on NATS and NGS but no requests yet for MQTTv5 so far.

Once we see legit demand we will make sure it's supported.

We have some great work coming that allows lighter weight consumers to scale to that level and beyond. Happy to chat with folks on how we can make that work today.

We are always interested in feedback on how we can do better. Feel free to jump on our slack channel to join the community. We are actively working on the C client. Interested in more details on Python and Java issues as well.

I think entropy, in however you measure it, does influence something like a UUID generator differently than the cryptographic algorithms. What you are trying to achieve, or more importantly the condition you are trying to avoid, is different.

I agree, was simply sharing because it was a need we had, which might be a need someone else had as well. Anyone can feel free to use it or not.

Yes, but most UUID when moved across networks are translated to hex, so 32 bytes/characters whereas NUID's are 22 bytes, so generally a savings of 10 bytes per when stored as a string.

UUID V4 is ~900ns/op, NUID is ~60ns/op, so 15X speedup, or 1500%.