The Declarative Fatigue Manual
The Hype of Immutability
In 2026, NixOS is the darling of the dev-ops world. It promises "Reproducible Systems" and "Atomic Rollbacks" through a single configuration file. It sounds like magic. But for most users, NixOS leads to Declarative Fatigue: a state where you spend more time fighting with the Nix language than actually using your computer. Tebian provides the Reproducibility of NixOS with the Familiarity of Debian.
This manual provides the technical critique of the declarative model and explains how Tebian's "Pillar Isolation" is a more human-centric solution.
1. The Nix Trap: Learning a Language to Use an OS
To configure NixOS, you must learn the Nix Language. It is a functional, lazy language with a steep learning curve. Want to install a package? You must edit a .nix file and rebuild. Want to change a shortcut? Edit the file and rebuild. This introduces a "Thinking Barrier" between the user and the system.
The Tebian Alternative
Tebian uses standard Bash and TOML for its scripts and configs. You don't need a degree in computer science to understand tebian-settings. It is a set of transparent scripts that you can read, edit, and run in real-time. We achieve "Reproducibility" by keeping our entire OS logic in a single folder (~/Tebian) that you can copy to any other machine.
2. FHS Compliance: The World is not Nix
NixOS rejects the FHS (Filesystem Hierarchy Standard). It doesn't have /usr/bin or /lib in the traditional sense. Everything lives in the /nix/store. This means that 90% of the world's software—which assumes an FHS layout—will not run on NixOS without custom "packaging" or "wrappers."
Tebian is 100% FHS Compliant. Because we are pure Debian underneath, every binary, every script, and every proprietary tool (like Steam or Discord) works exactly as the developer intended. We don't break the world to fix the OS.
3. Maintenance Overhead
When something goes wrong in NixOS, you have to debug the configuration logic. When something goes wrong in Tebian, you debug the System. Because Tebian follows the standard Linux paradigms, the skills you learn are transferable to every other Linux system in the world. NixOS skills only work on NixOS.
Conclusion: Simple is Better than Sophisticated
The Declarative Fatigue Manual proves that "Statelessness" doesn't require a complex functional language. By using Debian as our base and isolating our configs in ~/Tebian, we provide a system that is easy to move, easy to backup, and—most importantly—easy to use. One ISO. One menu. Zero declarative fatigue.