Project Ceylon: Keeping the Architecture, Rebuilding the Assumptions
Project Ceylon keeps the architectural ideas that made the Amiga compelling while rebuilding the assumptions underneath them for modern hardware.
Entry 22
Development Journal
The running record of Project Ceylon: what was tried, what worked, what didn't, and what turned out to be wrong. Entries stay as they were written; when something changes, a later entry says so.
Entries, newest first
The Backstory Is Live. Tomorrow, Y'all Get the Mess as It Happens.
The retrospective is caught up. From here forward, Project Ceylon becomes a real-time record of the work, wrong turns, breakthroughs, and whatever happens next.
Entry 21
Where Project Ceylon Stands Today — September 6, 2026
This closes out the retrospective backfill with an honest accounting: what's proven, what's partial, what's planned, and what flatly isn't built yet. Starting tomorrow, this becomes a real…
Entry 20
52, 53, and Other Numbers That Ruin Your Evening
With the scheduler starvation bug fixed, the next client finally ran — and immediately failed for a much dumber reason. Shared logic assumed channel 52. It was actually assigned channel 53.
Entry 19
The RNG Bug That Wasn't an RNG Bug
Two SecureRandom client tests were failing. Every instinct said the bug was in the random-number code. It wasn't. It was a busy-spinning restart starving lower-priority services out of CPU…
Entry 18
Random Numbers Turn Out to Be a Whole Damn Subsystem
I expected to spend an afternoon on random numbers. I spent a lot longer than an afternoon on random numbers, because it turns out trustworthy entropy is genuinely its own subsystem, not a…
Entry 17
One Management API, Whether You Click It or Type It
Whether you're driving Ceylon through a GUI or a terminal, it should be the same semantic backend underneath, not two tools that happen to overlap most of the time.
Entry 16
Applications Without Pretending We're Unix
An application on Ceylon isn't automatically a Unix process wearing a different hat. Building the runtime meant deciding, on purpose, what to borrow from that model and what to leave behind.
Entry 15
Ceylon Horos: The Lion at the Boundary
Horos is Ceylon's security umbrella — the conceptual boundary between identity, credentials, authentication, sessions, and authority. The name comes from an old Greek word for a limit or…
Entry 14
From Nu-Day to Ceylon: Stop Building the Workstation and Build the Computer
The pivot: one shared platform, validated across multiple profiles — workstation, server, security appliance, media workstation, development — instead of one narrowly-scoped media…
Entry 13
Why Project Nu-Day Failed
"Failed" doesn't mean nothing worked. It means the project's boundaries stopped making sense. Building a real media workstation meant building an entire operating platform underneath it…
Entry 12
Project Nu-Day: What Actually Worked
Before I get into why Nu-Day didn't survive, it deserves an honest accounting of what it actually proved. A working path is not the same thing as a finished subsystem, but it's not nothing…
Entry 11
Browse by tag
All 95 tags, A to Z. The number is how many entries use each tag.