2024/10/03

Newest at the top

2024-10-03 11:13:06 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 11:12:14 +0200yoneda(~mike@193.206.102.122)
2024-10-03 11:03:29 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-10-03 10:58:44 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 10:55:01 +0200Inst_(~Inst@user/Inst) (Ping timeout: 252 seconds)
2024-10-03 10:52:35 +0200liamzy__(~Inst@user/Inst) Inst
2024-10-03 10:50:44 +0200feetwind(~mike@user/feetwind) (Quit: WeeChat 4.1.2)
2024-10-03 10:47:54 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-10-03 10:46:58 +0200acidjnk(~acidjnk@p200300d6e72cfb63d87029be15e343a0.dip0.t-ipconnect.de) acidjnk
2024-10-03 10:44:07 +0200alexherbo2(~alexherbo@2a02-8440-3207-288e-206f-9822-5a5d-6079.rev.sfr.net) (Remote host closed the connection)
2024-10-03 10:43:08 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 10:39:56 +0200alexherbo2(~alexherbo@2a02-8440-3207-288e-206f-9822-5a5d-6079.rev.sfr.net) alexherbo2
2024-10-03 10:39:19 +0200mari-estel(~mari-este@dynamic-176-000-160-069.176.0.pool.telefonica.de)
2024-10-03 10:32:17 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-10-03 10:28:41 +0200Inst(~Inst@user/Inst) (Ping timeout: 265 seconds)
2024-10-03 10:27:42 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 10:26:05 +0200Inst_(~Inst@user/Inst) Inst
2024-10-03 10:25:57 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-10-03 10:17:05 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-10-03 10:12:05 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 10:02:24 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-10-03 09:57:33 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 09:54:35 +0200misterfish(~misterfis@84.53.85.146) misterfish
2024-10-03 09:48:30 +0200raym(~ray@user/raym) (Quit: updating server)
2024-10-03 09:46:49 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-10-03 09:46:43 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2024-10-03 09:42:52 +0200tzh_(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz)
2024-10-03 09:42:47 +0200machinedgod(~machinedg@d50-99-47-73.abhsia.telus.net) machinedgod
2024-10-03 09:41:44 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) merijn
2024-10-03 09:39:52 +0200arahael(~arahael@user/arahael) (Remote host closed the connection)
2024-10-03 09:38:10 +0200polyphem(~rod@p4fc2c55e.dip0.t-ipconnect.de) polyphem
2024-10-03 09:35:15 +0200econo_(uid147250@id-147250.tinside.irccloud.com) (Quit: Connection closed for inactivity)
2024-10-03 09:34:38 +0200amano(amano@gateway/vpn/airvpn/amano) (Quit: amano)
2024-10-03 09:33:46 +0200 <amano> probie: My application is already complete.
2024-10-03 09:33:38 +0200xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 252 seconds)
2024-10-03 09:32:53 +0200 <probie> I've given up attempting any sort of predication and (for personal projects) just start by dumping everything in a single module to be pulled apart as it becomes clearer how to do so
2024-10-03 09:32:20 +0200 <amano> The code is not the problem. The problem is the pilot that uses the program.
2024-10-03 09:31:56 +0200 <jackdk> Anyway, not my code, not my problem if the design hits trouble. I wish you the very best of luck and I genuinely hope that it succeeds.
2024-10-03 09:31:02 +0200merijn(~merijn@204-220-045-062.dynamic.caiway.nl) (Ping timeout: 255 seconds)
2024-10-03 09:30:59 +0200 <jackdk> I believe that one must be clairvoyant to reliably predict module boundaries. Applying modus ponens, we then conclude...
2024-10-03 09:30:49 +0200alioguzhan(~Thunderbi@78.173.89.238)
2024-10-03 09:30:43 +0200 <amano> until my death probably.
2024-10-03 09:30:32 +0200alioguzhan(~Thunderbi@78.173.89.238) (Remote host closed the connection)
2024-10-03 09:30:32 +0200 <amano> My application is largely finished and will probably not change....
2024-10-03 09:30:27 +0200xff0x_(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp)
2024-10-03 09:29:46 +0200 <amano> If I fail to predict module boundaries, then existential typeclasses break down.
2024-10-03 09:28:57 +0200 <jackdk> When I have been that confident in how I expect my code to evolve, I have often been humbled N < 10 months down the line.
2024-10-03 09:28:42 +0200 <amano> In my application, ui mode is totally independent from ui state. Thus, I can have an existential typeclass for ui mode and another for ui state.
2024-10-03 09:27:55 +0200 <amano> They don't need to know each other, and everything is fine.
2024-10-03 09:27:41 +0200 <amano> When things are disentangled, existential typeclasses don't hurt.