A lot of the problems in the #Nix/#NixOS community are fundamental, built into its culture, from toxic development culture to the two repeated military-industrial sponsorship situations.
The culture of undermining community authority, of acceptability of conflict of interest, of tolerating abusive behaviour, goes up to the very top of the organization, with Eelco Dolstra.
You can read an extensive summary of the issues and sign an open letter to the Foundation here:
Instead of one Nix talk, we will do a round of short Nix lightning talks and a Nix Q&A session where you can raise questions and problems that you encountered while using Nix or NixOS, or that so far prevent you from using them. If you want to present a lightning talk (5-10min), feel free to send us a message.
anyone here that can help me with nix on macos with limited sudo access and self-signed certs being forced into my connection to nixos.org by corporate?
I, again, am thinking about combining Silverblue as my base system with a more complex Nix setup to replace toolbox (which is effectively a separate whole Linux to maintain or throw away regularly, or build a CI for to create new images, etc. -- nah).
Now, Nix works fine, but it needs to store things under /nix because most binaries are prefix dependent and not portable in their location. But what if I download the nix store to $HOME/.nix instead and then launch a light-weight throw-away container/namespace that simply maps $HOME/.nix to /nix but keeps everything else identical?
Would that work? Did someone already build that stuff?
Helsinki Haskell Users Group's first book club had its conclusion meeting today with Sockets and Pipes coming to its very end. It has been a ride, one with plenty of scheduling difficulties, but I think we only fell like a month and a half from the original planned schedule and actually had a member retention rate of 100% (of members who were there in the beginning, sadly we could not quite make it 133%)!
To talk a bit about the book as a whole, I do feel like I understand Monad Transformers a lot better now though I'll still need to reread the sections introducing them I am sure. ReaderT especially was something I could see was colossally handy, but given it was in the second to last chapter we were already quite deep with trying to understand everything else so the true utility of it remains somewhat hazy despite the quality of the chapter itself which felt higher than those surrounding it. The habit of reading RFCs and attempting to match the spec in the types one writes is also one I should include in my general workflow, though that is probably a no-brainer for most. It just wasn't a thing in my previous work, so bear with me while I call it a novel concept!
I'm still working on my personal project, but getting nix-build working seems difficult. I'll just have to bring it up in the next main group Office Hours meetup I suppose, lest I never get this show on the road!
Eheh, just noticed that the installer for nix-installer from install.determinate.systems takes a while to be updated after a new github release.
The releases says it was done 5 hours ago for 0.18 version but the script still fetches 0.17.1.
Just caught this because I couldn't find a way to update the old version I had around without uninstalling and installing it again. Been delaying it for a while 😮💨.
Yesterday session to bring quicklisp/ultralisp/git together with #nix for #commonlisp development and deployments with NixOS was very fruitful.
One of the main problems with #sbcl deployments is that you need a matching SBCL version and glib version for them to work. Nix can be a solution to that but it has a very sad story for common lisp dependency management.
Maybe something will come out of it. Currently I have an autogenerated flake with all of ultralisp and a lispDerivation function that creates a derivation and pre-compiles the fasls given the lisp implementation you wanna use.
Pour une formation que je vais faire au boulot, je viens de créer un #nix#flake qui te fournit un #neovim configuré au petits ognons pour les besoins de la formation. C'est vraiment un outil qui envoie. nix run github:owner/repo et zou tu as ton éditeur sans interférer avec ta potentielle conf locale.
Avec mon #cachix perso pour récupérer une version précompilée pour les OS utilisés, c'est du pur bonheur.
@itsfoss I’ve been using Arch for quite some time, mainly due to how customizable it is and because of the AUR.
But recently, @nixos_org is growing on me more and more, and I even use #nix more and more outside #nixos too. My next desktop will run exclusively on NixOS, one of my laptops already does!
What's the 2024 state of the art for local macOS+arm64 development nonsense?
Without spending TOO much time combing my (halfhearted because I've been developing via headless Linux since 2020 & it's actually very nice) notes, the last I recall hearing is:
Homebrew still "is what it is” & its entire world has since been updated for arm64?
Actual-Docker works now, but still via a (Virtualization.framework? emulating Intel??) Linux VM?
#Python env management. I’m told PDM is current state-of-the-art, Hatch also good, uv if you're not allergic to VC money, Poetry if you can stomach its bug surface, or the evergreen "just use pip-tools”.
Or use a polyglot tool like mise (fka rtx) or asdf (or haha-only-joking-unless, Determinate System's #Nix installer + flakes).
Also curious about #Rust on macOS arm64, even though that's getting ahead of myself.
Could #Guix or #Nix be modified to not require ever greater amounts of storage? Like, maybe just using shallow clones, or Merkle logs instead of linear git histories, or something?
The Nix project has had quite a bit of bad publicity in the last month for having Anduril sponsor NixCon NA.
I am very happy to see that —after admittedly way too much effort— we now finally have a sponsorship policy to prevent this from happening in the future. A big Thank You to all who contributed and pushed for this!
If you turned your back on Nix due to this, please consider accepting the apology from the Foundation Board.
Keep exploring the problems of guix pull, channels and checkouts, but I wouldn't say that it's the most exciting thing to do, especially annoying part is a huge feedback loop: almost an hour for initial guix pull on debian system to finish.
After a year and a half of using #FreeBSD daily, it will be impossible to go back to using #Linux unless it's minimally based on BSDs (like #Gentoo, #Arch, #NIX).
If you wanna try it (and have Flakes enabled), you can simply run the following command:
nix run github:blinry/nixpkgs/tic-80#tic-80
Let me know if something breaks! :D Would be happy about feedback or code review in the PR! Haven't tried or enabled it on MacOS, if you wanted to try that, that'd also be wonderful! #nix#nixos#nixpkgs