Post

aly
@aly.codes

au contraire my take on nixos is that I do understand it and therefore think it is objectively bad

cafkafk@cafkafk.bsky.social

A lot of peoples take on NixOS is and I quote "I don't understand this therefore it is objectively bad", which some people somehow think is a good take that we have to take seriously

aly
@aly.codes

actually okay to make a serious take: probably my most steaming "nixos is bad" take isn't absolute it's that people way overuse nixpkgs service modules and treat nixos like an orchestrator when it rly rly rly isn't

aly
@aly.codes

I think that is undeniably true, it’s really bad But also like. There is no reason to run most things as systemd services when container orchestration exists

asa
@asap.systems

depends on what you mean by container orchestration docker compose is evil, and I think you can get very far with systemd-maxxing (depending on what you're hosting). I've never actually used kubernetes so I can't speak to that

asa
@asap.systems

it _almost_ does (the merit of 1:1 wrapping systemd config with nix equivalents is up for debate, but at least nix lets you use variables in them), but then puts all your config in a massive fixed point with fake namespaces that takes 10s to evaluate

0 reposts3 likes

aly
@aly.codes

the main thing missing with just writing units yourself is that the deployment and maintenance strategy is just “use ansible…I guess”

asa
@asap.systems

you're talking to the guy who thinks filesystems were a mistake agreed that it's annoying, but it's also not really a design flaw on systemd's part