Most of my projects start with a question: can I do this without that? I build the thing, use it for real, and write down the verdict. The good ones grow up and get a successor. So my repos aren't a list. They're a family tree:

• 🟢 Notes: sublime_zk → sublimeless_zk → telekasten.nvim → omajop → omajot. Zettelkasten tools since 2017, one editor at a time.
• 🟠 Web, in Zig: zap → bounded/http → baz. From a C foundation to pure Zig with hard limits.
• 🟣 Slides: Bûllets → slides → rayslides. Plain text in, great talk out. Third attempt, best one.
• 🔵 No cloud: dockercr → omajot. If SSH or Tailscale can do the job, I don't need somebody's cloud.

omajot is where the lines meet: notes from the green line, a hub served by baz from the orange one, and the no-cloud rule from the blue one.

Omarchy is my desktop. When I miss something in the bar, I write a plugin for it. There are five so far.

omagma: Gmail and Google Calendar in the terminal. Threads, Vim keys and Markdown compose; one week across three accounts; meetings with Google Meet links, guests from Contacts, and a reminder that joins in the right Chrome profile. Plus a read-only bar dropdown and an agent CLI. Website	omajot: my own notes app, synced by my own hub. A dropdown and a main window in the bar, full keyboard control, and the same notes in the terminal and on my phone.
omajop: a Joplin notes browser. Folders and tags, the note list and the rendered note, one click away. omajot's predecessor. When you're ready to move, omajot imports Joplin in one command.	omapress: Omarchy news in the bar. The newspaper turns red when there are unread posts, and a keyboard-driven panel reads them without a browser. Works offline.
neomarchy: search, favorite and play neowake sessions from the bar. Playback runs through mpv with MPRIS, so the media keys just work.	Install Four of them are one command each: u=https://github.com/renerocksai for p in omajot omajop \ omapress neomarchy; do omarchy plugin add $u/$p --enable done omagma ships as a verified release bundle: give your coding agent its website and let it walk you through the Google setup. omajot also needs its hub: see Get started.

The question, the trade, the verdict.

One Gmail tab was using roughly 2 GB of RAM on my desktop. So omagma brings Gmail and Google Calendar into the terminal instead, for up to three accounts kept apart. The TUI does the whole job: threads, search, Vim keys, labels, attachments, invitations, and Markdown compose with a cancellable send countdown. Calendar shows all three accounts in one week, creates and reschedules meetings with Google Meet links and guests picked from Contacts, and reminds me ten minutes before a meeting, with Join opening in that account's Chrome profile. A read-only dropdown in the Omarchy bar shows new mail at a glance, and a JSONL agent CLI lets agents work mail and calendar with only the per-account grants I approve. All of it is Zig: a static musl binary on Linux, and the same TUI controller even runs in the browser as WebAssembly.

Trade: always-open Gmail and Calendar tabs, for a terminal, a bar and an agent interface that each get exactly the permissions I grant them.
Verdict: ✅ Mail and calendar in the terminal, and the bar holds three accounts in about 31 MB, against one 2 GB tab.

Apple-Notes-like markdown notes in the Omarchy bar, in the terminal, and on my iPhone. No Dropbox: a small Zig hub syncs every device over Tailscale. The hub runs on my always-on M3 Max, the same box my coding agents already live on. Hub-and-spoke is a pattern I trust, so notes got the same treatment. A CRDT written in Zig merges concurrent edits, and the same Zig core runs natively on the desktop and as core.wasm in the phone's web app. The hub is a baz app.

Trade: Dropbox's zero-setup sync, for notes that never leave my own machines, work offline, never conflict, and that agents can script.
Verdict: ✅ Daily driver. My notes live there now.

omajot's older sibling in spirit. ghcr.io has download limits. A self-hosted registry wants TLS, a CA and access tokens. dockercr skips all of it: the registry only listens on loopback, and SSH port forwarding does the authentication and the encryption. No Docker Hub, no certificates.

Verdict: ✅ Push to production like a boss.

Zap (★ 3.4k) made Zig backends blazingly fast on top of facil.io, a C library. bounded/http replaces that foundation with pure Zig on io_uring, kqueue and IOCP, inspired by TigerStyle: connections, buffers, queues and workers are reserved up front. When capacity runs out, it pushes back instead of growing. On Linux it needs no libc, so a server can be one static binary. Baz (Bounded Async Zap) puts Zap's typed endpoints on top, with streaming, SSE, Mustache templates and cookies.

Verdict: ✅ Good enough to trust with my notes: it runs the omajot hub.

In the early nineties I designed a small Radical RISC CPU on paper. At Christmas 2020 I finally built it: VHDL, simulated with ghdl and gtkwave from vim and tmux, with its own assembler, running on a Xilinx Spartan-7 FPGA board. The whole story is written up, from microcode sketches to the first executed instruction.

Verdict: ✅ Nearly thirty years late, and it runs.

My third answer to the same question. Bûllets (2020) turned the Godot game engine into a slide show: interactive animations, a game in your deck, and a multiplayer mode through bullets-server. slides (2021, my first Zig project) went small: one executable, Dear ImGui and OpenGL, a markdown-ish text format, at 10 000 FPS. rayslides, built on raylib, keeps the readable source and adds a visual Studio that stays in sync with it, reveals, transitions and morph animations, and an embedded Neovim. Bûllets' multiplayer grew up, too: it's now a phone remote with speaker notes, plus Crowdplay audience polls.

Verdict: ✅ Nobody has noticed I'm not using PowerPoint.

A ticket booking system on TigerBeetle. Tickets and goodies are accounts and transfers. A checkout places a time-limited hold, a pending transfer, and the payment webhook either finalizes or voids it. It uses FastAPI, Redis and PostgreSQL, has load tests, and I wrote an auto-batcher for the async TigerBeetle client along the way. Try it live.

Verdict: ✅ If you can reserve it or run out of it, TigerBeetle can count it.

_{⚡ zig ⚡  ·  Vienna  ·  renerocks.ai}