linuxmemes @lemmy.world 0x4E4F @sh.itjust.works 1y ago

Arch and Gentoo users reading about NixOS

It's not about the destination, it's about the journey.

94 comments

...to get a working config, you need to learn a whole new programming language and figure out the tweaks for each package you want to install, so I'd argue the journey is just as long
- NixOS sounds like a way to avoid learning Linux by learning an abstraction.
  
  that's why I only use my computer with raw system calls, shell is bloat
  
  I'd personally advise against NixOS as a first distribution for that matter. It's a great distribution, but if you want to understand the underlying mechanics, start with something where you interact with them, like Arch or whatever.
  
  That's why I used to use arch btw
  
  Nix is to Linux what Tailwind is to CSS
  
  it's an abstraction yeah but understanding what exactly it is abstracting and how is where you'll get snags, it's definitely not a newbie distro.
- Like everything with Nix, you pay a little more upfront to get a great experience later.
  
  oh yeah, I daily drive NixOS and use it on my homelab as well
- That's not true.
  
  You have to get PhD in functional programming first.
  
  Wait, are you saying my degree has real world use?
- That's why you go for GNU Guix instead, since it's the same kind of concept but configured using the Guile Scheme you already know.
  
  (You do already know Scheme, right?)
  
  the Guile Scheme you already know.
  
  ⬅️➡️👊
- It comes with a working config.
  
  Adding applications and rebuilding is generally trivial.
  
  The problem becomes if you want to use flakes or home manager, which you probably should. The config for those is complicated and poorly documented.
  
  I don't know the programming language. I've been running it for about a month now. If you're not doing anything complicated or doing any crazy conditionals or running one config for 27 boxes it's no different than editing a yaml.
  
  It took me about 2 days to get Nvidia working properly with offloading that was my hardest task so far.
- But, at least in theory, you'll only do it once.
  
  Well, I "did it" for an evening once, it was fun. The next day it got annoying REAL fast. But I do keep the config around, so I guess I can just go back to it eventually to keep doing it.
- I had no experience in nixOS, just went to the package website, it tells you exactly what to add to each section of the config.
  
  Well not everything is packaged and when they aren’t it Can get more complicated to install since nixos doesn’t use the default file system layout. Another thing is that certain programs have assumptions about being able to do certain things like changing their own config files that don’t work well with the nixos way of doing things. (Looking at you fish(it works but you can’t manage your configuration for it(pretty sure?)with nix))
- not to mention how many things they want to go through their system. getting vim set up “their way” while also trying to install python3 support, vimtex, and plug-vim was almost impossible. not to mention finding a way to store the vim configs separately from the rest of nixos. (i use vim on multiple operating systems so switching everything to the nixos wasn’t a viable option.)
  
  maybe there was a better way to do it that i didn’t know about, but boy did i try to find it.
  
  you can just include dotfiles and the like in a nix config, while it's not the recommended way it usually works
  
  in my experience installing support for most things is way easier on nix, as long as they're already packaged well. I'm still scared of the eventual time when I'll have to create my own package for the nix store to install from source
- The hard part is unlearning last century distro mindset, not this.
- Idk flatpak and docker are pretty easy to set up. If anything gets too complicated it's easy to go back to old reliable.
- You still need to figure out the tweaks on other systems. Unless you want the Nvidia machine learning to complain that your C compiler is the wrong version and exit. Or maybe you'd prefer to deal with a package calling ps and parsing its output (?!) but you have ps that's a different version so the output doesn't parse the same
  
  I mean, when have we ever had a system that is working without any tweaks? Once you install third party packages, there's so many things that can go wrong
How often do you reinstall your OS? In practice never, I installed Arch around 8 years ago on one computer and that's the install I have today still. I copied it twice to a bigger SSD but that's kind of it.
- There is a certain thrill when you nuke your disk to install a distro you never tried before. I actually just nuke one of my laptop last night to try void linux.
  
  I was wondering if Void was still popular. It was kind of feeling like NixOS took all its hype
  
  I'm reporting you to the Ubuntu police!
- Yeah, I don't think that's the best selling point for desktop use. For me it's having all my configs for all my devices in a single place, checked in git, with bits of config I can easily share between my different devices.
- Hey, man. Some of us just suck at everything but reinstalling.
- You clearly don't have a software hoarding problem
- Easy install is not the only benefit. You also get fearless upgrades. When I upgrade my Nvidia driver and it inevitably exposes bugs in one of my apps, I can always jump back to the previous build version without uninstalling anything.
- Damn... 8 years? I made it almost two years with tumbleweed on my work laptop.
  
  I like mixing it up, trying different diatros and various programs. After awhile, a fresh install just feels nice...
- Every few months or so? There is always that one distro that sounds cool and maybe it's better than what you are using atm. Yeah, sure. It's mostly a waste of time and I keep coming back to Arch after a few days, but without this drive I would not have ever tried Arch in the first place. So because of this I found my favorite distro, but I can also never be 100% sure it's the best distro. Pros and cons, I guess.
- Could I maintain the same OS install for the life of a device? Sure. Can I resist disro hopping? Nope!
  
  I made it, I think, 3 years on a Fedora install once.
- I didn't reinstall my OS because I wanted to. Ubuntu messed up the upgrade from 20 LTS to 22 LTS. There was some message in the console, but an hour later I forgot about it and shut off the computer without checking the message again
  
  When it came back it was a terminal and I had no working WiFi. I googled how to do WiFi on Ubuntu from the terminal, but the answers all told me about the previous WiFi on Ubuntu and I didn't even have that daemon
  
  Eventually I wiped the drive and installed NixOS because it backs up your previous configs. When an upgrade fails you just undo and go to the previous working version.
- Same. Even for Windows…why reinstall so much? I installed W10 1607 and I’ve just been installing updates. Same for my Linux machines. Just upgrade and be done people.
- Maybe not useful for yourself alone, but the benefit of being able to share your entire config with others doesn't sound bad
- Main machine was last installed with Ubuntu 14.04 LTS. Running 22.04 now. Gonna celebrate a tin anniversary this year! 🎊
  
  Installed 22.04 few months ago, did my configs, and then subscribed to Ubuntu Pro (free for five devices). Now I can enjoy a stable experience for at least a decade.
nix being 20 years old and still lacking decent documentation on the language it's what hurts me the most, because the people who do know it works so some amazing things with it
- Imagine if NixOS had as good a wiki as Arch. Personally, I wouldn't bother with another distribution again.
  
  They released their wiki apparently on April 1st.
  
  So now we need just to fill it with the missing content. (which there is a lot). And it will be as good as the arch one..... In 20 years.
  
  Or smb made a bad April's fool and actually their wiki is older.
  
  Nixos has made me a better software engineer, I hope it takes off
- nix is 20 years old?!? I thought it was relatively new like maybe 10 years old
  
  the package manager was first released in 2003, so nearly 21!
- The problem is that it's all spread out, they do actually have really good documentation for the language, it's just not easy to find. AND SPREAD OUT!
Or, they could learn Ansible and get 80% of the way, and be able to reproduce the result on more than one OS. 🥹
- Nix is not something exclusive to NixOS, and people are already using it to make reproducible configs that work on more than one OS.
  
  I'm even using Ansible in what I'm currently building with Nix, because it does one thing well that I need to do: distribute files and run commands on a lot of hosts at once.
  
  In my head they're different use cases. Nix is amazing for a living build. Ansible is more pigeon-holed to production systems where you don't want (or need) that history baked into every system
- That is, until a new Ansible version breaks playbooks again, or an OS is updated in a way that messes with you playbooks, or a package is removed from the playbook but not the installed system...
  
  Ansible is good for ephemeral containers or VMs, but any more permanent system will eventually deviate from the set configuration.
- Getting only 80% of the way there is why it never worked before for the whole system
  
  Where's Ansible OS?
Meanwhile me using Fedora with pretty much everything setup the way I want it out of the box:
- Blasphemy! How dare you not tweak your install!
  
  Reminds me of the meme I made for another thread:
  
  (That's accurate to my setup, BTW.)
- I use Mint, BTW.
- Basically why I switched from Arch to Endeavour
Wow, you have sold me on installing Nix next. I'm a programmer and this sounds dreamy!
- On most systems, you can install the Nix package manager and try it out before taking the leap :)
- nix develop is going to change your workflow. Don't fear the flake my friend :)
Stop threatening me with a good time!
I am a Gentoo user and most of that is already a reality on Gentoo systems. Get the stage3 tarball set up, slap your /etc/portage/make.conf and /var/lib/portage/world files in there and build.

Obviously, depending on whether it should be a blank system with the same apps installed or a clone of a previous system, configuration in /etc and one's home directory may need to be copied, too.

94 comments