How long have you been using Linux, so on the one hand you still keep thinking about Windows. And on the other hand you already progressed to an Arch derivate, use BTRFS, snapshots, a non-standard bootloader and all that stuff?

I like NixOS. But it’s really for people with too much spare time to learn new programming languages, abstract concepts and weird quirks. It’s great. But sometimes you’ll also do a simple nixos-rebuild switch and it’ll greet you with 4 pages of gibberish. Or you’ll spend 3h packaging some weird Python stuff, because you can’t just install and run it like on a regular distro 😅

Pardon me for asking so … but if you yearn for the “stability” (“simplicity”?) of Windows why not use a Linux distro with an approach more similar to that?

So something not Arch based, … and even tho NixOS almost kinda is the correct direction (for an arch-ish thing), I got the feeling you don’t really want to configure your system & potentially upkeep that config?

Also to note that the actual issue wasn’t fully diagnosed. Reinstalling the full os to fix an update is fairly extreme for your mainstream Linux these days.

But to be at least a bit on topic - bcs I need “simplicity” & “stability” at times when I can’t even (for months on end) I use Tumbleweed (rolling distro).

This will sound like heresy to some, but get away from the bleeding edge. You probably don’t need the absolute latest version of every little thing. It can feel cool knowing you know how to fix a borked install but actually having to do so sucks. Dump the hype and get to something stable for your daily driver. If you want to experiment, do it on another drive/machine. Building a custom rocketship is cool, but you should probably build it without breaking the truck you use to go get parts.

You must have been of Microslop for a while if you think frustrating issues on update is a Linux thing. Just last a couple weeks ago, Microsoft released a security update that locked people out of their “C” drive. (In Windows, this is bad)

What would your ultimate distro be like?

… Debian.

Under linux you have the option to not reboot after an update, use that power wisely.

You did not, so you took a risk and lost.

Im always surprised how different the windows expirience seems to be for many people or do they ignore all the searching for drivers, editing registry entries, running sketchy bats, trying compatibility modes until something works, random blue screens, shutdowns that are reboots.

Why sometimes Linux is hard to switch to

Switching is easy. Sticking to it is harder and involves relearning most of your activities in a new context.

So now I face another reinstall…

I’d honestly think that CachyOS was more ‘sturdy’. Though, I suppose it’s curious that you don’t mention anything about your troubleshooting attempts. Beyond your rollbacks in hopes of resolving the issue*. If you don’t like/want to (learn to) troubleshoot, then reconsider if CachyOS is your home.

FWIW, over (almost) 4 years of Fedora Atomic, I was only once ‘forced’ to reinstall; which happened in the first week (or so). And that was 100% a user error.

This and having to dive into the deep end of terminal commands to get drivers, programs or games working can be quite frustrating.

This isn’t recognizable to me. Would you be so kind to clarify/elaborate? Perhaps with an example even?

I understand why people are turned off and go back to Windows…

The only time I felt this, was when I just cold-turkey switched to Fedora Silverblue and bashed my head to the wall when trying to implement Madaidan’s hardening 😅. But, again, that was just very naive.

Onto NixOS for me.

NixOS is definitely based. So go for it.

What would your ultimate distro be like?

Stateless, and hardened AF. So, probably an amalgamation between your favorite security-focused Linux (be it secureblue or Qubes OS) and NixOS for its impermanence module.

Every modern distro keeps previous kernel boot entries available at boot time. You don’t need to use snapshots to simply not boot a potentially problematic kernel update.

There are literally near zero reasons to ever have to reinstall any Linux install. Moving to a more complex distribution isn’t going to solve your problem here, which is just learning a different workflow. That workflow being more akin to software development workflows: if something fucks up, just revert.

If I’m being completely honest, it sounds like you hit a problem and then just kinda gave up (I’m not trying to sound mean or anything - please don’t take it that way).

If I were in that situation I would probably drop to a terminal (ex. CTRL+ALT+3) and try to find what failed (journalctl). Especially if the screen just stayed black I would probably wonder what packages I just updated. I’m not going to remember, but it’s probably something graphical. Maybe I installed nvidia dkms packages and I have a mismatch or I decided to try out a different login manager and it happens to not support Wayland or something. Snapshots would be my last resort, not my first.

As far as NixOS, I love it. Its incredibly stable and the declarative language is really handy to write in. I’m not aware of any graphical store though (outside of maybe some github project). Its declarative meaning you write the configuration.nix file and import any secondary files into the config. And packages are installed declaratively:

environment.systemPackages = with pkgs; [
    pkgs.gnome-tweaks
    pkgs.gnome-control-center
    pkgs.gnome-terminal
}

I would say if you are wanting GUI that NixOS is probably not a great choice. I mean just to get installed package version, you’re going to have to do a one-liner (mine for example):

#!/bin/bash 
find /run/current-system/sw/bin/ -type l -exec readlink {} \; | sed -E 's|[^-]+-([^/]+)/.*|\1|g' | sort -ui