2024/12/22

Newest at the top

2024-12-22 08:20:55 +0100flukiluke(~m-7humut@2603:c023:c000:6c7e:8945:ad24:9113:a962) (Remote host closed the connection)
2024-12-22 08:16:49 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-22 08:12:15 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 08:09:12 +0100takuan(~takuan@178-116-218-225.access.telenet.be)
2024-12-22 08:02:48 +0100 <jaava> is haskell good for physics simulations where one would probably lean towards c++, fortran or python depending on the use case?
2024-12-22 08:01:59 +0100 <jaava> hi discovered haskell through xmonad but now i'm curious about using it for other things
2024-12-22 08:01:05 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-12-22 08:00:59 +0100jaava(~nick@syn-076-035-209-158.res.spectrum.com)
2024-12-22 07:54:34 +0100gorignak(~gorignak@user/gorignak) gorignak
2024-12-22 07:52:23 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 07:50:40 +0100Guest78(~Guest78@213.233.155.134) (Ping timeout: 240 seconds)
2024-12-22 07:44:54 +0100pavonia(~user@user/siracusa) (Quit: Bye!)
2024-12-22 07:43:51 +0100youthlic(~Thunderbi@user/youthlic) youthlic
2024-12-22 07:43:06 +0100hiredman(~hiredman@frontier1.downey.family) hiredman
2024-12-22 07:41:38 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-22 07:37:00 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 07:31:44 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-22 07:27:55 +0100agent314(~quassel@149.40.50.111) agent314
2024-12-22 07:27:25 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 07:16:39 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds)
2024-12-22 07:15:24 +0100tnt2tnt1
2024-12-22 07:15:24 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 265 seconds)
2024-12-22 07:14:22 +0100tnt2(~Thunderbi@user/tnt1) tnt1
2024-12-22 07:12:03 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 07:03:30 +0100tnt2tnt1
2024-12-22 07:03:30 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 252 seconds)
2024-12-22 07:03:21 +0100housemate_(~housemate@124.187.109.206) (Remote host closed the connection)
2024-12-22 07:02:50 +0100housemate(~housemate@124.187.109.206) (Ping timeout: 265 seconds)
2024-12-22 07:01:56 +0100tnt2(~Thunderbi@user/tnt1) tnt1
2024-12-22 07:01:23 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-22 07:00:22 +0100housemate_(~housemate@124.187.109.206) housemate
2024-12-22 06:56:40 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 06:50:45 +0100alecs(~alecs@61.pool85-58-154.dynamic.orange.es) (Ping timeout: 265 seconds)
2024-12-22 06:47:00 +0100CrunchyFlakes(~CrunchyFl@31.19.233.78)
2024-12-22 06:46:21 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 276 seconds)
2024-12-22 06:46:10 +0100alecs(~alecs@61.pool85-58-154.dynamic.orange.es) alecs
2024-12-22 06:44:30 +0100CrunchyFlakes(~CrunchyFl@ip1f13e94e.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer)
2024-12-22 06:41:18 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 06:39:28 +0100tnt1(~Thunderbi@user/tnt1) tnt1
2024-12-22 06:33:05 +0100tnt1(~Thunderbi@user/tnt1) (Ping timeout: 248 seconds)
2024-12-22 06:30:30 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-22 06:25:54 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-22 06:25:14 +0100ryanbooker(uid4340@id-4340.hampstead.irccloud.com) (Quit: Connection closed for inactivity)
2024-12-22 06:23:54 +0100 <monochrom> Having said that, if you say you are only using GHC, then you know it almost sticks to "use lazy for non-strict, use eager for strict". But there are occasional deviations when the code optimizer thinks it's more efficient to do it some other way.
2024-12-22 06:21:38 +0100 <haskellbridge> <Bowuigi> I see, yeah Haskell can be hard to understand sometimes lol
2024-12-22 06:17:53 +0100poscat0x04(~poscat@user/poscat) poscat
2024-12-22 06:17:42 +0100poscat(~poscat@user/poscat) (Read error: Connection reset by peer)
2024-12-22 06:17:32 +0100 <monochrom> Denotational semantics strives to (even prides in) avoid talking about them.
2024-12-22 06:16:58 +0100 <monochrom> Yes absolutely. If you want to predict how much time and how much space are spent, they emphatically require knowing the evaluation strategy, i.e., operational.
2024-12-22 06:15:40 +0100 <haskellbridge> <Bowuigi> So the duplication is operational right?