❄️ Guix System First Impressions as a Nix User // https://nemin.hu
The first data science book that has a chapter on monads https://reproducible-data-science.dev/
Learn how to build robust #DataScience pipelines with #RStats, #Python , #Julia and #Nix !
The first data science book that has a chapter on monads https://reproducible-data-science.dev/
Learn how to build robust #DataScience pipelines with #RStats, #Python , #Julia and #Nix !
Why you do like guix vs nix or vis versa?
Please only answer if you've tried both guix and nix.
I've been thinking about getting into one or the other, but I can't decide, and I don't have all the time in the world, so whatever I choose, I'll probably be stuck with for like many months until I can switch if I don't like it.
Interested in #declarative computing, #linux or #reproducible software? #Guix is going to be at #FOSDEM for lots of goodness on #guile #scheme and the #nix approach to packaging #FreeSoftware - check out the talks various people are giving:
https://guix.gnu.org/blog/2026/meet-guix-at-fosdem-2026/
As usual the Declarative and Minimalist computing track will have lots of interesting #lisp #spritely and #nrepl talks!
Why you do like guix vs nix or vis versa?
Please only answer if you've tried both guix and nix.
I've been thinking about getting into one or the other, but I can't decide, and I don't have all the time in the world, so whatever I choose, I'll probably be stuck with for like many months until I can switch if I don't like it.
Interested in #declarative computing, #linux or #reproducible software? #Guix is going to be at #FOSDEM for lots of goodness on #guile #scheme and the #nix approach to packaging #FreeSoftware - check out the talks various people are giving:
https://guix.gnu.org/blog/2026/meet-guix-at-fosdem-2026/
As usual the Declarative and Minimalist computing track will have lots of interesting #lisp #spritely and #nrepl talks!
has anyone done the #categoryTheory of #Nix or #Guix?
I was shocked to not find a model in Dolstra's dissertation.
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. 