Re: State of Haskell 2025
Because I haven't tried to upgrade: the risk of breaking something exceeds any 'benefit' from new 'features', none of which do I want to use.
If you did not try to upgrade, how did you find out that upgrading would break your code? Indeed, only offering "yes" and "no" as options is not enough for this question. "Bottom" would be the appropriate answer in your case, and I'd have chosen that, too. Olaf
That's what the word “risk” means. It's when you haven't found out.
On 11 Dec 2025, at 22:04, Olaf Klinke via Haskell-Cafe
wrote: Because I haven't tried to upgrade: the risk of breaking something exceeds any 'benefit' from new 'features', none of which do I want to use.
If you did not try to upgrade, how did you find out that upgrading would break your code?
Indeed, only offering "yes" and "no" as options is not enough for this question. "Bottom" would be the appropriate answer in your case, and I'd have chosen that, too.
Olaf _______________________________________________ Haskell-Cafe mailing list -- haskell-cafe@haskell.org To (un)subscribe, modify options or view archives go to: Only members subscribed via the mailman list are allowed to post.
What @MigMit said. Actually, over the past year rather a lot of upgrades in Haskell-land have broken stuff/made it more awkward to use -- including the mailing list losing my handle (AntC) and arbitrarily breaking threads in pieces (like this one) and timeouts (just now). So the likelihood of a GHC upgrade breaking my code is low; but the benefit for me is zero. I'll leave it a few years for others to iron out the wrinkles. I do monitor the release notes; so I can see the long-running breakages that I'm currently having to work round aren't getting fixed either. AntC
participants (3)
-
anthony.d.clayden@gmail.com -
MigMit -
Olaf Klinke