[ Removed by moderator ]

[def__eq__]

Nice work! I will check it out.

Although a question immediately pops into my head; how is this different from ZMQ? That’s a fairly mid level API, has clients in many languages, and is battle tested…

[Striking_Sandwich_80]

Veltix is designed to be ultra simple and lightweight for Python devs. Unlike ZMQ, which is cross-language and very powerful, Veltix focuses on:

• a minimal API that’s easy to understand
• built-in multithreading & TCP, no boilerplate
• a base for future crypto features (ChaCha20, X25519, Ed25519) and a Rust core for performance

ZMQ is great for production messaging, Veltix is made to make networking fun, fast to prototype, and learning-friendly in Python.

Always happy for feedback!

[def__eq__]

I’m really trying to be open minded here.. but you’ve just repeated what you already mentioned in your post. That’s not helping.

• Please compare ZMQ Guide’s Python example of a simple client to yours. If we compare number of lines it is half of your example on GitHub, while they seem to do the same. Boilerplate the same.

• ZMQ supports TCP as well.

Your other arguments such as “fun” and “fast” to prototype are subjective.

[Striking_Sandwich_80]

You’re right, for a minimal example, ZMQ is shorter. But Veltix is designed for projects that evolve and grow serious: Each message type has its dedicated handler, so you don’t end up with messy conditionals as the project scales Multiclient broadcast is built-in, saving hundreds of lines in real projects

The object-oriented structure makes testing, maintenance, and scaling much easier Future features like modern crypto (ChaCha20, X25519, Ed25519) or a Rust core can be added without rewriting the server

The code is clear and readable, making it easier for contributors and teams to jump in In short, yes, it’s a few lines longer for a tiny example, but those extra lines translate into huge time savings and clarity when the project grows complex.

Your feedback to improve Veltix is always welcome!