GHCup discontinued (or why you should use Nix)

https://hasufell.github.io/posts/2025-04-01-use-nix.html

60 Likes

Good that we proud users of Nix, who have waded through the swamp of Nix tutorials and manuals, have perfected our Flakes, shells 'n derivations, and have learned to live with a determinant (or, determinate (?)) yet ingenious community are above such mundane announcements :smile: and would never exchange our beefed-up configurations for banal, regular configuration files…

6 Likes

This is great news this April! It is gratifying to see how progress is being made in simplifying the Haskell ecosystem.

Out of curiosity, are there any plans to discontinue Cabal and Stack as well and have Nix be entirely responsible for builds? It would also be nice to have the primary source of all Haskell packages become nixpkgs, and have Hackage redirect appropriately to nixpkgs. I would be a fool not to jump on the bandwagon.

20 Likes

Grossly off-topic (or is it?) but any chance GHC can be buildable from MicroHS or Hugs to complete the cycle? :smiling_imp:

Wow, I almost thought this to be an April fool’s joke!

1 Like

Meaning ? Are we really shutting it down ? I thought it was a joke. At this point now, I am a bit worried.

1 Like

Here’s an example of a nix flake:
(…)
I’m sure you’ll get it after going through the documentation above.

This is 100% a joke

1 Like

I love it! Line 15 of the example flake:

outputs = inputs:

Truly functional style.

4 Likes

Heh, maybe it could do with an explicit “this is a joke” at the top, now we’re past huntigowk day

1 Like

For what it is worth, I have just now edited my own response to highlight the two important keywords.

I love good jokes! :smiley:

Reading this on April 3rd and that title really scared me :sweat_smile:

The example nix flake seemed pretty basic to me. Perhaps showing something more complex would sell people on the power and ease of configurability of nix?

6 Likes