**Summary**
The presenter, Tris, explains why they moved from a long‑time Ubuntu/Linux setup to NixOS (referred to as “Nyx OS”). The key points are:
- **Massive, up‑to‑date package repository** – NixOS offers roughly three times more fresh packages than other distros, far exceeding even the AUR.
- **Declarative, single‑file configuration** – The entire system (boot loader, networking, users, services, etc.) is defined in `configuration.nix` (plus a separate hardware config). Changing the system is as simple as editing this file and running `nixos-rebuild switch`.
- **Reproducibility & rollback** – Every successful build creates a new boot entry; previous configurations are retained, allowing instant rollback from the boot menu or via `nixos-rebuild switch --rollback`. This makes updates safe and eliminates the fear of breaking the system.
- **Version‑controlled workflow** – Tris scripts the edit‑rebuild cycle, auto‑formats the config, shows a diff, and commits each successful build to Git, giving a full history of system states.
- **Flexibility** – Hardware config is separate, so the same `configuration.nix` can be reused across machines; you can test multiple configs in a day, share configs, or create a personalized live USB.
- **Stability + cutting‑edge** – Because of atomic upgrades and rollback, Tris can enable unattended background updates without sacrificing stability, getting both the latest packages and a reliable system.
- **Ecosystem extras** – Nix Flakes provide exact reproducibility; Home Manager manages dotfiles; the Nix language, while initially unfamiliar, becomes a powerful, unified way to configure everything (services, kernel modules, fonts, groups, etc.).
- **Minor quirks** – Packages do not share dependencies (more disk use but safer), generic binaries need a small tweak, and the configuration language has a learning curve, but the benefits outweigh these issues.
Overall, Tris argues that NixOS uniquely combines a huge fresh‑package repo with declarative, reproducible, and rollback‑safe system management, making it ideal for daily use, content creation, and development.
1. Tris has dual‑booted Linux, primarily Ubuntu, since 2006 and used it as his daily driver for over a decade.
2. He produces all of his videos, podcasts, and music on Linux.
3. In his free time he spends a lot of time gaming on Linux.
4. Linux distributions are primarily differentiated by their package manager (and system).
5. As a user, Tris does not base his choice on the package manager differences.
6. Distributions are not differentiated by desktop environment, color theme, etc.; those can be obtained anywhere.
7. Linux distributions are general‑purpose operating systems.
8. For Tris, the three most important aspects of a Linux distro are features, reproducibility, and stability.
9. The principle he uses to evaluate them is “how many fresh packages can I safely install?”
10. NixOS provides more fresh packages than any other distribution—about three times more.
11. The Arch User Repository has fewer packages and far fewer fresh packages than NixOS.
12. The inflection point where NixOS’s package advantage became clear was around 2022.
13. NixOS’s advantages extend beyond just the number of packages.
14. The video script, links, and images are part of a markdown document freely available on GitHub under a public‑domain license.
15. Two years ago Tris tried using a Steam Deck as his main machine and it worked well.
16. A year ago he tried Sahi Linux on Apple Silicon; both systems are based on Arch Linux.
17. After realizing Apple’s hardware was not as claimed, he switched back to his main desktop and continued using Arch, having converted his dotfiles.
18. A systemd update once reversed his mouse buttons due to a bug in his mouse driver; he filed a bug and it was patched the same afternoon.
19. A kernel update once prevented his machine from booting; he had to reinstall, but he had good backups.
20. NixOS allows both cutting‑edge features and stability.
21. NixOS is built on the Nix package manager, which works differently from apt, pacman, yum, or brew.
22. NixOS uses declarative package management: packages are listed in a configuration file (e.g., package.json, Gemfile, pyproject.toml) and a single install command brings the system to that state.
23. The entire system can be configured from a single declarative package file (plus a separate hardware configuration file).
24. The NixOS installer provides a base configuration split into `configuration.nix` and `hardware-config.nix` by default.
25. `hardware-config.nix` is generated automatically and contains kernel modules, filesystem mount points, and networking tweaks.
26. Separating hardware config allows `configuration.nix` to be shared across multiple machines.
27. NixOS options exist for many applications (e.g., neovim, Steam, Baldur’s Gate 3) to enable or customize them.
28. Configuration can be versioned with Git; storing it on a USB drive lets you reproduce the same system on another machine.
29. You can temporarily boot a friend’s machine with your custom config and revert back easily.
30. Dropping the config file on a bootable NixOS USB creates a personalized live OS.
31. Each successful `nixos-rebuild switch` creates a new boot menu entry, allowing rollback to any previous working generation.
32. Because all previous configurations are saved, it is impossible to leave the system in an unbootable state.
33. Rollback works like booting an older kernel but also reverts all other system changes.
34. A recommended tip is to avoid `nix-env` because it does not interact with the declarative configuration.
35. The declarative model lets you switch all packages and config at once, so you never need to start from scratch; you can adopt others’ configurations trivially and rollback with a single command.
36. You can test many different configurations in a single day.
37. The primary daily loop in NixOS is editing the configuration file and running `nixos-rebuild switch`.
38. Many users create scripts or aliases to streamline this loop; an example script opens the editor, runs auto‑formatting with Alejandra, shows a condensed git diff, rebuilds, discards output, and commits the change to Git with generation metadata.
39. If a build fails, the script prints a readable error; the full log is saved in `nixos-switch.log`.
40. By default NixOS tracks the stable channel; switching to the unstable (bleeding‑edge) channel requires only two commands.
41. You can roll back to the last working configuration from the boot menu if an update causes problems.
42. Because packages do not share dependencies, you can install individual packages from the unstable channel while keeping the rest of the system stable.
43. NixOS cannot run dynamically linked executables built for generic Linux out of the box; adding two lines to the configuration permits normal binaries to work.
44. Creating custom systemd services for arbitrary long‑running commands is trivial in NixOS using the same configuration language.
45. Many system tweaks—kernel modules, XDG MIME type, font settings, X11/Wayland settings, audio backends (PipeWire, Jack), OPG and hardware acceleration, adding users to groups—are performed by editing the same declarative file.
46. The Nix language is a Turing‑complete functional programming language; learning it is worthwhile, though simple configurations can also be written in TOML if the syntax is a barrier.
47. Nix Flakes provide exact reproducibility and richer configuration capabilities.
48. Home Manager is a popular Nix‑based dotfiles manager that integrates well with the Nix ecosystem.
49. Each NixOS package gets its own dependencies (no sharing), which uses more disk space but NixOS mitigates this with file reuse and garbage‑collection options.
50. NixOS is well suited for building per‑project development environments; it can support every language and package without containers or VMs (e.g., the reel.it service).
51. A recommended next video is Vim Joy’s fast guide to getting started with NixOS.
52. Tris offers limited one‑on‑one mentoring slots via Patreon for topics such as Rust, personal organization, creative production, web tech, etc.
53. Patreon supporters can get early access to videos, Discord perks, and have their name in the credits.