How Feather is built
Its own Wayland compositor, shell and apps in a single Rust project. No borrowed panels, themes or a dozen background services.
Four rules everything rests on
The event loop never blocks
The main loop serves only Wayland, input and finished frames. D-Bus, disk, icons, wallpapers and panel rasterisation run on worker threads with bounded queues; stale results are dropped.
Idle means no work
No timers, no polling, no speculative redraws. If nothing changes on screen the compositor does not wake up: 0 CPU ticks in 5 seconds.
Animations move finished buffers
Springs are solved analytically and applied as GPU transforms. Apps do not redraw while their windows fly, so motion runs at the full refresh rate.
Only what changed is drawn
Damage tracking limits rendering to real regions. Fonts are memory-mapped, only needed glyphs are rasterised, and caches are bounded.
Performance budgets
Budgets steer development and are verified by measurement, not assumption.
| Compositor metric | Budget | Measured |
|---|---|---|
| Idle | 0 CPU ticks in 5 s | 0 |
| Work per frame: scene and GL | ≤ 1 ms | 0.65 ms |
| Blocking on swap | ≤ 0.2 ms | 0.08 ms |
| Private memory, steady state | ≤ 60 MB | 34 MiB |
| Shell UI redraw | ≤ 4 ms CPU | 3.1–3.5 ms |
| Cold start to first frame | ≤ 300 ms | — |
| App animations | = refresh rate | 60 / 60 |
Measured on a Radeon RX 580 (4K, 200% scaling) and in a nested 2880×1800 window. These are individual scenarios on specific hardware. Final acceptance in a real DRM session is still open — see the method and measurement history (in Russian).
What is in the project
All components live in one Cargo workspace. Apps are standalone Wayland clients; the shell UI is built into the compositor.
| feather-de | Compositor, window management, shell, settings and Linux integration |
| feather-ui | Shared library for drawing, text, scaling, localisation and UI elements |
| featherctl / feather-api | Command-line tool and the org.feather.Shell1 D-Bus API |
| feather-files | File manager and open/save dialogs |
| feather-terminal | Terminal with its own DEC/ANSI/VT core |
| feather-notes · preview · textedit · calc | Notes, viewer, editor and calculator |
| feather-monitor · feather-store | System monitor and app store |
src/ compositor, shell, settings, system workers crates/feather-ui/ text, drawing, themes, input, scaling, i18n files/ terminal/ notes/ preview/ textedit/ calc/ protocols/ extra protocol definitions session/ session wrappers, PAM, greetd example packaging/ installers, PKGBUILD, desktop and portal files bench/ functional scenarios and measurements docs/ spec, reports and roadmap
Protocols and integration
Wayland
- xdg-shell and server-side decorations
- wlr-layer-shell: waybar, rofi, mako
- foreign-toplevel: third-party docks and panels
- text-input and input-method: fcitx5, ibus
Graphics and games
- VRR: FreeSync and Adaptive-Sync
- Explicit sync
- Direct scanout of fullscreen frames
- pointer-constraints and relative-pointer
Linux desktop
- XWayland through on-demand xwayland-satellite
- xdg-desktop-portal: screen capture over PipeWire
- StatusNotifierItem: system tray
- DBusMenu and org.gtk.Menus: global menus
Build it yourself
The project builds with plain Cargo. A nested windowed run does not touch your current session.
cargo build --release --locked --workspace dbus-run-session -- cargo test --release --locked --workspace FEATHER_PROFILE=1 target/release/feather-de --windowed
What is not finished yet
The core shell, the apps and much of the integration are done. We do not hide the open areas:
- Physical monitors, hotplug, VRR and sync across different GPUs
- Suspend and resume, Fn keys and Bluetooth accessories on real hardware
- Final acceptance of frame time, startup and memory in a full DRM session
- Protocol checks against real waybar, rofi, fcitx5 and ibus
- Packaging for other distributions