2025/10/03

Newest at the top

2025-10-03 07:43:35 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds)
2025-10-03 07:43:34 +0200aditya_an1l(~aditya_an@user/aditya-an1l:63825) aditya_an1l
2025-10-03 07:39:11 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 07:35:20 +0200trickard_trickard
2025-10-03 07:21:50 +0200takuan(~takuan@d8D86B9E9.access.telenet.be)
2025-10-03 07:12:56 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-10-03 07:11:00 +0200peterbecich(~Thunderbi@47-149-198-150.fdr01.slbh.ca.ip.frontiernet.net) peterbecich
2025-10-03 07:08:27 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 07:06:58 +0200Maeda(~Maeda@91-161-10-149.subs.proxad.net) (Quit: Done for the day!)
2025-10-03 07:03:44 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-10-03 07:00:22 +0200trickard_(~trickard@cpe-52-98-47-163.wireline.com.au)
2025-10-03 07:00:08 +0200trickard(~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-10-03 06:59:46 +0200 <ski> it's message-passing concurrency, as opposed to shared-memory concurrency (which would be hard to do, with transparent distribution)
2025-10-03 06:59:15 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 06:57:04 +0200Pozyomka(~pyon@user/pyon) pyon
2025-10-03 06:56:35 +0200 <jreicher> So the assumption is the concurrency-safety of side effects would be provided in other ways? I think I'm starting to understand...
2025-10-03 06:54:24 +0200 <ski> main focus was concurreny and distribution, with fault-tolerance (and fail-fast)
2025-10-03 06:53:11 +0200 <jreicher> I understand the positives of it, but I don't understand why they would do that while retaining the negatives of side-effects in functions.
2025-10-03 06:49:31 +0200 <ski> sending messages between processes
2025-10-03 06:49:25 +0200 <ski> Erlang basically gets "single assignment" ("instantiation") from Prolog (which is also why defining a variable in each branch makes it in scope after, like e.g. `if 2 > 3 -> X = 2 ; true -> X = 3 end,X * X', is a thing). the immutability of data structure values (including function values referencing non-local variables) helps with transparently sharing (same node) or cloning (different node) values when
2025-10-03 06:48:07 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-10-03 06:47:40 +0200chromoblob(~chromoblo@user/chromob1ot1c) chromoblob\0
2025-10-03 06:46:35 +0200chromoblob(~chromoblo@user/chromob1ot1c) (Ping timeout: 244 seconds)
2025-10-03 06:43:52 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 06:32:57 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds)
2025-10-03 06:28:28 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 06:26:34 +0200Googulator76(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu) (Quit: Client closed)
2025-10-03 06:25:45 +0200Googulator2(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu)
2025-10-03 06:21:00 +0200Googulator76(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu)
2025-10-03 06:20:47 +0200Googulator76(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu) (Quit: Client closed)
2025-10-03 06:16:55 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-10-03 06:15:07 +0200michalz(~michalz@185.246.207.197)
2025-10-03 06:10:27 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 06:00:54 +0200Googulator76(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu)
2025-10-03 06:00:41 +0200Googulator76(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu) (Quit: Client closed)
2025-10-03 05:59:19 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-10-03 05:53:29 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 05:42:37 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-03 05:40:44 +0200Googulator22(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu) (Quit: Client closed)
2025-10-03 05:40:40 +0200Googulator76(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu)
2025-10-03 05:38:04 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 05:27:37 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-03 05:22:36 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 05:16:09 +0200Googulator22(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu)
2025-10-03 05:16:03 +0200Googulator41(~Googulato@2a01-036d-0106-03fa-f110-0864-c42c-107f.pool6.digikabel.hu) (Quit: Client closed)
2025-10-03 05:13:59 +0200aforemny(~aforemny@i577B1257.versanet.de) aforemny
2025-10-03 05:13:39 +0200aforemny(~aforemny@i59F4C602.versanet.de) (Ping timeout: 250 seconds)
2025-10-03 05:12:01 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-10-03 05:04:11 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-10-03 04:56:21 +0200 <jreicher> I've never quite understood why Erlang has the "single assignment" concept (restriction?) and yet allows side effects in functions. That's almost a contradiction for me.