| 10 Feb 2025 |
 Tristan Ross | In reply to @emilazy:matrix.org
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 Yeah, one of the things I've learned is if you want something done then you have to take authority because not many people are going to. | 22:47:09 |
 @dmjio:matrix.org | I think GHCJS just reads all the JS into memory from every dep. to concat it (aka JS linking) and it just blows the heap | 22:51:48 |
| @dmjio:matrix.org | a user said builds were taking 8GB resident and minutes to link | 22:53:14 |
 alexfmpe | I do remember 16GB ram being recommended minimum for ghcjs linking heh | 22:53:45 |
| alexfmpe | data point: I just checked and nix-build -A haskell.packages.ghc810.miso builds on a days-old master | 22:54:56 |
| alexfmpe | it doesn't on haskell-updates, but only like 4 deps fail, I don't mind fixing that | 22:55:05 |
| alexfmpe | so I guess the question becomes, is anyone using miso with ghcjs from today's nixpkgs that would also be driven into a corner if they didn't get to bump nixpkgs until js backend was feature par out of nixpkgs? | 22:55:11 |
| alexfmpe | (and that's assuming the ghcjs build works on that nixpkgs, but that build takes longer to have an answer for) | 22:56:50 |
| alexfmpe | * (and that's assuming that ghcjs 8.10 build works on this days-old nixpkgs, but that build takes longer to have an answer for) | 22:57:06 |
| @dmjio:matrix.org | that I'm not sure, there's one person in particular who would know Tysonzer0 and he's not online, but I've pinged to join. All of miso's examples and haskell-miso.org use the 6 year old hash. | 22:58:04 |
| @dmjio:matrix.org | I can make a PR to update my nix scripts and bump the nixpkgs hash to latest see how far it gets. | 23:04:18 |
| @dmjio:matrix.org | alexfmpe let me check the payload sizes again rn and compare with what you've shown | 23:04:27 |
| alexfmpe | I'd say compare with and without -dedupe, but not closure nor compression | 23:05:06 |
| alexfmpe | I'm not sure if -dedupe per-se will come back | 23:05:36 |
| alexfmpe | doyougnu: do you...gnow? | 23:05:49 |
|  Kyle joined the room. | 23:30:40 |
| @dmjio:matrix.org | 
Download image.png | 23:53:26 |
| @dmjio:matrix.org | alexfmpe: w/o the -dedupe too .. not sure if that even does anything anymore. There was a time when js-sources were duplicated in all.js though. 3x smaller | 23:54:07 |
| @dmjio:matrix.org | $ nix-build --arg examples true -A miso-examples
| 23:54:54 |
| alexfmpe | Hmmm about 2.5x or so. I wonder if the gap goes down considerably post closure and compression | 23:56:09 |
| alexfmpe | Though... it might already be less bloated than 10 | 23:57:06 |
| alexfmpe | * Though... it might already be less bloated than 8.10 | 23:57:13 |
| alexfmpe | Huh I wonder if I can already build my project with 9.12 js backend | 23:58:00 |
| alexfmpe | Ah one thing though | 23:58:56 |
| alexfmpe | The stuff coming out of the derivation I pasted and it's all ~10MBs | 23:59:23 |
| alexfmpe | I think that's an actual executable | 23:59:33 |
| alexfmpe | At least it is for the hello package | 23:59:53 |
| 11 Feb 2025 |
| alexfmpe | I'm not sure what else is there, maybe just a call to nodejs | 00:00:43 |
| alexfmpe | * The stuff coming out of the derivation I pasted where it's all ~10MBs... | 00:01:08 |
| Tristan Ross | https://endoflife.date/ghc this is fun to look at, anything older than 9.2 isn't supported at all. | 00:04:22 |
