I don't want to bore my HackerNews fellows, so I'm sorry in advance, but wasn't there a lot of drama in the Nix community? I've read some time ago that a private company was buying parts of its infrastructure (or something like that) and forcing some changes upstream and people were not happy about it.

I'm interested in NixOS, but I'm at an age where I just want things to stay stable and change only when they really have to. I already have a lot of big mandatory changes from life itself, I don't need more :)

I'm writing this in good faith. I'm genuinely curious and interested in trying it again.

▲

georgyo 7 hours ago | parent | next [-]

There is drama, yes. But it is getting a lot better recently.

It's a thriving open source ecosystem. There are forks, there are differing opinions, and in-depth discussions.

But, universally, everyone agrees that nixpkgs, independent from any implementation, is the real value of nix.

That said, things change. OpenSSL 4, glibc 2.44, gcc 16, etc which then requires a bit of tweaking every now and then.

▲

eddieroger 7 hours ago | parent [-]

Have flakes stabilized? I thought those were one of the points of contention, while also being the kind of thing that I was the most interested in as a way of hopefully managing a small fleet of VMs. I had trouble getting the idea to stick because I really believed in the single-config ideal reality, but couldn't bend my config far enough in.

	▲	georgyo 7 hours ago \| parent \| next [-]
		Flakes are neither stable or unstable... They are defacto stable in that everyone is using them and the interface is not really going to change at this point. But they are still marked as an experimental feature. To get them out of experimental, the requirements are normalizing the CLI. Currently some options are global and some are local to a command. The plan as I understand it is to make them all local. This would make it clear which options any particular command actually take instead of guess work. They are not going to break usage, but make the usage more clear. And fetchTree needs to be stabilized. A big criticism of flakes is that they had a nonstandard method of fetching data and repos. fetchTree is a new nix built-in that behaves the same way. This makes flakes a lot less special. So, nix flakes are a stable experimental feature, slowly getting to the state that it won't be experimental any more.
	▲	wojtek1942 6 hours ago \| parent \| prev [-]
		"Experimental does not mean unstable" (2023) https://determinate.systems/blog/experimental-does-not-mean-... I know not everyone is a fan of DS, but this post has a nice, concise explanation of how to think about the state of flakes.

▲

iamnothere 7 hours ago | parent | prev | next [-]

There was, it’s mostly dried up now that a bunch of the loudest voices split off to Lix. The Nix community weathered it decently despite some people’s best efforts.

▲

usumgallu 8 hours ago | parent | prev [-]

[dead]