| 10 Feb 2025 |
 alexfmpe | I know the folks working on js backend have been throwing google closure compiler at hello world and whatnot successfully, I just haven't tried any of that myself, was strictly in "build it in nixpkgs" mode | 22:24:14 |
| alexfmpe | so 3 is possibly fixed | 22:24:22 |
| alexfmpe | 1 is probably fixed? wasn't this caused by spawning node processes like there's no tomorrow? | 22:24:45 |
 maralorn | And this number 4 means, that the miso nixpkgs pin got too old and you somehow need a way out. Do I understand that correctly? | 22:24:47 |
| maralorn | Well, come to think of it. It’s actually probably only 4 years old. | 22:25:18 |
| alexfmpe | I see where I got confused. The commit adding the pin was ~2 years when I looked but the pinned commit is indeed from 2019 | 22:25:38 |
| alexfmpe | * I see where I got confused. The commit last touching the pin was ~2 years when I looked but the pinned commit is indeed from 2019 | 22:25:43 |
 @dmjio:matrix.org | Would love to see the new backend reach feature parity but I just feel like ghcjs users have to now become nix experts and/or compiler engineers, which some want to do I guess, others just wanna build web apps | 22:26:08 |
| maralorn | That’s actually a valuable data point. I keep telling my boss that at some point we won’t be able to sustain this … | 22:26:49 |
| alexfmpe | I'd think mainlining ghcjs makes it easier for users to consume with less hassle no? | 22:27:36 |
| alexfmpe | $ nix-build -A pkgsCross.ghcjs.haskell.packages.ghc912.miso <-- this is how one builds miso for js backend on 9.12 inside nixpkgs | 22:28:39 |
| maralorn | I kinda hate doing nix and nixpkgs stuff to. I also just wanna program Haskell apps. Alas, someone has to do the plumbing. Our collective goal here is to make all of this as smooth as possible, so that we can all get back to writing software. 😄 | 22:29:39 |
| maralorn | * I kinda hate doing nix and nixpkgs stuff, too. I also just wanna program Haskell apps. Alas, someone has to do the plumbing. Our collective goal here is to make all of this as smooth as possible, so that we can all get back to writing software. 😄 | 22:29:52 |
| alexfmpe | yeah, we're kind of in ripping off the band aid mode at this point | 22:35:25 |
| maralorn | I mean really we in this channel are really not responsible for any of the ecosystem developments we just try to keep it all working together. 😄 | 22:35:33 |
| alexfmpe | do you have a sense on how old their nixpkgs pin is? | 22:38:33 |
| alexfmpe | like, are they using recent nixpkgs or not anywhere near that | 22:39:31 |
| @dmjio:matrix.org | I'll try to get him in here to ask so I don't say the wrong thing | 22:39:52 |
| @dmjio:matrix.org | alright let me try this, ideally I could just update miso's nix scripts to this and then nixpkgs 25 and hope and pray for the best? | 22:41:16 |
 emily | (I think the decisions that lead to being on years-old Nixpkgs and years-old GHC and years-old […] are not uncorrelated…) | 22:41:42 |
| alexfmpe | well I don't know about the "linking" bits of closure compiler and whatnot, but haskell-wise that's building on haskell-updates | 22:41:46 |
| alexfmpe | well it might not matter for you if you're only getting libraries out of nixpkgs | 22:42:28 |
| emily | (which is fine, until you diverge from the pattern by also picking "new OS version" or "new Nixpkgs version" or … and then either something breaks or a whole lot of maintenance burden just got offloaded on someone else) | 22:42:36 |
| alexfmpe | it'll just be a problem for me getting miso-examples building and running in nixpkgs heh | 22:42:51 |
| emily | (and since it's Nixpkgs it's probably the responsibility-without-authority kind that has reliably burned people out for years…) | 22:43:09 |
 Tristan Ross | In reply to @emilazy:matrix.org
(and since it's Nixpkgs it's probably the responsibility-without-authority kind that has reliably burned people out for years…) Yeah, I think we're fixing the authority problem a bit with teams. Having people who are dedicated to working on specific things help. | 22:44:27 |
| alexfmpe | note you probably won't get much caching from nixos.org yet, especially on mac
not a problem for your downstream, but might be annoying now for you if you end up compiling 9.10 to compile 9.12 and such | 22:44:52 |
| alexfmpe | * note you probably won't get much caching from nixos.org yet, especially on mac
not a problem for your downstream since you have your own caching, but might be annoying now for you if you end up compiling 9.10 to compile 9.12 and such | 22:45:02 |
| emily | a team only means anything if it has defined responsibilities and authority and a clear path to resolution when teams have conflicting needs, which is not something Nixpkgs has historically been any good at | 22:45:38 |
| @dmjio:matrix.org | this tbh, got so bad I stopped doing version bounds in my cabal file, because you /had/ to use nix to work with ghcjs, stack dropped support, cabal-install was only used for building, nix was the resolver. Now stuff "works" again and the cabal people are upset that I'm making it hard for their constraint solver by underspeciying constraints | 22:46:57 |
