Seems Determinate Systems are the true murderers of the once open community that was #nix. Since i have last looked they have:
1. Effectively Hard forked Nix into their own Determinate Nix, with a pinky promise to upstream everything, which does not seem to have been done at the scale originally promised. https://determinate.systems/blog/announcing-determinate-nix/
2. The nix installer has been reworked to not support the original nix project, only this non-standard Determinate Nix version for "their consumers".
3. Blaming upstream for not doing it their way with flakes. Effectively acting as flakes will one day become only supported by their Determinate Nix fork in the future. https://www.reddit.com/r/NixOS/comments/1j4fhgf/determinate_nix_30_featuring_stable_flakes/mg8e5w7/
4. Forked nixpkgs and (mis)used the MIT license to create a proprietary fork with SBOMs and CVE monitoring. Notably maintaining security patches for packages outside of nixpkgs, effecitively commercializing the open project nixpkgs for their profit. https://determinate.systems/secure-packages/
Ah well, I wont be getting back into Nix anytime soon. Maybe the community is largely ignoring DetSys, but given that still core people of the nix community work there, the actions of this one company destroys the trust in nix as a whole.
Learning that #mise, a meta packaging tool, which I personally use, package, and contribute to through a plugin, took a major turn 6 months ago towards largely vibe coding all future development by the lead developer. I'm not really sure what to do with this information, at least it is somewhat clearly labelled?
So I'm on the market to look for another packaging tool. Wondering if #nix ever got their drama resolved since i left. I know nixpkgs does have a vague "no llm slop" rule, but nothing explicitly against use of AI completely.
Maybe I should try to pick up another tool for packaging more seriously, like RPMs and Open Build Service, and contribute more upstream to openSUSE. 
Seems Determinate Systems are the true murderers of the once open community that was #nix. Since i have last looked they have:
1. Effectively Hard forked Nix into their own Determinate Nix, with a pinky promise to upstream everything, which does not seem to have been done at the scale originally promised. https://determinate.systems/blog/announcing-determinate-nix/
2. The nix installer has been reworked to not support the original nix project, only this non-standard Determinate Nix version for "their consumers".
3. Blaming upstream for not doing it their way with flakes. Effectively acting as flakes will one day become only supported by their Determinate Nix fork in the future. https://www.reddit.com/r/NixOS/comments/1j4fhgf/determinate_nix_30_featuring_stable_flakes/mg8e5w7/
4. Forked nixpkgs and (mis)used the MIT license to create a proprietary fork with SBOMs and CVE monitoring. Notably maintaining security patches for packages outside of nixpkgs, effecitively commercializing the open project nixpkgs for their profit. https://determinate.systems/secure-packages/
Ah well, I wont be getting back into Nix anytime soon. Maybe the community is largely ignoring DetSys, but given that still core people of the nix community work there, the actions of this one company destroys the trust in nix as a whole.
Learning that #mise, a meta packaging tool, which I personally use, package, and contribute to through a plugin, took a major turn 6 months ago towards largely vibe coding all future development by the lead developer. I'm not really sure what to do with this information, at least it is somewhat clearly labelled?
So I'm on the market to look for another packaging tool. Wondering if #nix ever got their drama resolved since i left. I know nixpkgs does have a vague "no llm slop" rule, but nothing explicitly against use of AI completely.
Maybe I should try to pick up another tool for packaging more seriously, like RPMs and Open Build Service, and contribute more upstream to openSUSE. 
Looking back on it now, if I could do it all over again, I would've just started with NixOS.
I see people recommending NOT to make NixOS your first Linux distro, and I can't see where that advice is even coming from, frankly.
I've learned so much more about the inner workings of Linux systems, by using NixOS, than by any other means. I see no reason why that would be any less true if I'd never touched anything else.
I look at it like this: every other distribution, however ironically, hides the system by exposing it to the user directly; NixOS, however ironically, exposes the entirety of the system to the user by doing so at a high level of abstraction. Everything that happens on the system configured at the same level of abstraction; that is, there is no package manager properly: there is instead, if we're calling it what it actually is, a build system (that is for some reason, inexplicably) marketed as one.
It completely changes the entire concept of what having an operating system installed on your computer even means.
I honestly believe I would have a better understanding than I do now, now, had I simply jumped straight from Windows to NixOS and never bothered with anything else at any point.
Looking back on it now, if I could do it all over again, I would've just started with NixOS.
I see people recommending NOT to make NixOS your first Linux distro, and I can't see where that advice is even coming from, frankly.
I've learned so much more about the inner workings of Linux systems, by using NixOS, than by any other means. I see no reason why that would be any less true if I'd never touched anything else.
I look at it like this: every other distribution, however ironically, hides the system by exposing it to the user directly; NixOS, however ironically, exposes the entirety of the system to the user by doing so at a high level of abstraction. Everything that happens on the system configured at the same level of abstraction; that is, there is no package manager properly: there is instead, if we're calling it what it actually is, a build system (that is for some reason, inexplicably) marketed as one.
It completely changes the entire concept of what having an operating system installed on your computer even means.
I honestly believe I would have a better understanding than I do now, now, had I simply jumped straight from Windows to NixOS and never bothered with anything else at any point.
Going immutable on macOS, using Nix-Darwin
https://carette.xyz/posts/going_immutable_macos/
#HackerNews #Going #immutable #on #macOS #Nix-Darwin #macOSDevelopment #ImmutableSystems #DevOps
@rl_dane I saw this just before sleep
I tried with #Fish
Fish store history as #YAML
I tweaked the command to make it barely works
Since it's YAML, it's store the timestamps
So, i tried to do an actual #year_in_review
3 hours later, here it is !
https://gitlab.com/pinage404/dotfiles/-/commit/5089def105806afe92684609a004081cf5aa136d
Here is mine :
1. #git :blobcatheart:
2. #lsd https://github.com/lsd-rs/lsd :blobcatrainbow:
3. #cat (which is actually an alias over #bat https://github.com/sharkdp/bat 🦇)
4. #rg #RipGrep https://github.com/BurntSushi/ripgrep 🪦
5. #Nix https://nixos.org :nixos:
After almost a year of full time using #nixos today was the day I realized, I don't need to `ssh` to the other computer, `git pull` and switch.
If `ssh` is there, #nix can connect to the other computer, build and deploy all from my main computer.
I was aware of nix's ability to connect and deploy to other computers, I don't know why it took me so long to realize how simple it is.
Merry Christmas 🎉
Here's the command I'm using `nh` instead of `nixos-rebuild`:
https://github.com/woile/nix-config/blob/main/justfile#L7-L10
Are you ready for the 2026 Nix/NixOS sprint season?
Ocean Sprint will happen in April on Lanzarote, registration is open until 20th January:
https://oceansprint.org/
A great opportunity to meet people from the community, hack and swim with great weather!
Already in February, the first Aurora Sprint will be happening in Reykjavik, Island:
https://aurorasprint.com/
The sprint focuses on Nix for embedded linux systems.
Are you ready for the 2026 Nix/NixOS sprint season?
Ocean Sprint will happen in April on Lanzarote, registration is open until 20th January:
https://oceansprint.org/
A great opportunity to meet people from the community, hack and swim with great weather!
Already in February, the first Aurora Sprint will be happening in Reykjavik, Island:
https://aurorasprint.com/
The sprint focuses on Nix for embedded linux systems.
TIL that in Nix, if you have a multi-line string of code, you can simply prefix it with a comment stating the name of the language and Tree-sitter will highlight it for you!
{
# The TOML string below will be highlighted!
programs.foo.extraConfig = /* toml */ ''
bar = "baz"
'';
}
Today I finally release #PKGMGR 1.0.0 🎉
A multi-distro workflow & package manager built on #Python + #Nix. It unifies repo management, builds & releases and now stabilizes and future-proofs @infinito development and deployment.
More: https://s.veen.world/pkgmgr
#Linux #DevTools #Nix #FOSS #Automation #MultiDistro #ArchLinux #Debian #Ubuntu #Fedora #CentOS #DevOps #CI #OpenSource #InfinitoNexus #NixOS #Arch #ArchLinux
It is a sad day, at the same time I look back and realize the journey was beautiful and taught me a lot.
I am no longer running a 100% #guix system. I got tired of things breaking, being removed without warning or explanation, undocumented things, cryptic error messages.
I am but one person and cannot afford to debug stuff everyday.
I therefore took the pragmatic choice of scripting some things on top of #fedora and spread the risk, with #guix #nix #flatpak and #dnf packages.
cc: @rafa
🎉 nix-dev-docs-l10n is published!
🚀 Preview:
https://projects.localizethedocs.org/nix-dev-docs-l10n
🌐 Crowdin:
https://localizethedocs.crowdin.com/nix-dev-docs-l10n
🐙 GitHub:
Today I finally release #PKGMGR 1.0.0 🎉
A multi-distro workflow & package manager built on #Python + #Nix. It unifies repo management, builds & releases and now stabilizes and future-proofs @infinito development and deployment.
More: https://s.veen.world/pkgmgr
#Linux #DevTools #Nix #FOSS #Automation #MultiDistro #ArchLinux #Debian #Ubuntu #Fedora #CentOS #DevOps #CI #OpenSource #InfinitoNexus #NixOS #Arch #ArchLinux
TIL that in Nix, if you have a multi-line string of code, you can simply prefix it with a comment stating the name of the language and Tree-sitter will highlight it for you!
{
# The TOML string below will be highlighted!
programs.foo.extraConfig = /* toml */ ''
bar = "baz"
'';
}
I published my first #Nix / #NixOS library!
Niccup: Hiccup-like HTML Generation in ~120 Lines of Pure Nix.
Transforms Nix expressions into HTML.
The website has some cool examples, I'm especially proud of the quine one that was slightly tricky to get right: https://embedding-shapes.github.io/niccup/examples/quine/
Website: https://embedding-shapes.github.io/niccup/
And a softer introduction blog post with motivation and more background: https://embedding-shapes.github.io/introducing-niccup/
Has anyone figured out how to run Home Manager on Fedora Silverblue yet? I've been unsuccessful so far and would appreciate some pointers.