83 karma · joined August 12, 2025
But fair question. If tmux already fits your workflow, there may be no reason to switch. hrdx is more opinionated around running multiple coding agents across projects: it provides a workspace and pane sidebar, agent activity and completion status, built-in launch/resume flows, persistent sessions and layouts, and an external control API. The tradeoff is that it is much younger and less configurable than tmux.
Try it, play around with it, love it or hate it :-)
Ive been coding for almost 20 years, and for the past few with Go. Nobody would believe that a project of this scale or even a much smaller one could be pulled off, halfway stable, over a couple of days. Not even with a blueprint or two in hand. Thats why it matters, and its totally fair, to point out when something is largely vibe-coded. "Vibe slopped" is meant more as a joke. The essential parts of the code I actually understand. Some of them I modified and overhauled myself.
zot is a learning project not production logic with peoples sensible data or lives depending on it. ;-)
One piece of feedback that kept coming up: "Docker is great, but for local dev it can feel heavy, especially when I just want to spin up an event store and start building."
So I built Genesis DB LocalStack. A native macOS experience for event-sourced development:
What it does
- Runs Genesis DB locally, natively, no Docker daemon needed
- Launch instances in milliseconds
- Each project gets its own isolated DB + domain (*.genesisdb.local)
- Run multiple instances for microservices workflows
- Export/Import environments for fast team onboarding
- Config lives in plain text: version control friendly
Why?
Local dev today often means container orchestration before first code. Genesis DB LocalStack tries to remove friction: install app > click > build.
Sometimes the fastest developer experience is still the simplest:
Real processes on your machine, predictable ports, zero orchestration overhead.
Is a native, Docker-free local event-store helpful to you?
Appreciate any feedback, especially from folks doing event sourcing and CQRS, perhaps even with Genesis DB, in production.
Many thanks!
If you run into bugs and want to share them, please just open an issue in the GitRepo's, or send us a message, ... Genesis DB is already being used in production projects, and so far issues that came up have been addressed in newer builds, including performance.
On performance specifically, it would be really helpful to know more about your setup: machine, architecture, how much RAM, ... Performance issues mainly existed in the very early versions, some of which were still SQL wrappers.
On the "one-man show" point: The architecture of your software can allow you to swap out the underlying database system, meaning you're not dependent on anyone. Thanks to CloudEvents, your data remains compatible with other CloudEvents-supporting systems.
In the end, it's up to everyone to decide which software they want to use.