Why My Local Machine Runs on Fedora Silverblue

Most developers configure their local OS by installing global libraries, node packages, and database instances. Over time, their machine accumulates configuration drift, leading to "works on my machine" issues and broken system upgrades.

I run Fedora Silverblue.

Silverblue is an immutable desktop operating system. The host OS /usr and root directories are read-only and transactional. Upgrades are staged as read-only OS tree commits (rpm-ostree). If an update fails, I roll back instantly to the previous boot state.

The Platform Workflow

Because the host is immutable, I am forced to isolate every single dev workflow:

1. Host Apps: Installed strictly as flatpaks.
2. Workloads & CLI Compilers: Run inside Toolboxes (rootless Podman container namespaces). I have separate toolboxes for Go, Rust, python-dev, and local model debugging.
3. Reproducibility: My local configurations are fully auditable, isolated, and scriptable. It trains you to treat your workstation like production infrastructure.