The year is 2040.
In Nixpkgs, all calls to mkDerivation have been replaced with mkAIDerivation.
Reproducibility is lost.
There is no hope for humankind.
https://t.co/boqiQAuvDS
Join us in Chicago for an evening of functional programming discussions and networking! Enjoy beer, pizza, and lightning talks while connecting with fellow enthusiasts.
Jan 16th, 2025 @ 6:00 PM / 325 W. Huron
Hosted by Bitnomial, a leader in US digital asset futures
@angerman Oh... that's certainly not the capitalization I was thinking of when I came up with the name 🤦 I mean, the name is pretty on-the-nose as-is, I didn't think it could be taken any worse 🤦
I wrote a little tool in #haskell that takes an input shell script, and turns it into a series of shell scripts that only consist of shebang lines:
https://t.co/vJ0CJZfEhK
Sometimes in older GHCs in #Haskell you want an easy way to write multi-line strings, without having to manually concatenate, or pull in a QuasiQuoter. Here's a method you probably shouldn't use:
I put together an example repo of how to build a fully statically-linked x86-64 Linux #Haskell binary using #Nix. Everything is documented, so you should hopefully be able to use this to get started with static linking:
https://t.co/FJl5T28drZ
@kerckhove_ts I believe @angerman was also saying in a Nixpkgs issue that at least ghc-9.8+ (and possibly also ghc-9.6?) is able to produce statically-linked binaries in haskell.nix, so that would be another option.
@kerckhove_ts Ah yeah, that makes sense. I wasn't trying to say that your approach is invalid, its just not the fully general approach of using pkgsStatic, or going with a mixed package set like static-haskell-nix.
@kerckhove_ts Also, if you're distributing the static binary anywhere, it is possible you're pulling in gmp? Maybe that's not alright? I couldn't see if you were using the native-bignum GHC backend anywhere.
@kerckhove_ts This mixed dynamic/static approach is also what static-haskell-nix used to do (and possible still does?). But it is different from just using pkgsStatic, since you end up having to do a lot more overriding of various dependencies if you end up needing more than just zlib.
I recently released a new CLI tool `cloudy`. It makes it easy to spin up temporary compute instances on various cloud providers.
I'm trying to make it feel similar to `docker run` or `vagrant`, but for running one-off applications in the cloud:
https://t.co/TmVGodrOKJ
I recently released a new CLI tool `cloudy`. It makes it easy to spin up temporary compute instances on various cloud providers.
I'm trying to make it feel similar to `docker run` or `vagrant`, but for running one-off applications in the cloud:
https://t.co/TmVGodrOKJ
I wrote a blog post about FODONUTs: fixed-output derivations for operating network-utilizing tests in #Nix. Helpful if you want to run internet-accessing tests in a Nix derivation, and you don't want to worry about constantly updating a hash for a FOD.
https://t.co/iLPuti2tYd
I still think about this tweet quite often.
On one hand, it paints #Nix in too good of a light. It can be pretty difficult to get some pieces of software building with Nix. Especially for beginners.
On the other hand, Nix does feel like a super power once you get used to it.
I'm actively trying to work through my Nix God complex. It's been so long that when I see non-Nix users complain about issues getting software to run, I'm truly confused. It's like someone looking at a river lamenting about having to ford it while I'm riding a bicycle on a bridge