Newest at the top
| 2024-12-28 06:39:01 +0100 | chexum | (~quassel@gateway/tor-sasl/chexum) chexum |
| 2024-12-28 06:38:30 +0100 | chexum | (~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection) |
| 2024-12-28 06:37:00 +0100 | notzmv | (~umar@user/notzmv) notzmv |
| 2024-12-28 06:31:40 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-12-28 06:30:57 +0100 | gorignak | (~gorignak@user/gorignak) (Quit: quit) |
| 2024-12-28 06:27:09 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 06:20:34 +0100 | gorignak | (~gorignak@user/gorignak) gorignak |
| 2024-12-28 06:19:24 +0100 | remedan | (~remedan@ip-62-245-108-153.bb.vodafone.cz) remedan |
| 2024-12-28 06:17:07 +0100 | Feuermagier | (~Feuermagi@user/feuermagier) (Quit: Leaving) |
| 2024-12-28 06:16:52 +0100 | remedan_ | (~remedan@ip-62-245-108-153.bb.vodafone.cz) (Quit: Bye!) |
| 2024-12-28 06:15:14 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2024-12-28 06:11:12 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2024-12-28 06:10:40 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 06:08:31 +0100 | <homo> | yeah, so much different from the rest :) |
| 2024-12-28 06:05:31 +0100 | <haskellbridge> | <sm> ah, a darcs user! |
| 2024-12-28 05:58:43 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 245 seconds) |
| 2024-12-28 05:54:32 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 05:49:00 +0100 | fun-safe-math | (~fun-safe-@2601:1c2:1b7f:801f:ece:4698:cd8b:41e1) fun-safe-math |
| 2024-12-28 05:47:44 +0100 | fun-safe-math | (~fun-safe-@2601:1c2:1b7f:801f:83ce:3f54:3f3c:7c89) (Quit: No Ping reply in 180 seconds.) |
| 2024-12-28 05:46:55 +0100 | rekahsoft | (~rekahsoft@76.69.85.220) (Remote host closed the connection) |
| 2024-12-28 05:45:42 +0100 | giost | (~giost@pool-72-74-37-230.bstnma.fios.verizon.net) |
| 2024-12-28 05:41:17 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds) |
| 2024-12-28 05:39:59 +0100 | <homo> | to me it is important to always have darcs available |
| 2024-12-28 05:38:27 +0100 | <homo> | at the very least until ghc's bootstrap problem is solved, the biggest haskell one will get on guix on riscv and arm is microhs |
| 2024-12-28 05:36:57 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 05:32:31 +0100 | <haskellbridge> | <sm> has microhs been compiled with ghc wasm yet I wonder |
| 2024-12-28 05:32:21 +0100 | <homo> | or even something crazyingly impossible for ghc: port microhs to plan9 and enjoy haskell2010 with 50 extensions |
| 2024-12-28 05:31:10 +0100 | <homo> | if there is any special work required for porting that is |
| 2024-12-28 05:30:46 +0100 | <homo> | another advantage of microhs is that it might be ported on more cpu architectures than ghc itself |
| 2024-12-28 05:29:57 +0100 | <haskellbridge> | <sm> a lighter haskell compiler would be great! try microhs and hell |
| 2024-12-28 05:28:55 +0100 | <homo> | what if ghc maintainers are secretly afraid that something can compile ghc faster than ghc compiles itself and that's why they make it impossible to bootstrap |
| 2024-12-28 05:27:15 +0100 | <homo> | another reason to have alternative haskell compiler: save resourses compiling it |
| 2024-12-28 05:24:44 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds) |
| 2024-12-28 05:21:48 +0100 | sayurc | (~sayurc@169.150.203.34) (Quit: Konversation terminated!) |
| 2024-12-28 05:21:34 +0100 | Feuermagier | (~Feuermagi@user/feuermagier) Feuermagier |
| 2024-12-28 05:20:39 +0100 | <geekosaur> | and then only because I use -j12 |
| 2024-12-28 05:20:14 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-28 05:20:13 +0100 | <monochrom> | couldn't do that with 4GB 7 years ago. |
| 2024-12-28 05:20:06 +0100 | <geekosaur> | my current machine is big enough that it only starts to breathe heavy when building ghc |
| 2024-12-28 05:19:36 +0100 | <monochrom> | Actually even two ghci open and one ghc compiling. |
| 2024-12-28 05:19:00 +0100 | haskellbridge | sm has 630 processes running here |
| 2024-12-28 05:18:51 +0100 | <monochrom> | Certainly I can keep two ghci open today but I couldn't back then. :) |
| 2024-12-28 05:18:21 +0100 | <geekosaur> | and except for that brief-ish period trying to use it as an emergency backup laptop, it spent its later years as a fileserver |
| 2024-12-28 05:17:50 +0100 | <haskellbridge> | <sm> homo: depends on the apps, doesn't it |
| 2024-12-28 05:17:20 +0100 | <geekosaur> | although I actually still have it and it may yet ride again: unlike at least some modern machines, it works on AC power even without a battery installed |
| 2024-12-28 05:17:07 +0100 | <homo> | so, when you need so much RAM, how much multi-tasking does your computer perform? can you keep more apps open today than you could 10 years ago? 20 years ago? |
| 2024-12-28 05:16:31 +0100 | <geekosaur> | I can't really complain much, it had a good full life until its battery finally died (nobody makes batteries for it any more, of course) |
| 2024-12-28 05:15:57 +0100 | <haskellbridge> | <sm> I'm remembering my 1K ZX80 |
| 2024-12-28 05:14:53 +0100 | <haskellbridge> | <sm> which in the grand scheme of things is an amazingly powerful machine, right?! It's just you've got to have software right sized / efficient enough for the hardware |
| 2024-12-28 05:13:41 +0100 | <geekosaur> | minuscule screen |