2026/04/28

Newest at the top

2026-04-28 03:48:19 +0000gabriel_sevecek(~gabriel@92-180-227-14.dynamic.orange.sk) (Ping timeout: 272 seconds)
2026-04-28 03:47:21 +0000dutchie(~dutchie@user/dutchie) (Remote host closed the connection)
2026-04-28 03:45:52 +0000merijn(~merijn@62.45.136.136) merijn
2026-04-28 03:44:29 +0000bkani(~bkani@user/bkani) (Ping timeout: 245 seconds)
2026-04-28 03:44:21 +0000emaczen(~user@user/emaczen) (Ping timeout: 244 seconds)
2026-04-28 03:42:34 +0000gabriel_sevecek(~gabriel@92-180-227-14.dynamic.orange.sk) gabriel_sevecek
2026-04-28 03:41:07 +0000gabriel_sevecek(~gabriel@92-180-224-71.dynamic.orange.sk) (Ping timeout: 264 seconds)
2026-04-28 03:36:58 +0000bkani(~bkani@user/bkani) bkani
2026-04-28 03:34:47 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2026-04-28 03:30:23 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 03:26:18 +0000bitmapper(uid464869@id-464869.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2026-04-28 03:23:24 +0000bkani(~bkani@user/bkani) (Ping timeout: 255 seconds)
2026-04-28 03:20:50 +0000jmcantrell_jmcantrell
2026-04-28 03:18:52 +0000bkani(~bkani@user/bkani) bkani
2026-04-28 03:09:48 +0000jmcantrell_(~weechat@user/jmcantrell) jmcantrell
2026-04-28 03:05:37 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2026-04-28 03:05:15 +0000bkani(~bkani@user/bkani) (Ping timeout: 246 seconds)
2026-04-28 03:04:41 +0000tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Remote host closed the connection)
2026-04-28 03:02:20 +0000ephapticpulse(~user@user/ephapticpulse) ephapticpulse
2026-04-28 03:01:28 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2026-04-28 03:00:48 +0000bkani(~bkani@user/bkani) bkani
2026-04-28 03:00:23 +0000bkani(~bkani@user/bkani) (Remote host closed the connection)
2026-04-28 02:56:33 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 02:45:10 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-04-28 02:42:52 +0000chexum(~quassel@gateway/tor-sasl/chexum) chexum
2026-04-28 02:42:39 +0000chexum(~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection)
2026-04-28 02:38:05 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 02:31:38 +0000Square(~Square4@user/square) (Ping timeout: 248 seconds)
2026-04-28 02:27:09 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2026-04-28 02:22:43 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 02:10:18 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)
2026-04-28 02:05:42 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 02:00:04 +0000rekahsoft(~rekahsoft@70.51.99.119) (Remote host closed the connection)
2026-04-28 01:57:14 +0000xff0x(~xff0x@ah206235.dynamic.ppp.asahi-net.or.jp) (Ping timeout: 256 seconds)
2026-04-28 01:55:18 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-04-28 01:50:00 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-28 01:47:56 +0000yin(~zero@user/zero) zero
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