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 application pretending to be small.
If Nu-Day's problem was that a media workstation quietly needed to be a whole platform underneath it, the fix isn't to shrink the ambition back down to fit the old boundary. The fix is to stop pretending the boundary was ever the right shape, and build the platform on purpose instead of by accident. That's Project Ceylon.
One platform, multiple profiles
The core idea is simple to say and a lot of work to actually mean: one shared underlying platform, with multiple validated profiles built on top of it. A Workstation profile. A Server profile. A security-appliance profile I've been calling SBS internally. A Media Workstation profile — Nu-Day's original ambition, now honestly positioned as one profile among several instead of the whole project. A Development profile. And, further out, appliance and micro-device profiles once the shared foundation is solid enough to support them.
The difference between this and what Nu-Day was trying to do isn't really technical — a lot of the actual pieces are the same pieces. The difference is honesty about what's shared infrastructure and what's profile-specific behavior on top of it. Nu-Day tried to be one profile's worth of ambition wearing a full platform's worth of requirements. Ceylon is explicit that the platform comes first, and profiles are validated configurations of it, not separate projects that happen to share a name.
What the shared platform is meant to include, eventually
The long-term list of shared components includes a GUI layer (NuGUI), a terminal and management CLI, a system manager and file manager, authentication, networking, storage, service management, logging, a help system, and application launching. I want to be very direct about something: that is a list of intended shared components, not a list of finished ones. Some of them exist in early form. Some of them exist mostly as a clear design intent and not much implementation yet. I'll be specific about which is which as this journal goes on, and especially in the status-update entries — the whole point of writing this in public, as it happens, is that I don't get to quietly blur that line.
Why this is the right container this time
A profile-based platform means a media workstation can genuinely be a first-class citizen of Ceylon without every other use case having to be a media workstation too, and without the shared authentication, networking, and storage layers having to pretend they only exist to serve one profile's needs. That's the structural fix for Nu-Day's actual problem — not more discipline about scope, a container shaped correctly for what I was actually always trying to build.
The next few entries get into the shared foundation itself, starting with the part that turned out to need the most careful thinking of anything so far: security and identity, under a name I've been calling Horos.
Originally published on The Weekend Report: https://theweekendersproject.com/report/from-nu-day-to-ceylon-stop-building-the-workstation-and-build-the-computer