A few years ago I built occasionly.io, a little app to host events and invite friends. It was great, I had fun, but I let it slide as I focused on other things. Even so I still used it religiously for managing my own calendar and schedule, but it became annoying to maintain, and it withered.
For a while now I've missed it, and I've missed having a non-work software project that isn't boat or bell ringing related. Now feels like the time, and regularly documenting what I'm working on has been a great system for staying consistent, hence this here weblog.
Occasionly v0 was a Rails app, deployed on Fly.io, built the old-fashioned way with artisanally hand-crafted code. It was buggy, too — especially the messaging connections which sometimes didn't work.
And deploying it was slow, annoyingly slow. A few months back I ~vibed~ a deployment tool for PocketBase, and I've been spoiled by rsync:
That's the bar: sub 10-seconds (network latency notwithstanding). You can get Rails down to a couple of minutes, and Kamal is great, but why settle.
Starting from zero
The first step in building an events/calendaring service is creating a web framework from scratch. Some might say you also need a new programming language, but I'm using Zig. I'm a huge fan of Zig. Our stances on AI differ (I will be writing very little of this code), and I perpetually have strong "beginner energy," but I love the language and their commitment to building excellent software, and the design choices just feel *chefs kiss*.
As for web frameworks, Ruby on Rails is inspired, and it may be token efficient, but the software development contract has changed. And I used to be excited about Svelte(Kit), but as a full-stack framework it's a non-starter. We no longer have to trade speed against developer ergonomics, we can go the whole way, and I think there's space to answer the question "what if Rails but we're in 2026, and it's built to be written by machines?"
(Of course the real reason for this is that I'm inspired. Rationalisations be damned; it's vibes all the way down.)
What I'm vaguely building
At a high level I'm building this to help manage my time, and make it easier to hang out in-person with my friends and family. Coordinating time and location is still a mess, and I'm not using Luma or Partiful for a few people I already know. There's something missing in the 3-15 person space, with WhatsApp filling that void assuming there's a wrangler in the group.
My MVP
The first thing I want is events on my calendar. This was what I used the most, and the "create an event in any calendar app -> immediate event page to share" was so very useful. That is step 1 — a calendar and syncing it.
I could build this on top of e.g. Google Calendar or something else, but a single calendar is just the beginning, and there are more interesting things you can do when you own the whole stack. And besides, code is now free, so a CalDAV server it is. For zyn this means:
routing, and custom http methods (
PROPFINDetc.)views / rendering
a database (postgres) and its shenanigans
deployment
authentication and authorisation (although this somewhat lives in user-land)
a bunch of other things I'm forgetting
This isn't entirely "from scratch," e.g. I'm using the excellent http.zig library (and pg.zig and ztl and more soon... Karl Seguin is a machine).
This week I got most of the first 3 implemented:
Setting up a database for development is one of the most annoying things across frameworks, and zyn will have a fully-managed Postgres instance, even in development. No setup, just zyn dev and everything runs, as god intended.
After init this is the initial app.zig entry point:
const zyn = @import("zyn");
pub const RequestLocals = struct {};
pub const middleware: zyn.Middleware = &.{
.use(zyn.RequestLogger, .{}),
};
pub const routes = @import("routes.zig");And the routes.zig file:
const zyn = @import("zyn");
const std = @import("std");
pub const prefix = "/";
pub const defaults: zyn.RouteDefaults = &.{.layout("layouts/application.html")};
pub const table: zyn.RouteTable = &.{
.get("/", root, &.{}),
.get("/healthz", zyn.routes.health, &.{}),
};
fn root(_: *zyn.App, req: *zyn.Request, res: *zyn.Response) !void {
const time = std.Io.Timestamp.now(req.io, .real).toSeconds();
try res.render("root.html", .{ .time = time });
}I quite like the API so far, but nothing is sacred. Next up is a very minimal ORM, authentication et al, then figuring out deployment.
Until next Thursday!
- Nick