Exactly where I’m at. I’ve had no issues with it, I have my home computer all set up and customized over the last 3 years, I’m not doing that again just to say that I’m on a different distro unless something goes very wrong.

Manjaro is great. I keep on coming back to it time to time.

Fantastic distro.

None of the criticisms people have against it affect me.

Yeah, I use Ubuntu LTS on my server because updates make me nervous. I can’t just update it all willy-nilly. If something goes wrong during an update, I must stop what I’m doing and get it up ASAP.

A few months ago I accidentally deleted grub the morning before I went to an all day concert, and I had lots of unhappy people that were using services that I host. Luckily that was an easy fix.

My laptop, though? I use Opensuse Tumbleweed. I’m fine with the rolling release for my laptop. Just not my server.

Also not OP, but I learned about the pain of Nvidia drivers the hard way. No way in hell am I letting my system auto update on a work day

NixOS has snapshots built in as well but I’ve never had to actually use them to recover anything because Nix packages are built in isolation from one another, and their dependencies are declared, so packages can’t break each other when installing or upgrading them.

NixOS is also an immutable distro, which prevents accidental bad changes to the system. Tumbleweed is very friendly and stable compared to many other distros out there, but it’s still vulnerable to accidental breakage in the same ways most other distros are. I think the cherry on top for the average joe using Nix compared to OpenSUSE, however, is just the fact that the Nixpkgs repository absolutely dwarfs OpenSUSE’s.

Luckily, if you prefer to stick with whatever distro you’re running already, but want the power of the Nix package manager, you can get the best of both worlds and install just Nix (without NixOS) on any distro.

Yes, although the thing on my desk is just an x-term & media player, so “desktop system” doesn’t mean that much…

Mostly video performance (1080 vid stuttered badly, while it plays fine on the same machine under linux.) & compatability. (Not that I want to run a browser on my x-term, but it would be nice to have as a fallback option. Can’t install anything recent.) Oh, and extended attributes in the filesystem. I REALLY like being able to add name=val tags to a file. It’s immensely useful. That might be my favorite feature of linux? Funny.

Also, I was in the midst of switching from Solaris to Linux on my server, so it just seemed like a good idea to run the same OS on the desktop.

What do you use? What are some problems you have with Slackware?

It all began with Nix software build system and package manager; they needee a way to build, compile software in a reproducible way. That is, if it builds on my machine, it should build on yours too given some constraints. Then they build a whole package repository for such sofware or package definitions, Nixpkgs, that can be build or retrieved using Nix package manager. Nixpkgs grew to be a repository for enabling runnig an GNU Linux OS on it: NixOS. It is declarative in the sense you write what it should contain like packages and behaves like system services. For example, see https://git.sr.ht/~misterio/nix-config.

Atomic in the sense that when you want to change system’s configuration or state, everything should suceed in that update, otherwise fails; it is everything or nothing. This enables storing previous and current system revisions, so can rollback to previous state.

Nix plus things like flakes, nix shell, enables a build inviroment akin to containers, but much better, correct, and flexible.

Haskell is just an ecossytem Nixpkgs support.

I prefer to come at it from an immediate utility level, and I think a good place to start with that is home-manager.

You can install nix and home-manager on any Linux distribution or MacOs. It lets you, in a single place, specify what packages you want, services you want to run at the user level, and what config files you want in your home directory. For a lot of things, home-manager has built-in config options, but you can also specify arbitrary config files.

Then, you can take this one file to a new computer, and with no other config, have everything set-up the way you like it.

NixOs allows you to do this for your whole system.

It also has a bunch of other benefits, which tie-in to the jargon you bring up. But if you want to check it out, I’d worry about that later.

Step 1. Write down all the packages you want in a list, configure all of your system with predefined config options Step 2. Rebuild Step 3. Use packages

Step 4. Configure more settings and install more packages Step 5. Realise you broke everything Step 6. Boot previous version of config and continue with your life

Also makes configuring your system far simpler

Installing gnome is as simple as putting

services.xserver.enable = true;
services.xserver.displayManager.gdm.enable = true;
services.xserver.desktopManager.gnome.enable = true;

In your config file and then doing nixos-rebuild switch

deleted by creator

I haven’t really used Tool/Distrobox so correct me if I’m wrong, but don’t they basically contain a sort of a lightweight copy of the OS (minus the kernel/and some core stuff? ), so wouldn’t you have to keep all your containers up-to-date as well, in addition to your host OS? I’m just wondering how much of a double-up/space waste there is going on with such a setup.

As a fellow Silverblue user, I really wanted to like NixOS. I was surprised to discover it did not support declarative management of flatpak workflows, which pretty much eliminated it as an option for me. That, combined with its highly unconventional filesystem hierarchy, and its cumbersome configuration and project documentation was enough to send me back to Silverblue.

Don’t get me wrong, NixOS is very powerful and an excellent solution for some use cases; it just wasn’t right for mine.