Edit:

I did not know about Kinoite. I am definitely checking it out, sounds similar to what made me interested in Vanilla OS 2

I’ve started recommending it to others, while personally I’m happier with Arch’s more transparent and simplified architecture and development, plus rolling release to avoid mass breakage on full upgrades.

but rolling-release distros does mean one day you might update and reboot and something is broken. it's more maintenance than fedora.

1. with Fedora Atomic you get an operating system with the reliability and resistance to entropy and ability to power wash of Chrome OS, but also the ability to be changed via building your own custom image (its easy, check out BlueBuild) or with easily reversable overlays, plus an update cadence that offers an excellent middle ground between rolling release and point release — you get all non major version updates to your image's software basically immediately, but major versions wait for every 6 months so they can be integration tested and stuff.

2. And then with Distrobox you get the ability to trivially create a containerized environment with your Linux distribution of choice inside (can be different from the host), that nevertheless integrates almost seamlessly with the host (including having access to all of your hardware devices and your home directory and being able to trivially export applications, as well as easily open a shell inside the container with a simple terminal command), so you can have your cake and eat it too: a fully bleeding edge rolling release distro like Fedora Rawhide or Arch Linux inside your distro box to get the most up to date developer tools, but a more stable system as your host. And if something goes wrong in the container you can easily just blow it away and regenerate it since Distrobox has a declarative container spec (distrobox assemble). For GUI management of Distroboxes check out Pytaxis and BoxBuddy-rs.

There are some things you should know if you go this route though that will save you a lot of pain and frustration:

1. Fedora Atomic is really barebones by default, and since layering is kind of painful it can be really annoying to do the system administration necessary to get it set up; especially if you have an Nvidia card and you have to do all the typical annoying shit you have to do on Linux to set that up. So instead of using vanilla Fedora Atomic, I highly recommend checking out Universal Blue[0], which offers pre-built Fedora Atomic images with all of that annoying setup and system administration done for you already. Their headline images (Bazzite and Bluefin) are really opinionated, but don't worry about that, their base images[1] are perfectly usable too! That's what I use :)

2. Layering packages via rpm-ostree should not be used for just random system utilities or applications. That's not how it is intended to be used, and that way lies only pain. The whole point is that the applications you use as a user, including terminal ones, should be separate from the core system, and not dependent on it, so they can be updated separately and not break each other. Layers, since they are updated by the system package manager, must be versioned in lockstep with the rest of the system, and the system image will fail to build if it can't update the layers you have, so really only use it for things you consider part of your essential OS. People who forget this tend to come away really hating Atomic distros. For your development environment or any build environments you need, create distroboxes and install applications inside them; for GUI applications, just use Flatpak, or install the application inside a distrobox and use distrobox-export to integrate the app into the host. If distrobox feels too heavyweight, or you just want various sundry utilities installed on your host system, then I recommend using something like Homebrew or Nix or Guix or Pkgsrc, that is, any package manager that installs things to your home directory in a way that is cleanly separated from your host system and independently updated. Universal Blue images come with a script to get Homebrew all set up for you. Wouldn't have been my first choice, but its very convenient.

For more on the benefits of this, see this pastebin article I made: https://rentry.co/mm2qcwzh

If you're wondering what the advantage of this is over Nix, the most important to advantages for me are that:

1. Nix's directory structure is basically completely unreadable and unusable for human beings in a way that is far worse than the default posix directory structure

2. Nix requires absolutely every program and package that runs on it to be custom patched to deal with its alternate directory structure, and while sure yes it's package repository is gigantic so a lot of that work is done for you, it can still cause weird problems and make things much more unreliable and good luck if there's a package that isn't there or hasn't been updated for a while. I'm on an emacs Discord and apparently installing it on Nix is very difficult. It's just another layer of possible incompatibility and failure and annoyance on top of the stack of those layers that compose linux.

Meanwhile, you got most of the same benefits on an atomic distro, except:

1. it's all completely human readable

2. uses standardized technology so it's already compatible with everything without having to do any work

3. you can get fully different distros inside distro boxes, unlike with and Nix's equivalent.

The other thing is that with nix, you configure your entire system at a layer of abstraction above what's actually happening on the system — it's not like that declarative config is actually directly deciding how the system operates, no, it's just layered on top of all of the existing crap Linux has going on, and you're just hoping that it can automatically, imperatively perform the actions necessary to keep your system in line with the config.

That, and to get the same level of resistance to entropy and reversibility and ability to power wash and rebase and cherry-pick changes and stuff that you get with an atomic distro on nix, you would have to Version Control your Nix config and then also be very very careful with manually committing with informative commit names at regular intervals every time you make a change and stuff, instead of it being handled automatically for you and not requiring an extra version control tool slapped on top.

Plus, Nix doesn't benefit from the minor, but still meaningful in my opinion, security benefits of an immutable image-based distro.

[0]: https://universal-blue.org/ [1]: https://github.com/orgs/ublue-os/packages [2]: https://distrobox.it/

Also drawbacks for me when using nix:

- I needed to greatly increase boot partiton, because nix stores there linux kernels. Whith dual-booting Windows, I created 2GB partiton at the end of disk. Thankfulluly Windows reused it.

- vscode was having strange laggines on nix.

- nix language is quite strange but also imo taught poorly. This was my attempt to demistify it https://github.com/rofrol/nix-for-javascript-developers.

btw. nice remark about nix beeing declarative but beneath is Linux not-declarative. It is like functional programming, but you still have some internal state of components that can clash with your functional top-down approach.

Yeah. That's what always made me loathe to try it out. I'm glad there's someone else that feels that way.

Why does NixOS work for me?

I got attracted to Nix because of the possibility of being on the bleeding edge. According to repology Nix related package repositories are far up and to the right, their own cluster. In fact, only Arch is getting close by, but not being as good in terms of freshness, as can be seen from the position of AUR below [2].

1: https://mihai.page/nixos-and-me/

2: https://repology.org/graph/map_repo_size_fresh.svg - even nixpkgs 24.05 stable is so far ahead of every other repo it's not funny.

1. How friendly is the installer? I can get a second hand machine in which I can afford to nuke the disk and let Nix take it all but what if I need to install it side-by-side with my existing Windows install on my main laptop where I have a custom partitioning scheme? Ubuntu's installer provides sufficient flexibility to able to re-use partitions without overwriting them, allocate whatever mount point I want, resize things etc. I have been using Linux for close to 20 years but fdisk still spooks me.

2. How easy is multi-monitor setup and switching between setups? I have a main monitor that I usually use but occasionally I also use the laptop screen as a second display and sometimes I just use the laptop screen.

3. The 1st link alludes to be able to rollback changes from grub? How? What are my recovery options if I mess up the system?

2. I'm using a laptop with AMD/NVIDIA on Wayland with KDE, this is no problem. This question is in the domain of your display server and compositor, not the base distro.

I choose the previous build from grub, and then rollback my config files from git and rebuild. Every build creates an entry on the boot menu so I can go back to any previous iteration of my setup (I do have it set to only keep the last 15 builds)

1. The installer is Calamares. It's fantastic and fully user-friendly, no need to worry about it.

2. I'll speak for KDE6 which I personally find superior to GNOME. You can have either with NixOS. I don't think there's anything specific to NixOS on multi-monitor functionality. There's a menu accessed either through a keyboard shortcut or system tray that allows any of the 5 permutations laptop/monitor. And it pops up as an OSD menu whenever you connect a monitor. I'd say the functionality is 'done'.

3. I suggest you read up on how Nix works, once you understand it you can understand NixOS better. To summarize, all programs in your system are stored in /nix/store and accessed through symlinks. You don't access /bin/bash, you access the bash executable stored in /nix/store through its symlink in your PATH. And all the symlinks are stored in a single directory. This directory is called a profile. There are multiple profiles. With NixOS, not only just executables but the system configuration data (users, passwords, mounted disks, desktop environment settings, traditionally in /etc) is also stored in profiles. This way you can have multiple 'whole system configuration's all containing different system configurations, arbitrary versions of arbitrary programs, and they don't conflict. During the boot, you can choose between different profiles. It's not limited to grub, systemd-boot also works.