Building open source when the world around you is falling apart.
When I started developing ZenQL, I wasn’t thinking about production metrics or CI/CD pipelines. I was unemployed, the conflict in Iran wasnt something that i expected, and writing Go code was the one thing that still made sense.
ZenQL is a lightweight query language for Go — designed to be simple, memory-safe, developer-friendly and polymorphic. No magic, no bloat. Just a clean API that gets out of your way.
The Numbers Don’t Lie
This week, something shifted. i started working on a smart memory management mechanism for ZenQL internal operations. specifically when working with collections. because it was the pain point obviously. something that could allocate memory safely and more predictable. less dangerous for production environment and docker containers. GitHub’s traffic data told a story I wasn’t expecting:
things were getting serious even before introducing v1.8.1 (memory management, Projection etc...)
and the day of the release was a big hit.
530 clones in a single day. But the number that matters more is 163 unique cloners.
Why? Because the clones-to-unique ratio (~3.25:1) tells you this isn’t curiosity traffic. That ratio is the fingerprint of CI/CD pipelines — automated systems pulling the package repeatedly across builds. Real teams. Real workflows. Real production.
I’m Writing This Because open source built during hard times deserves to be documented. Not as a sob story — but as proof that useful things get found. And of course, to let the go community know that there is a production-ready tool that can help you a lot when dealing with data, named ZenQL
Top comments (0)