AltOS Development Blog #1: The Vision
Why Build Another Linux Distro?
Fair question. There are already hundreds of Linux distributions out there. Ubuntu, Fedora, Arch, Manjaro, Pop!_OS... why add another one to the pile?
Because they all have the same fundamental problems.
The Problem with Linux Desktop Environments
Configuration is a Mess
Want to change a setting? Good luck finding where it's stored. Is it in /etc? Maybe ~/.config? Wait, some apps use ~/.local/share. Others have their own hidden folders. Some use JSON, others use XML, some use their own custom formats.
There's no unified system. It's like archaeology - you dig through layers of legacy decisions hoping to find the right file.
Dependency Hell
Update one package. It needs a newer version of a shared library. That breaks three other applications. Now you're troubleshooting for an hour instead of actually doing anything productive.
Traditional package managers share dependencies to save disk space. That made sense in 2005 when hard drives were expensive. It doesn't make sense in 2026 when breaking your system costs way more than 2GB of storage.
Rigid Desktop Environments
GNOME says "this is how panels work." KDE says "this is how widgets work." XFCE says "we're lightweight so you get fewer options."
They all give you some customization - within their predetermined constraints. You can change colors and move panels around, but you can't fundamentally change how the desktop works.
The AltOS Solution
Unified Configuration
Everything in /altos/config/. One directory. TOML format. Version controllable. Easy to backup, easy to sync across machines, easy to understand.
Want to change your theme? Edit /altos/config/desktop/theme.toml. Every application reads from the same config files. Changes apply instantly without restarting anything.
Container-Based Packages
Each application bundles its dependencies in a .alp (AltOS Package) file. Yes, this uses more disk space - about 20-40% more than traditional packages.
But you know what never happens? Updates breaking your system. Each app has exactly the library versions it needs. Update one app, and nothing else is affected.
Modern SSDs are cheap. Your time isn't.
True Customization
AltOS doesn't force a desktop environment philosophy on you. Want Windows-style panels at the bottom? Done. macOS-style menu bar at the top? Easy. Both? Sure. Neither and just use keyboard shortcuts? Go for it.
Change window corner radius, border thickness, title bar height, button layouts - everything is configurable because everything reads from the same theming system.
What I've Designed So Far
I've spent the last few weeks designing AltOS's core architecture. Here's what I have so far:
AltWM: Custom Wayland compositor with advanced window management. Smart snapping, custom zones, multiple workspaces, smooth animations.
AlTerm: Terminal emulator built from scratch in C. Not just another terminal - this is the core text interface layer for AltOS. Phase 0 is complete (working Wayland window with keyboard input).
alp Package Manager: Container-based package system with a smart App Center. Automatic update detection, version rollback, security scanning.
Unified Config System: TOML-based configuration for everything. One place to look, consistent format, easy to manage.
Themes Store: Community marketplace for desktop customizations. Complete desktop makeovers plus individual assets.
Design Philosophy
"AltOS adapts to the machine, not the machine adapts to it."
Older hardware? AltOS automatically simplifies visual effects and disables resource-intensive features. Gaming rig? Full desktop effects, smooth animations, everything enabled.
The system detects your hardware capabilities and configures itself accordingly.
Current Status
Deep in the design phase. I've created 9+ comprehensive specification documents covering desktop environment architecture, Wayland compositor design, package format, unified configuration system, app center design, terminal emulator roadmap, and window management.
AlTerm Phase 0 is complete - I have a working Wayland window with keyboard input and event loop. It's basic, but it's the foundation for everything else.
What's Next?
Next development blog will cover AlTerm in detail - why I'm building a terminal from scratch, what I've learned about Wayland, and the technical architecture.
After that, I'll dive into the package system design, the unified config architecture, and the desktop environment vision.
The Long Road Ahead
Building an operating system is a massive undertaking. This will take years. But every major project starts with a vision and a plan.
Right now, I have both.
The design phase is nearly complete. Implementation comes next. And I'm documenting the entire journey right here.
- James