2026/04/28

Newest at the top

2026-04-28 01:38:33 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2026-04-28 01:37:21 +0000yin(~zero@user/zero) (Ping timeout: 244 seconds)
2026-04-28 01:31:52 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 01:31:17 +0000dtman34(~dtman34@c-73-242-68-179.hsd1.mn.comcast.net) dtman34
2026-04-28 01:23:31 +0000yin(~zero@user/zero) zero
2026-04-28 01:22:28 +0000 <janus> would be interesting to hear if you also recognize guarantees like that in practical database libraries... because i am a bit unsure if what is said maps 1:1 to rel8 and such
2026-04-28 01:21:10 +0000haskellbridgesm hasn't listened to this episode yet either
2026-04-28 01:21:01 +0000 <janus> pretty sure rel8 also has an answer to this question
2026-04-28 01:20:44 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-04-28 01:20:27 +0000 <janus> they do mention in the podcast that they want guarantees that you don't avoid n+1 queries. and that did make me think of the Orville db library we use at flipstone, which attempts something similar
2026-04-28 01:16:30 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 01:15:40 +0000 <monochrom> I did not listen to the podcast. I would write declaratively in the first place; if something optimizes it, that's a bonus, but even if not, I'm fine with it. My experience is that declarative code is easier to change than imperative code when requirement changes in the future. And easier to reverse-engineer---hell, declarative is defined to mean nothing to reverse-engineer.
2026-04-28 01:14:48 +0000 <janus> the one by Jane Street is more practical, i'd say
2026-04-28 01:14:33 +0000 <janus> i like Type Theory Forall a lot, but it is also necessarily academic (just younger academics). so i suppose it is also not the engineer's podcast you're looking for
2026-04-28 01:14:16 +0000 <haskellbridge> <sm> I love the podcast. I like hearing the history and especially from the long time researchers. But it could really use more practitioner interviews for balance
2026-04-28 01:13:54 +0000yin(~zero@user/zero) (Ping timeout: 248 seconds)
2026-04-28 01:13:26 +0000 <haskellbridge> <sm> Real World Haskell !
2026-04-28 01:13:04 +0000 <haskellbridge> <sm> I love the podcast. I like hearing the history and especially from the long time researchers. But it could really use more modern practitioner voices for balance
2026-04-28 01:11:30 +0000 <janus> i do feel like a premise this retrospective is necessarily shaping the culture though
2026-04-28 01:11:10 +0000 <janus> but i am so glad i am not the only one ranting
2026-04-28 01:11:02 +0000 <janus> hah well that's a question of taste :D
2026-04-28 01:10:29 +0000 <haskellbridge> <sm> and while I'm ranting.. that damn music ! It is so depressing !
2026-04-28 01:10:00 +0000 <haskellbridge> <sm> it's not just the technical content, it's sometimes the long story of academic career, moves, etc blah blah blah :)
2026-04-28 01:09:48 +0000 <janus> THANK YOU sm
2026-04-28 01:08:58 +0000 <haskellbridge> <sm> damnit jim, I'm an engineer not a professor
2026-04-28 01:08:47 +0000 <janus> we're compiling an imperative program to SQL (declarative style), only for the query planner to compile it back into a series of index lookups? how is this not esoteric?
2026-04-28 01:08:41 +0000 <haskellbridge> <sm> it is hard to handle the intense academic content of the podcast sometimes
2026-04-28 01:07:19 +0000 <janus> somebody, please explain to me how this has any useful application beside code golfing?
2026-04-28 01:06:45 +0000 <janus> am i listening to a code golfing podcast?
2026-04-28 01:06:25 +0000 <janus> regarding the technical content... i know they are talking to an academic. but to my ears, i can't see the practicality in compiling an imperative program to recursive CTEs using trampolines
2026-04-28 01:05:44 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2026-04-28 01:03:59 +0000 <janus> imagine a college freshman listening to the Interlude, they must feel like Haskell is for dinosaurs :O
2026-04-28 01:03:20 +0000 <janus> i just feel like it is so very anachronistic and nostalgic, how can anybody stand it
2026-04-28 01:02:52 +0000havochunter(~havochunt@2a02-a467-ef2-0-f6c3-1c29-6870-3369.fixed6.kpn.net) (Remote host closed the connection)
2026-04-28 01:02:43 +0000 <janus> they are kinda explaining where MonadComprehensions and TransformLispComp come from
2026-04-28 01:02:18 +0000 <janus> did anyone listen to the latest Haskell Interlude? it
2026-04-28 01:00:42 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 00:49:54 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-04-28 00:48:52 +0000bkani(~bkani@user/bkani) bkani
2026-04-28 00:45:41 +0000tzh_(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Ping timeout: 244 seconds)
2026-04-28 00:45:10 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2026-04-28 00:44:57 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 00:42:48 +0000bkani(~bkani@user/bkani) (Ping timeout: 265 seconds)
2026-04-28 00:34:52 +0000bkani(~bkani@user/bkani) bkani
2026-04-28 00:34:12 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2026-04-28 00:31:13 +0000arandombit(~arandombi@user/arandombit) (Ping timeout: 244 seconds)
2026-04-28 00:29:08 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 00:22:06 +0000acidjnk_new3(~acidjnk@p200300d6e700e5152a5a580b5c2ab95f.dip0.t-ipconnect.de) (Remote host closed the connection)
2026-04-28 00:18:08 +0000xff0x(~xff0x@ah206235.dynamic.ppp.asahi-net.or.jp)
2026-04-28 00:17:57 +0000merijn(~merijn@62.45.136.136) (Ping timeout: 246 seconds)