2025/10/28

Newest at the top

2025-10-28 13:42:24 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Quit: = "")
2025-10-28 13:40:33 +0100Lycurgus(~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org ))
2025-10-28 13:38:49 +0100tromp(~textual@2001:1c00:3487:1b00:b825:23c0:1f89:fdbd) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-10-28 13:35:44 +0100Googulator89(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 13:35:44 +0100Googulator8(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 13:30:38 +0100Googulator89(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 13:30:29 +0100Googulator89(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 13:21:35 +0100 <Lycurgus> biz logic and hs - culturally discordant / cognitively dissonant
2025-10-28 13:20:45 +0100Googulator62(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 13:20:45 +0100Googulator89(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 13:19:11 +0100chele(~chele@user/chele) chele
2025-10-28 13:18:23 +0100 <kuribas> IMO even worse if it comes from the database, and you don't even know the shape of data without inspecting the database.
2025-10-28 13:17:45 +0100 <kuribas> [exa]: Without data, like in clojure, it's just loosely modelled "somewhere".
2025-10-28 13:17:17 +0100 <kuribas> [exa]: I see "data" as modelling the entities of the business logic.
2025-10-28 13:16:07 +0100Zemy_(~Zemy@2600:100c:b0a5:5276:63:4fff:fe56:bec) (Ping timeout: 260 seconds)
2025-10-28 13:15:49 +0100merijn(~merijn@77.242.116.146) merijn
2025-10-28 13:15:44 +0100Googulator49(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 13:15:37 +0100Googulator62(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 13:13:25 +0100 <[exa]> (doc refers to papers from 1995-ish)
2025-10-28 13:13:05 +0100Zemy(~Zemy@72.178.108.235)
2025-10-28 13:12:27 +0100Zemy(~Zemy@72.178.108.235) (Read error: Connection reset by peer)
2025-10-28 13:11:46 +0100Zemy_(~Zemy@2600:100c:b0a5:5276:63:4fff:fe56:bec)
2025-10-28 13:11:23 +0100 <[exa]> is there actually some tech docs behind hoogle? in particular, how complex queries it can handle
2025-10-28 13:09:05 +0100bggd(~bgg@2a01:e0a:819:1510:698b:6600:5c85:9225)
2025-10-28 13:08:35 +0100 <[exa]> ok not "most" but it constraints the implementation pretty well, esp. if you manage to have the interpretish types, and esp. if you manage to separate the issue into nice blobs that only touch each other's `data`
2025-10-28 13:07:09 +0100 <__monty__> IME it's definitely not most business logic.
2025-10-28 13:06:55 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 264 seconds)
2025-10-28 13:06:55 +0100 <__monty__> Like the interpreter pattern?
2025-10-28 13:06:45 +0100Lycurgus(~juan@user/Lycurgus) Lycurgus
2025-10-28 13:05:57 +0100 <[exa]> kuribas: btw the types are a good counter-argument, in haskell most of the "business logic" tends to get implemented in `data` definitions instead of functions. :D
2025-10-28 13:03:29 +0100 <[exa]> in the case of business logic vs. stupid bugs that prevent you to refactor to new business logic, it becomes 99.99999-0.00001 rule
2025-10-28 13:02:54 +0100 <[exa]> kuribas: people tend to ignore the 80-20 rule when talking about programs
2025-10-28 13:01:49 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-10-28 12:59:01 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2025-10-28 12:58:23 +0100koz(~koz@121.99.240.58)
2025-10-28 12:57:40 +0100koz(~koz@121.99.240.58) (Ping timeout: 246 seconds)
2025-10-28 12:56:59 +0100trickard_(~trickard@cpe-55-98-47-163.wireline.com.au)
2025-10-28 12:56:46 +0100trickard(~trickard@cpe-55-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-10-28 12:54:48 +0100Googulator49(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu)
2025-10-28 12:54:32 +0100Googulator49(~Googulato@2a01-036d-0106-03fa-d161-d36f-e0e5-1b0a.pool6.digikabel.hu) (Quit: Client closed)
2025-10-28 12:49:01 +0100ttybitnik(~ttybitnik@user/wolper) ttybitnik
2025-10-28 12:48:31 +0100trickard_trickard
2025-10-28 12:47:04 +0100 <__monty__> Hoogle is a killer feature that's only possible due to Haskell's type system.
2025-10-28 12:46:03 +0100xff0x(~xff0x@2405:6580:b080:900:be8e:c85:6713:439e)
2025-10-28 12:39:43 +0100Lord_of_Life_Lord_of_Life
2025-10-28 12:38:55 +0100Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 240 seconds)
2025-10-28 12:38:21 +0100Lord_of_Life_(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-10-28 12:37:02 +0100Zemy_(~Zemy@2600:100c:b0a5:5276:7458:afff:fe16:3be) (Ping timeout: 256 seconds)
2025-10-28 12:33:49 +0100Zemy(~Zemy@72.178.108.235)
2025-10-28 12:32:40 +0100Zemy(~Zemy@72.178.108.235) (Read error: Connection reset by peer)