long-term Nix and NixOS users, why do you still use Nix/NixOS? Has your interest about it diminish?
I’ve been using Nix and NixOS for 4 years now. While I like using it for my PCs and tried using it for servers with success, I think its ecosystem still is immature for development and production purposes, and thus my passion for Nix has faded.
So my question is what keeps you using Nix or NixOS? How have you been using it? Do you still feel passion and hype for it?
I’ve been using it for around 5 years on my desktop and VM servers. I have one template config for my servers and just add a new service for whatever I’m doing on that server. And their services list just keeps getting better.
I’ve been using NixOS for six years, and while I’m not a hyped as I was in the beginning, I still use it over anything else. My distro hopping days are over, I’d rather do something else with my time and have my computer just work.
It give me piece of mind that I can always get back to working system. Setting up new desktops is just figuring out hardware, the rest of my stuff is just there waiting to go. And its super nice to be able to upgrade without fear of a broken system.
It was a lot of learning up front, but now I feel like the maintenance is way less than with other distros.
I’ve been using NixOS for two years, and I’m not as hyped as I used to be. I’m a little nostalgic for my first days trying out Mint and Manjaro, and I’d like to try out Kinoite and maybe Guix on another drive, but I don’t think I could ever switch to using those permanently.
Setting dotfiles through home manager is nice, especially since they’re synced between my pc and laptop, and if I ever need to reinstall or set up a new device it’s all there. It doesn’t seem that cool after getting used to it, but just editing plain config files seems pretty messy and unorganized after using home manager. Flakes are pretty cool and being able to nix run any program without installing it is nice.
My impermanence setup is a little annoying though, and since I use Syncthing to sync my KDE dotfiles between devices that can bug out sometimes, but it seems nicer and more organized than not having impermanence so I don’t think I could go back there either.
I’ve been using guix for a little over a year and a half and be forewarned theres way fewer of us so packages get updated super slowly (if at all).
I will say the best thing about guix is that scheme is hands down a better language for doing what Nix/Guix is trying to accomplish and of the few packages I’ve written for Nix and Guix, I’ve had a much nicer time writing Guix packages.
I’ve been using Nix for 8 years and can’t imagine using anything else. Especially on severs it is in a completely different league than the next best thing (which I guess is a myriad of docker containers?) I’ve also been using it on desktop for nearly that long and it is also pretty great. It maybe isn’t quite as polished as some other distributions like Fedora or Ubuntu but I haven’t had a major issue. Plus being able to set up a new system and being 95% of the way to my full customized experience is incredibly. Especially nice because I have a desktop and laptop so keeping their configs in sync is great.
For development I have found it is pretty nice. I mostly use nix-shell to make dependencies available. There is the occasional thing that doesn’t work because they want to download prebuilt binaries over the internet, but honestly I mostly consider that a feature that these don’t work by default. Plus if you need to get these working you can just use steam-run and it works correctly 99% of the time.
I have only been on nixos a few weeks. Absolutely loving it. I keep seeing people talking about this needing to use steam-run for binaries. I don’t understand what this means at all tbh. I’m a newbie web Dev so everything I’ve made so far has just been running in Firefox and node. Will I ever have to worry about this? Or is this just a issue for making software outside of the browser?
You don’t need it often. Just if you are running pre-built binaries. There are other ways to work around it but steam-run is a big hammer that basically sets up an environment that looks like a “regular” distro with a bunch of command libraries available for running that command.
One example I had in web-dev was Prisma which wants to download some pre-built binaries when installed via npm. These are available in nixpkgs (and I am now using these) but the first way to get it working was just to run it via steam-run.
I don’t know much about distrobox but probably. It seems like distrobox would be a bit more isolated from the host system. (Which can be both a prod or a con depending on your use case.) steam-run will also reuse the host libraries rather than downloading a new copy so it will be more efficient.
I’ve only been using it for about a year, but as of now I can’t imagine ever going back to imperative system configuration. Having my infrastructure declared in its entirety by a version controlled code base is just too comfy.
Add comment