Newest at the top
| 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 |
| 2024-12-28 05:13:09 +0100 | <geekosaur> | the really extreme case was when I was temporarily limited to an old eee pc laptop. 600MHz Atom, 2GB |
| 2024-12-28 05:12:44 +0100 | <haskellbridge> | <sm> +big |
| 2024-12-28 05:12:25 +0100 | <haskellbridge> | <sm> but yes 4G isn't much for today's apps |
| 2024-12-28 05:12:12 +0100 | <haskellbridge> | <sm> * bad |
| 2024-12-28 05:12:06 +0100 | <haskellbridge> | <sm> your computer may have been running some other things as well. Also, the project you had open in VSC might have been a factor. Also, you might have been unlucky and hit a bug ? It sounds abd |
| 2024-12-28 05:11:52 +0100 | <haskellbridge> | <loonycyborg> ye I guess it's about having 64Gb ram everywhere now |
| 2024-12-28 05:11:18 +0100 | <geekosaur> | I think it's the latter |
| 2024-12-28 05:11:01 +0100 | <haskellbridge> | <loonycyborg> or it's always like running an extra browser per app |
| 2024-12-28 05:10:44 +0100 | <haskellbridge> | <loonycyborg> I'm not sure what electron apps do under the hood. Can they share resources? |
| 2024-12-28 05:10:44 +0100 | <geekosaur> | imagine chrome in 4GB, if you will |
| 2024-12-28 05:10:23 +0100 | <homo> | overloaded? I didn't even install any plugins, I ran with complete defaults |
| 2024-12-28 05:10:21 +0100 | <geekosaur> | I ripped apart a dead machine to scavenge its 16GB RAM to make a 4GB laptop I had usable |
| 2024-12-28 05:09:58 +0100 | <haskellbridge> | <sm> I guess it was overloaded. I have a couple of terrific daily-use electron apps, but more memory to run them in |
| 2024-12-28 05:09:54 +0100 | <geekosaur> | 4GB i'd believe |
| 2024-12-28 05:09:47 +0100 | <homo> | back then I was doing unity game development and unity was so painfully slow I gave up |
| 2024-12-28 05:09:10 +0100 | <glguy> | useful thing* |
| 2024-12-28 05:09:09 +0100 | <homo> | or was it 8GB RAM, I really forgot as I don't have it 2 years already |
| 2024-12-28 05:09:01 +0100 | <glguy> | It's a useful to not let single events shape your whole reality |
| 2024-12-28 05:08:49 +0100 | <homo> | it was 64-bit 4GB RAM laptop |
| 2024-12-28 05:07:31 +0100 | <haskellbridge> | <sm> what kind of machine homo ? |