adept

I don't really like flake-parts or flakelight. I think that part of this is sheer brutalism (I don't mind writing bare Nix) but part of it is a desire to not rely on flakes which don't carry their own weight, following Wirth's principle for compilers.

How can you say this and still use flake-utils? All it does is manage your systems. You can write your own one-liner for that

eachSystem = f: lib.genAttrs systems (system: f nixpkgs.legacyPackages.${system});

Where systems is automatically supplied as a flake input (I think), or you can supply your own list of systems to support. You can then use it like this:

devShells = eachSystem (pkgs: {
    default = # your devshell
}

You can of course modify eachSystem to have more function parameters other than pkgs.

See this blog which initially inspired me not to use flake-utils

Related, and I cannot help but read "bcachefs" as "bitch café"

When it was on sale recently I didn't buy it. Instead I removed all Sony games from my wishlist, knowing they would require PSN even for single player games.

first post I saw

Thanks for your response.

That's exactly what i had in mind. I just wasn't quite sure it would work out as i imagined.

Since i asked this question i have already prepared a second (empty) disk and a disko config to make it all declarative. Before i actually apply this config to my second disk i'm looking into creating a VM to test the disko-partitions

Home-manager is probably what you want.

There are also some flakes (search in the official nixos search in the flakes tab) maybe one of them provides a module you need

OpenZuse

Nushell is pretty nice.

For Rocket league you need to manually enable proton under properties.

Its running without problems for me now

Often even when its on sale i have already lost interest.

Alternatively try nushell. Its basically powershell without ms

Quality can only increase. If people have to think twice about buying games and don't preorder every half- finished game