Introducing Lisa
Lisa is a desktop operating system. It aims for the calm of a Mac desktop: a menu bar along the top, a Dock along the bottom, one way to do each thing, and applications that look and behave as if one company made them, because one did.
This first post says what Lisa is made of, what it runs on, and, honestly, how far along it is.
Three languages, one contract
Lisa is written in three languages, and that is a tooling judgement, not an architectural split:
- Flutter and Dart for everything you see. Every application and every part of the desktop: the Shell, the Dock, the menu bar, Settings, Files. Flutter is a proven UI framework, and nothing in Rust matches it.
- Rust for everything underneath. The daemons, the compositor, boot, signing and the update transaction want a systems language.
- C++ where it cannot be avoided. The Flutter engine’s embedder API is a C interface, so the host that runs each application is C++.
What ties them together is the wire between them, the dev.lisaos.*
interfaces. Both sides used to be written by hand, with nothing but review to
make them agree. Now one contract generates both sides, and the
documentation with them.
On Fedora, without pretending otherwise
Lisa is a layer above a base: a Fedora-family system on real hardware that meets a written platform contract. The base brings the kernel, firmware, Mesa, systemd and drivers. Fedora’s own daemons, such as logind, NetworkManager, BlueZ and PipeWire, are used as they are and are not renamed. Lisa adds its own daemons, the compositor, the frameworks and the desktop.
It ships as one signed image per architecture, updated whole. An update installs beside the running system, and the machine switches to it on the next start, or does not switch at all. Applications are not part of that image: they come from Harbor, Lisa’s application channel, and an OS update never touches them.
Today Lisa runs on an Intel iMac and on an Apple M1 iMac through Asahi Linux.
What the desktop is made of
- The Shell: the menu bar, the Dock, notifications, the window switcher, and Beacon, which finds applications, files and settings as you type.
- Settings, with each pane a page of its own.
- Files, Monitor, Terminal, Preview and Calculator.
- Surfer, a web browser on WebKit.
- Harbor, where applications come from.
- Coder, the tool for building Lisa applications.
Each is a Flutter application on the same frameworks that third-party developers get. There is no private shortcut for the system’s own apps: an application imports only the public framework packs, the same ones anyone else’s application gets.
Written down first
The most unusual thing about Lisa is not in the code. Every decision is written down before it is built, at docs.lisaos.dev, and the code is measured against those pages.
Each page describes the system as it should be. Whatever is not yet so is listed at the bottom under Not yet true, never hidden in the description. All of those lines are gathered on one page, Gaps, which is the honest remainder of the project.
We work in three steps. First the page. Then a test that fails because the code does not do what the page says. Then the behaviour, proven on a real machine before anything is marked done. A change is reviewed by someone who did not write it, and a release is cut only when its gates pass.
How far along it is
Lisa is in development. Releases are cut often and installed on our own machines, but it is not yet ready for anyone else’s.
Each part of it has a page that says what it should do, and a list at the bottom of what it does not do yet. This blog is where we will say what changes, and why.
← All posts