FRESH

Hacker News

Home

NixOS 26.05

78 points by lostmsu

by linsomniac

4 subcomments

I switched my workstation over to NixOS ~6 weeks ago and it's been really good, I'm a total convert. The thing that really got me over the hump was entirely configuring it using Claude Code.
One unexpected benefit is that both my workstation and my backup laptop have the same setup, so I can run updates on the scratch box before doing my workstation. I decided to run the "latest" rather than 25.11 release, so it's nice to test before I apply (I hit a GDM issue a few weeks ago that left me at a black screen; but not a huge deal, just select the "previous" option in the grub screen).
I've got everything to parity with what I had on my previous Ubuntu workstation. I had anticipated issues with some software that isn't packaged (but NixOS packages a LOT), but that wasn't an issue. Claude was able to do all those things no problem.
The biggest tricky bit was with my vim setup; I've been using AstroVIM and trying to get away from managing my own vim setup. You can't, AFAICT, just apply astrovim in NixOS. So I described the vim setup I wanted to Claude Code, and I now have a ~700 line config that implements everything I wanted: LSP, TreeSitter, a small variety of other things. Unlike Astro/Lunar, where tweaks you want to make are buried in some set of files in this whole giant distro, it is all encoded in this one "neovim.nix" file.
I also set up home-manager and SOPS and so far that has been working just great! I now have home directory settings that are replicated across 2 machines.
I'm still really only using it on one machine, so we'll see how it gets more complicated if I start running it on some servers.

by tomalaci

5 subcomments

I had quite a rollercoaster going from Windows 10 to Arch to Windows and then settling on NixOS. Main reason being able to do clean package/program setup and centralize, version-control my configuration.
My main issue with Arch was that after installing and trying stuff it left OS dirty even after package removal. This might be because I had some things built and installed through AUR (e.g. latest mpv releases that sometimes broke). Eventually I went back to latest Windows 11 build wanting easy no-bs setup.
Of course, then MS decides to shove down half baked AI integration that somehow used half my RAM and randomly slowed my CPU. I am guessing it was busy indexing, searching or security-scanning something.
Got increasingly annoyed by Microslop and tried NixOS. Bumpy ride initially but after committing for few weeks I am finally settling on it be the last OS I need.

by mplanchard

1 subcomments

I love seeing all these posts from NixOS newcomers! It seems anecdotally like LLMs have really given it a boost recently, I guess by reducing the intimidation factor of the language and the unfamiliarity? Of all the positive and negative outcomes I have imagined from LLMs, NixOS becoming popular was not one of them, but I'll take it.

by AyanamiKaine

2 subcomments

I really love NixOS for my two devices, one surface laptop (lol), and my nvidia pc. It reduced my headaches with drivers so much.
Before updating my nvidia driver or something related to my surface I was scared to break something. With NixOS I can just go back to the old working config.
Another underappreciated feature about NixOS is, that you can create a VM out of a NixOS config to locally test a server update/deployment.

by chem83

2 subcomments

NixOS has been my daily driver since 2022/2023 and I have greatly improved the management of my 2 computers and few VMs since. Because of LLMs, I now understand the language much better, but even if I didn't want to write Nix directly, describing the config to AI usually produces good results.
The two main sticking points IMO are still:
- Development environments are still a pain. devenv.sh is great for web and backend, but not perfect for dependency (package) management and more complicated environments like mobile or embedded
- nixpkgs monorepo doesn't update fast enough IMO. As a consequence, I see a number of flake repositories popping up to more easily package and distribute software not yet on nixpkgs or that don't update often enough (https://github.com/numtide/llm-agents.nix is a good example). This is perhaps by design, but it takes some digging to find the reliable and trustworthy flake repos. I'm increasingly concerned with AUR-like trust issues

by rekoros

1 subcomments

After using NixOS for a bit and eventually learning to rely on it, life without it seems inconceivably complex

by evilmonkey19

0 subcomment

I decided to move to NixOS a few months ago. In terms of OS, it was one of the best decisions I've made so far. It's awesome to have the rollback experience, upgrade whenever you want and also being able to experiment without being afraid of breaking already working stuff.
Another great benefit, is that AI can read my whole OS (good and bad at the same time, I know). This makes the AI way more accurate on giving you a good solution instead of having to scan all of your OS and dig into /etc.
Personally, I really like NixOS. It's hard but definetely worth the try. Probably not for everyone, but worth it if you're a computer scientist or need to maintain hundreds of computers.

by hombre_fatal

0 subcomment

One of the best things about Nix, aside from LLMs being able to manage your config, is having a monorepo that contains the config across all machines (shared and machine-unique), like hosts/{nas,macbook}/{configuration.nix,home.nix,modules/}.
Now I have the same setup across my macbook, desktop, and NixOS servers.

by unforgivenpasta

3 subcomments

> Deprecation of x86_64-darwin
Understandable with Apple dropping official support but kind of sad as they were selling Intel powered Macs until as recently as 2023 and with Tahoe still continuing to receive security updates until 2028.
How is NixOS on Intel Macs currently? Hopefully Linux can still breathe life into these computers in 10 years time.

by LelouBil

1 subcomments

I post this on every post about Nix I encounter, but I sincerely hope that it gets static electricity typing one day. I have yet to try typenix (a fork of the typescript compiler applying the typescript type system to nix)
https://github.com/ryanrasti/typenix

by markatkinson

1 subcomments

I'd love to try NixOS but I still have PTSD from trying to run/use Nix on MacOS, across two separate profiles on the same physical device too.

by LelouBil

3 subcomments

I would love a Bazzite-style nixos distribution. Like batteries-included for gaming.
Is this kind of thing common in the NixOS space ? Like configs you can import that manage 99% of the os for you ?

by tiffanyh

1 subcomments

Why don’t more people use NixOS on servers?
Is it because of no LTS?
And is having a LTS somewhat the antithesis of what NixOS represents?

by yomismoaqui

0 subcomment

Let's talk about the important things... how is the drama currently on the Nix community?

by iLoveOncall

1 subcomments

> The 26.05 release was made possible due to the efforts of 2842 contributors, who authored 59703 commits since the previous release.
Maybe they should think about increasing their release cycle, that sounds completely unmanageable.
After 10 years in my company I have around 1,500 commits in total, it would take me 390 years to author 60K.

by shevy-java

0 subcomment

NixOS is a pretty cool idea in theory. In actual practice I found it too complicated to manage. Immutability is kind of cool too, but it creates an obstacle to solving even trivial task in my daily life using Linux. And I don't want to really use such a domain specific language like Nix, for things that really should not need a programming language per se. For instance, I like ruby, but I don't want configuration stuff to be kept in .rb files; that's also one gripe I have with homebrew, even if the idea to HAVE a recipe in a .rb file, is not bad per se. I am just too used to e. g. yaml files or any other simple format for literally everything. All my RC files and ENV data and aliases for shells is kept in .yml files; ruby then just autogenerates any target format I need for different shells/terminals, and so on and so forth. Also, NixOS is not very flexible. I prefer e. g. /Programs/Ruby/4.0.5/ rather than a hashed directory name. It's not a bad idea here either, and there would be many workarounds for that (see GoboHide on GoboLinux, for instance), but at the end of the day it felt as if I was fighting NixOS too much than getting real work done. There is something to be said about simplicity at all times, even if the ideas in NixOS are still great. For instance, we could guarantee that every snapshot would work, so people having the same hardware could just re-use configuration and have things work, without needing to know how to change the system precisely. That would not be needed because NixOS could make a guarantee about ALL possible stable snapshots in time. I don't think NixOS goes that far, so far, but it would be a very logical extension. Same with immutable packages / reproducible packages:
https://wiki.debian.org/ReproducibleBuilds
We could make such a guarantee if we extend NixOS. But until all of that happens, I stick with simplicity and flexibility. It just kind of works better, even if it is nowhere near as sophisticated as NixOS.