14 Oct 2024 |
maralorn | * I mean, there is not really a basis to argue teleologically here. 😄 I think the more relevant question is what it is good at. But our priorities are 1) building Haskell programs for nixos users 2) providing Haskell dev environments via Nix.
My stance is generally that I would always deploy everything with Nix and I usually only test what I deploy, which implies testing also only happens with Nix.
But if you develop a library for hackage then it makes sense to test it how users will use it, which is probably not with Nix. | 16:59:35 |
hellwolf | Hehe. That actually makes sense, if I develop in house a Haskell based service, I'd totally use nixpkgs's Haskell packages. That answers my question actually. | 17:00:55 |
maralorn | I think one big selling point for CI is obviously to use cache.nixos.org. But that only works well for the default ghc version. | 17:00:59 |
hellwolf | For developing a library, indeed, it's probably asking for troubles since most don't use nix | 17:01:22 |
hellwolf | * For developing a library that's published to hackage, indeed, it's probably asking for troubles since most don't use nix | 17:01:55 |
maralorn | But really my short answer is: The primary reason to use Haskell+Nix is if you want deploy or develop on nixos. | 17:03:44 |
maralorn | I write a lot of bash scripts in Haskell for my nixos systems, with template haskell to ensure presence of called programs at compile time. 😄 | 17:04:46 |
hellwolf | oh, how does that look like? | 17:05:43 |
hellwolf | fwiw, I am wrapping up the THSH project which mixes Haskell and shells, some tool I always wanted to have. | 17:06:15 |
emily | maralorn: just a ping to check about progress on release note/announcement/survey stuff? | 17:30:39 |
maralorn | emily: Well, frankly the policy is stuck in internal discussion. | 17:55:59 |
emily | I thought the survey/request for feedback was to get data to help inform the policy 😅 | 17:57:34 |
emily | but ok, good to know | 17:57:36 |
emily | dropping or relaxing the LLVM deps for old GHCs is still a possible backstop even if they need to stay for now I guess? since from previous discussions it seems like the conservative bounds were not really related to code changes given the use of textual IR etc. | 18:04:33 |
maralorn | Well, the problem is that I wrote that policy in an attempt to shortcut the survey thing, in the hope that it would reach the same people. | 18:06:47 |
maralorn | But apparently we need a survey because it is too hard to agree on a policy without the data. | 18:07:06 |
maralorn | The main thing holding me from writing a survey is actually knowing which tool to use. | 18:07:47 |
maralorn | * The main thing holding me from writing a survey is actually knowing which tool/server to use. | 18:08:01 |
maralorn | In reply to @emilazy:matrix.org dropping or relaxing the LLVM deps for old GHCs is still a possible backstop even if they need to stay for now I guess? since from previous discussions it seems like the conservative bounds were not really related to code changes given the use of textual IR etc. I will refrain from further commenting on llvm related details because I am setting the discussion up for failure with my cluelessness. | 18:08:58 |
emily | I hear CIVS has only had one data loss incident since 2006 😅 | 18:09:49 |
emily | there's always something boring like Google Forms, though I imagine some people may object to that | 18:10:40 |
alexfmpe | In reply to @maralorn:maralorn.de I write a lot of bash scripts in Haskell for my nixos systems, with template haskell to ensure presence of called programs at compile time. 😄 Do you use https://hackage.haskell.org/package/which or something else? | 18:39:47 |
hellwolf | huh, and is ghc922 going to be 9.22 or 9.2.2 :) | 19:07:13 |
hellwolf | * huh, and is ghc924 going to be 9.24 or 9.2.4 :) | 19:07:28 |
maralorn | In reply to @alexfmpe:matrix.org Do you use https://hackage.haskell.org/package/which or something else? I recently switched to that yeah. In most places I use shh. | 19:08:24 |
maralorn | In reply to @hellwolf:matrix.org huh, and is ghc924 going to be 9.24 or 9.2.4 :) Grave Mistakes have been made. | 19:08:55 |
maralorn | In reply to @hellwolf:matrix.org huh, and is ghc924 going to be 9.24 or 9.2.4 :) * | 19:09:05 |
alexfmpe | I blame cabal macros | 19:10:33 |
alexfmpe | turns out 920 is 9.20, not 9.2.0 | 19:11:06 |
alexfmpe | if we ever get to 9.99, there will be hell to pay | 19:11:53 |