Live data from Hacker News

NixOS 26.05

nixos.org

81–90 of 106 posts

Re: NixOS 26.05

#81

> 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.

1500 commits seems kind of low? that's an average of one commit every two ish days

Re: NixOS 26.05

#82
post #22

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.

On macOS I settled for Nix + HomeManager rather than going fully nix-darwin

I tried nix-darwin (with plenty of LLM assistance) but struggled to get it to work in the way I wanted. I couldn’t get it to manage my dock, and it was fiddly bootstrapping my two main users from an admin user.

Re: NixOS 26.05

#83
I've run nixos for ten years now without ever having to reinstall... Just continuous updates and my dev environments are nice and segregated and one command line away from being identical on all my computers.

Nirvana

Re: NixOS 26.05

#84

Earlier quoted context omitted.

I love the slightly weird learning curve on NixOS where initially it seems incredibly complex writing this weird functional programming language for every change you want to apply to your system, then over time it clicks and you end up in a place where any operating system that doesn't define everything in a weird functional programming language seems incredibly complex. I read blog posts about doing things on other…

When I started self hosting last year it seemed insane that hosting a service required separately managing the imperative firewall state, vpn, container runner, systemd, and reverse proxy. Nixos is nice because it just works. When I do a rebuild switch it will take down my affected services gracefully, apply the updates, update my firewall, and start the container all automatically and declaratively. Plus the owning…

I've find my email on simple-nixos-mailserver for almost a half decade... So easy, less than 25 lines of code and a command line to update every few months.

Re: NixOS 26.05

#85

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/depl…

I self host my own stuff in a data center with a bunch of computers. I have a virtualized setup all in nix defining nixos setups for all hosts. Switches are virtualized using open v switch and everything is made so that the nix expression generates a launch script to test the whole set up.

Before I deploy I know that all hosts will be able to boot properly from tftp and then communicate and launch kubernetes.

I never ssh into any of my nodes at this point. Amazing. It just works. Once in a while I'll restart them just for funsies.

Re: NixOS 26.05

#86

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?

I do use nixos on my (limited) servers. I self host everything. Ama.

Re: NixOS 26.05

#87

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

15 hours later and noone taking that ragebait, seems healthier than most communities to me as a total outsider.

Re: NixOS 26.05

#88

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.

> It seems anecdotally like LLMs have really given it a boost recently

I have been using Nixos for the past 5 years. And I really use the power of nix/nixos since Codex is doing good code with it.

Setup easily systemd-user unit with podman rootless, backup, writing script during build...

Re: NixOS 26.05

#89
post #62

Earlier quoted context omitted.

You could take this one step further using Syncthing to sync important data between the workstation and laptop. That's how my devices are configured, and it's amazing - if I need to travel for work, I just pick up my laptop and go. NixOS makes sure the system itself is identical (apps, most of the code configs, etc), then any app-spcific config is handled by Syncthing. It was really magical the first few times I used…

Really solid advice. Going to have to try that remote rebuild, because right now my 10yo T420 takes around an hour to rebuild gitbutler-cli (not yet packaged in NixOS), so that'd be real nice. I know syncthing has a solid reputation, but I'm a bit reluctant to try it on my home directory (it's super mission critical). Does that interact well with home-manager+SOPS? Mostly, when I'm away from my workstation, I just co…

As a small note against Syncthing, despite how much praise it gets, it's conflict resolution sucks. Enough so that it is easier to nuke it and set it up again instead. If you never have conflicts, it works fine though, but I find that rather unrealistic.

Re: NixOS 26.05

#90
post #85

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/depl…

I self host my own stuff in a data center with a bunch of computers. I have a virtualized setup all in nix defining nixos setups for all hosts. Switches are virtualized using open v switch and everything is made so that the nix expression generates a launch script to test the whole set up. Before I deploy I know that all hosts will be able to boot properly from tftp and then communicate and launch kubernetes. I never…

That sounds fascinating. Do you have public facing configuration you would be willing to share? :)
Post reply on HN