Hmm, I personally place Nix at the same level as Arch, because I see both distros being hard to get into because of how different they do stuff when compared to the average OS.
Maybe the real level up is trying to run BSD on unsupported hardware?
Arch is easier in my opinion, at least if you want to leverage the power NixOS can offer. A simple /etc/nixos/configuration.nix maybe not, but once you enter custom options / submodule territory and use stuff like lib.mapAttrs, I’d say NixOS is quite harder. Or just a more complex overrideAttrs. But then again, Arch doesn’t have an equivalent to that…
Let’s skip all intermediate quotes and directly jump to the xkcd reference:
I only program with butterflies.
Of course, there is an Emacs command for that: good ol’ C-x M-c M-butterfly
Hmm, I personally place Nix at the same level as Arch, because I see both distros being hard to get into because of how different they do stuff when compared to the average OS.
Maybe the real level up is trying to run BSD on unsupported hardware?
Arch is easier in my opinion, at least if you want to leverage the power NixOS can offer. A simple
/etc/nixos/configuration.nixmaybe not, but once you enter custom options / submodule territory and use stuff likelib.mapAttrs, I’d say NixOS is quite harder. Or just a more complexoverrideAttrs. But then again, Arch doesn’t have an equivalent to that…The real level up is bare-metal Emacs.
Shame this OS does not come with a solid text editor.
Text editors are bloat, I only use punch cards
Let’s skip all intermediate quotes and directly jump to the xkcd reference: I only program with butterflies. Of course, there is an Emacs command for that: good ol’ C-x M-c M-butterfly