Today I talk about the most overrated Linux distros. Be prepared for some circular reasoning. 👇 PULL IT DOWN FOR THE GOOD STUFF 👇Ko-fi - https://ko-fi.com/...
I’m very critical of all the immutable distrubtions - as an old timer in tech I’ve seen so many things come and go. I’m also curious, ofcourse, and already tried out a VM with NixOS and everything seemed fine.
But I’m going to wait it out before something like that becomes my main driver, I have a job to do (development, systems, stuff) and I cannot afford to say “sorry little to no progress today, my OS needs tinkering”.
(Feel free to tell me I’m wrong :-) I love to tinker with new stuff).
I still need to give NixOS the college try. The docs are slowly getting better but other than that I have heard great things from all over the Internet about it once you get your head around it. I failed at figuring it out on my own but the day will come where it makes sense I’m sure.
I think one of the issues with nixos learning materials is that they eschew talking about how to write your own packages. but to really understand anything, you have to get your head around writing and modifying packages. in nix, a package is just a build step that can do I/O during particular phases and produces an output to the nix store, so they’re an essential building block for anything that isn’t utterly trivial.
the other major stumbling block is working out how modules (the things that let you write config for the system) can actually be composed. adding a new module to imports gives you new config params you can set so you can organize your system config in terms of modules and packages to make things work the way you like.
Nix Pills are the canonical learning material for packages. I don’t know of any good learning material for modules - I learned by working on nixpkgs and another involved project that made extensive use of modules.
lastly, nix config files are written in the nix language and it’s a bit idiosyncratic. it almost looks and feels like Haskell but it’s slightly different in important ways. there’s no way around learning it if you have multiple systems and want to share config between them.
Funny. Whole reason I use nixos is because I cba to tinker with my systems anymore. Tell me another OS with which I can manage 20+ systems with even less effort and I’d consider switching.
Ah but then you are talking about servers? That would be a different story!
The machine that I use for development (laptop) should always work (I would trust nixos with this) and if I want to spin up a container (docker run) or install an application (apt install)or change my vpn client configuration it is currently effortless and I’m not sure nixos can do that.
Actually using nixos for some of my private servers would be a nice use case…
I use it for workstations, laptops and servers alike. I also configure them all on my home pc and remote push the config. Been a while since I manually SSH’d onto one of my machines…
I feel like it is too complicated for a desktop user. Linux is already complicated enough. On Silverblue I had to do some mental gymnastic to make some things work because everything is just made for Workstation. I don’t think the advantages outweigh the benefits
I’m very critical of all the immutable distrubtions - as an old timer in tech I’ve seen so many things come and go. I’m also curious, ofcourse, and already tried out a VM with NixOS and everything seemed fine. But I’m going to wait it out before something like that becomes my main driver, I have a job to do (development, systems, stuff) and I cannot afford to say “sorry little to no progress today, my OS needs tinkering”.
(Feel free to tell me I’m wrong :-) I love to tinker with new stuff).
I still need to give NixOS the college try. The docs are slowly getting better but other than that I have heard great things from all over the Internet about it once you get your head around it. I failed at figuring it out on my own but the day will come where it makes sense I’m sure.
I think one of the issues with nixos learning materials is that they eschew talking about how to write your own packages. but to really understand anything, you have to get your head around writing and modifying packages. in nix, a package is just a build step that can do I/O during particular phases and produces an output to the nix store, so they’re an essential building block for anything that isn’t utterly trivial.
the other major stumbling block is working out how modules (the things that let you write config for the system) can actually be composed. adding a new module to imports gives you new config params you can set so you can organize your system config in terms of modules and packages to make things work the way you like.
Nix Pills are the canonical learning material for packages. I don’t know of any good learning material for modules - I learned by working on nixpkgs and another involved project that made extensive use of modules.
lastly, nix config files are written in the nix language and it’s a bit idiosyncratic. it almost looks and feels like Haskell but it’s slightly different in important ways. there’s no way around learning it if you have multiple systems and want to share config between them.
For learning how to write and modify packages there is the nixpkgs manual, which also contains a section on writing modules.
Between zero-to-nix.com and nixos.wiki, I think there are enough docs to get started with it quickly.
Funny. Whole reason I use nixos is because I cba to tinker with my systems anymore. Tell me another OS with which I can manage 20+ systems with even less effort and I’d consider switching.
Ah but then you are talking about servers? That would be a different story! The machine that I use for development (laptop) should always work (I would trust nixos with this) and if I want to spin up a container (docker run) or install an application (apt install)or change my vpn client configuration it is currently effortless and I’m not sure nixos can do that.
Actually using nixos for some of my private servers would be a nice use case…
I use it for workstations, laptops and servers alike. I also configure them all on my home pc and remote push the config. Been a while since I manually SSH’d onto one of my machines…
I feel like it is too complicated for a desktop user. Linux is already complicated enough. On Silverblue I had to do some mental gymnastic to make some things work because everything is just made for Workstation. I don’t think the advantages outweigh the benefits
I agree that the documentation leaves a lot to be desired. If I may ask, do you remember which things caused the mental gymnastics?