2026/01/23

2026-01-23 00:02:18 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2026-01-23 00:03:18 +0100__monty__(~toonn@user/toonn) (Quit: leaving)
2026-01-23 00:04:51 +0100zanetti(~zanetti@2804:7f0:9b80:2edc:c121:46e7:c35f:46cf) zanetti
2026-01-23 00:13:09 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 00:14:16 +0100 <jackdk> Perhaps most approachable free intro. Optics By Example is worth the price.
2026-01-23 00:18:12 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-01-23 00:18:26 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au)
2026-01-23 00:20:24 +0100 <chromoblob> how the fuck are you supposed to write Haskell without recursion
2026-01-23 00:20:25 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-01-23 00:20:52 +0100 <chromoblob> and how is Haskell without recursion supposed to be useful
2026-01-23 00:23:28 +0100 <geekosaur> I think tht usually means without _explicit_ recursion, e.g. using folds/traverses
2026-01-23 00:28:53 +0100zanetti(~zanetti@2804:7f0:9b80:2edc:c121:46e7:c35f:46cf) (Quit: Konversation terminated!)
2026-01-23 00:33:34 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au) (Ping timeout: 244 seconds)
2026-01-23 00:34:08 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au)
2026-01-23 00:34:18 +0100 <jreicher> chromoblob: who's saying you should write Haskell without recursion?
2026-01-23 00:34:30 +0100Hafydd(~Hafydd@user/hafydd) (Quit: WeeChat 4.8.1)
2026-01-23 00:40:35 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-01-23 00:42:00 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2026-01-23 00:47:48 +0100RMSBach(~RMSBach@24.210.9.182) RMSBach
2026-01-23 00:50:23 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 00:50:25 +0100vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 264 seconds)
2026-01-23 00:51:03 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2026-01-23 00:55:03 +0100Hafydd(~Hafydd@user/hafydd) Hafydd
2026-01-23 00:56:36 +0100Square3(~Square4@user/square) Square
2026-01-23 01:00:06 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2026-01-23 01:10:11 +0100 <EvanR> the answer the question, certain patterns of recursion can be encapulsated in combinators that magically have the same effect
2026-01-23 01:10:13 +0100 <EvanR> to
2026-01-23 01:10:31 +0100 <EvanR> e.g. map and fold
2026-01-23 01:10:42 +0100 <EvanR> they can't do everything, but the more such tools you have the more you can do
2026-01-23 01:10:58 +0100 <EvanR> but sometimes explicit recursion makes more sense
2026-01-23 01:11:28 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 01:16:39 +0100 <probie> how are imperative languages without goto supposed to be useful?
2026-01-23 01:16:39 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-01-23 01:25:31 +0100Zemy_(~Zemy@2600:100c:b0ab:ed8b:c474:c7ff:febb:8ed3)
2026-01-23 01:27:14 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 01:28:13 +0100Zemy(~Zemy@72.178.108.235) (Ping timeout: 246 seconds)
2026-01-23 01:32:00 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2026-01-23 01:33:28 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-01-23 01:33:42 +0100trickard_(~trickard@cpe-93-98-47-163.wireline.com.au)
2026-01-23 01:43:02 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 01:48:16 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2026-01-23 01:51:32 +0100Zemy(~Zemy@syn-192-154-181-091.biz.spectrum.com)
2026-01-23 01:55:54 +0100Zemy_(~Zemy@2600:100c:b0ab:ed8b:c474:c7ff:febb:8ed3) (Ping timeout: 260 seconds)
2026-01-23 01:56:13 +0100Square3(~Square4@user/square) (Ping timeout: 246 seconds)
2026-01-23 01:58:49 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 02:01:45 +0100Zemy_(~Zemy@2600:100c:b0ab:ed8b:9876:2aff:fe33:1a1d)
2026-01-23 02:03:37 +0100Zemy(~Zemy@syn-192-154-181-091.biz.spectrum.com) (Ping timeout: 264 seconds)
2026-01-23 02:03:49 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds)
2026-01-23 02:05:55 +0100 <systemfault> for loops/while/etc...
2026-01-23 02:07:45 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-01-23 02:08:40 +0100 <jackdk> I think probie is asking rhetorically, to provide an analogous question/answer pair to chromoblob/EvanR.
2026-01-23 02:08:58 +0100 <EvanR> lol
2026-01-23 02:09:57 +0100 <EvanR> clearly systemfault is answering in such a way intentionally to highlight the irony
2026-01-23 02:10:53 +0100 <EvanR> this is what it's like in the tiplerian omega point simulation where everyone already knows everything anyone could talk about
2026-01-23 02:11:35 +0100 <systemfault> Yeah... that said, I don't know what a tiplerian omega point simulation is...
2026-01-23 02:13:14 +0100 <geekosaur> sounds to me like someone's been tippling on physics 🙂
2026-01-23 02:14:37 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 02:15:37 +0100xff0x(~xff0x@2405:6580:b080:900:52f9:378c:6eea:47d5) (Ping timeout: 265 seconds)
2026-01-23 02:17:50 +0100Pozyomka_(~pyon@user/pyon) (Ping timeout: 245 seconds)
2026-01-23 02:19:41 +0100Pozyomka(~pyon@user/pyon) pyon
2026-01-23 02:19:49 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-01-23 02:21:54 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2026-01-23 02:30:02 +0100Zemy(~Zemy@72.178.108.235)
2026-01-23 02:30:17 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 02:31:59 +0100Zemy_(~Zemy@2600:100c:b0ab:ed8b:9876:2aff:fe33:1a1d) (Ping timeout: 250 seconds)
2026-01-23 02:35:26 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2026-01-23 02:39:37 +0100Square2(~Square@user/square) (Ping timeout: 264 seconds)
2026-01-23 02:42:24 +0100Inline(~User@2001-4dd7-bc56-0-fdb7-c703-fc72-e0a.ipv6dyn.netcologne.de) (Ping timeout: 252 seconds)
2026-01-23 02:43:44 +0100omidmash3(~omidmash@user/omidmash) omidmash
2026-01-23 02:45:34 +0100omidmash(~omidmash@user/omidmash) (Ping timeout: 246 seconds)
2026-01-23 02:45:34 +0100omidmash3omidmash
2026-01-23 02:46:04 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 02:50:36 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2026-01-23 02:54:36 +0100Inline(~User@2001-4dd7-bc56-0-bf4e-84aa-8c9c-590c.ipv6dyn.netcologne.de) Inline
2026-01-23 03:01:29 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-01-23 03:08:07 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2026-01-23 03:10:07 +0100 <Leary> chromoblob: Write all your co/inductive co/data types in greatest/least-fixed-point form, and all your logic in folds. It's not even as bad as it sounds!
2026-01-23 03:11:43 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...)