

Im honestly more interested in Nix, as even with all the chaos it feels like it has good technical momentum. I just wish there was something equivalent to Geerlings “Ansibles for devops” or Shotts “The linux command line” for it.
Im honestly more interested in Nix, as even with all the chaos it feels like it has good technical momentum. I just wish there was something equivalent to Geerlings “Ansibles for devops” or Shotts “The linux command line” for it.
As someone who is curious about Nix but has given up after trying to wade through the myriad and conflicting “getting started” resources for it, I cant imagine how bad guix docs must be for a Nix enthusiast to adandon it.
It reads as an “honor” system rather than any objective exclusionary mechanism. Steering committee members are expected, and to their credit, were considered to have done so, but it all seems like judgement calls.
It is fully possible that grey areas or instances where other SC members didn’t personally care, were not met with recusal.
It would overall be better to not have those conflicts be likely or even possible.
That’s one the books I tried to get through. Maybe it was in a more raw state at the time, but it didn’t click for me.