2025/05/06

Newest at the top

2025-05-06 17:32:12 +0200tv(~tv@user/tv) (Read error: Connection reset by peer)
2025-05-06 17:32:12 +0200lbseale(~quassel@user/ep1ctetus) ep1ctetus
2025-05-06 17:27:08 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Quit: WeeChat 4.5.2)
2025-05-06 17:22:49 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 17:22:00 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer)
2025-05-06 17:22:00 +0200 <haskellbridge> <Liamzee> dotmorphism is okay?
2025-05-06 17:17:43 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-05-06 17:13:47 +0200 <haskellbridge> <Liamzee> Claude and Deepseek convinced me and each other that Zeromorph was a good name, when it refers to a constant and co-constant morphism. facepalm
2025-05-06 17:13:01 +0200 <haskellbridge> <Liamzee> had a disaster with LLM just now, I was looking for Haskell-themed website names, oriented around the arrow from the initial object
2025-05-06 17:11:50 +0200 <haskellbridge> <Liamzee> "When you realize that Gabriella Gonzalez's haskellforall.com blog is actually a pun on explicit universal quantification"
2025-05-06 17:11:16 +0200 <haskellbridge> <Liamzee> things that happen to you in life:
2025-05-06 17:06:41 +0200connrs(~connrs@user/connrs) connrs
2025-05-06 17:04:44 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61)
2025-05-06 16:55:59 +0200ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-05-06 16:54:01 +0200vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 244 seconds)
2025-05-06 16:40:37 +0200fp(~Thunderbi@2001:708:20:1406::10c5) (Ping timeout: 276 seconds)
2025-05-06 16:32:54 +0200tromp(~textual@2001:1c00:3487:1b00:cdc3:f42b:30fc:1c61) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-05-06 16:25:06 +0200ColinRobinson(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-05-06 16:19:43 +0200vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-05-06 16:16:27 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-06 16:16:10 +0200euleritian(~euleritia@dynamic-176-006-138-148.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-06 16:09:08 +0200 <df> but time has never been very reliable for that anyway, that's why we invented vector clocks etc
2025-05-06 16:08:25 +0200 <yin> wait no, that was Doc Brown
2025-05-06 16:08:25 +0200 <yin> "quickly, there's no time!"
2025-05-06 16:08:15 +0200 <df> yin: made life easier for a bunch of programmers? ordering events might be tricky though, I admit
2025-05-06 16:07:33 +0200hughjfchen(~hughjfche@vmi2417424.contaboserver.net) hughjfchen
2025-05-06 16:07:26 +0200merijn(~merijn@77.242.116.146) merijn
2025-05-06 16:07:08 +0200comerijn(~merijn@77.242.116.146) (Read error: Connection reset by peer)
2025-05-06 16:06:16 +0200hughjfchen(~hughjfche@vmi2417424.contaboserver.net) (Ping timeout: 244 seconds)
2025-05-06 16:05:47 +0200 <df> ... c'mon, somebody's gotta complete the douglas adams quote
2025-05-06 16:05:09 +0200 <yin> won't we miss async communication though? oh no what have we done?
2025-05-06 16:02:13 +0200 <df> time is an illusion anyway
2025-05-06 16:02:08 +0200 <df> good work, we can synchronise the entire world if we try
2025-05-06 16:02:03 +0200danza(~danza@user/danza) (Remote host closed the connection)
2025-05-06 16:01:30 +0200 <yin> we'll all be on the same time... soon
2025-05-06 16:01:20 +0200 <yin> done. they also wrote it down and will spread the word
2025-05-06 16:01:03 +0200danza(~danza@user/danza) danza
2025-05-06 16:01:01 +0200 <yin> wait
2025-05-06 16:00:49 +0200 <yin> i'm also telling all my contacts
2025-05-06 16:00:46 +0200 <df> ok, so we're sychronised, problem solved ;)
2025-05-06 16:00:24 +0200 <yin> df: ok i wrote it down too
2025-05-06 15:58:59 +0200 <df> it's 11:27:23 AM
2025-05-06 15:58:32 +0200 <df> yin: easily solved, I looked up the time earlier and wrote it down
2025-05-06 15:58:25 +0200 <haskellbridge> <maerwald> you can become an LLM input engineer
2025-05-06 15:57:58 +0200 <yin> there's that concept again
2025-05-06 15:57:30 +0200 <haskellbridge> <maerwald> time for a career change
2025-05-06 15:56:39 +0200 <yin> maerwald: i have come to accept that programming is boring any way
2025-05-06 15:55:12 +0200 <yin> messy UTC is just a result of that
2025-05-06 15:54:52 +0200 <yin> like the need for two people to independently agree on "what time it is now"
2025-05-06 15:54:02 +0200 <yin> tomsmeding: oh i mean "time" in general