Newest at the top
| 2026-05-17 21:02:01 +0000 | Eoco | (~ian@128.101.131.218) (Ping timeout: 244 seconds) |
| 2026-05-17 21:01:12 +0000 | <EvanR> | lately I've been applying probability to everything: the size of this integer is exponentially decaying so picking int64 instead of arbitrary precision gives a high chance the program works! |
| 2026-05-17 21:01:06 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) (Ping timeout: 248 seconds) |
| 2026-05-17 21:00:26 +0000 | petrichor | (~jez@user/petrichor) petrichor |
| 2026-05-17 20:59:53 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-05-17 20:59:38 +0000 | <EvanR> | answer: probably xD |
| 2026-05-17 20:58:51 +0000 | <EvanR> | yes that's also the "issue" with information theory, is probability appropriate in the first place |
| 2026-05-17 20:58:17 +0000 | <tomsmeding> | the issue with most practical nondeterminism is that it's not probabilistic but instead other components of the system, that are relevant to your model, doing stuff |
| 2026-05-17 20:57:51 +0000 | <tomsmeding> | I mean, sure, if all nondeterminm comes from probabilistic events, then the output is also probabilistic |
| 2026-05-17 20:57:37 +0000 | <EvanR> | then the book works for deterministic and non |
| 2026-05-17 20:57:33 +0000 | Eoco | (~ian@128.101.131.218) Eoco |
| 2026-05-17 20:56:52 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) |
| 2026-05-17 20:56:42 +0000 | <EvanR> | in this book on cybernetics, they sweep it all under the rug quite easily: determinism means the transition function for the system is single valued. And if it's not single valued e.g. modelling a general quantum measurement, then replace the whole thing with a probability distribution and it's single valued again (the distribution) |
| 2026-05-17 20:56:02 +0000 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2026-05-17 20:54:23 +0000 | <tomsmeding> | s/.$// |
| 2026-05-17 20:54:20 +0000 | <tomsmeding> | so pure concurrency is not really a thingt |
| 2026-05-17 20:54:13 +0000 | <tomsmeding> | purity implies determinism |
| 2026-05-17 20:54:04 +0000 | <tomsmeding> | I have recently been enlightened that the essence of concurrency is nondeterministic execution order |
| 2026-05-17 20:53:47 +0000 | <EvanR> | faithful to some semantics of concurrency, whatever word this is |
| 2026-05-17 20:53:30 +0000 | <EvanR> | I'm not sure purity is the right word if you want to make the concurrency pure (where is the pure function) |
| 2026-05-17 20:53:23 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-17 20:52:54 +0000 | layline_ | (~layline@149.154.26.39) layline |
| 2026-05-17 20:52:37 +0000 | Eoco | (~ian@128.101.131.218) (Ping timeout: 265 seconds) |
| 2026-05-17 20:52:25 +0000 | random-jellyfish | (~random-je@user/random-jellyfish) (Ping timeout: 248 seconds) |
| 2026-05-17 20:52:01 +0000 | <EvanR> | STM is cool because it is concurrency and no I/O |
| 2026-05-17 20:47:47 +0000 | jreicher | (~joelr@user/jreicher) (Quit: In transit) |
| 2026-05-17 20:45:34 +0000 | <tomsmeding> | I was going to ask, how do you do purity and I/O and concurrency, but I guess concurrency is IO and not I/O |
| 2026-05-17 20:45:20 +0000 | sp1ff | (~user@2601:1c2:4080:14c0::6eb4) (Read error: Connection reset by peer) |
| 2026-05-17 20:45:03 +0000 | <EvanR> | this is how all the esolangs can get away with purity and do anything (can only consume 1 char from stdio and output 1 char, at a time, is the extent of their I/O) |
| 2026-05-17 20:44:18 +0000 | <EvanR> | I/O specifically (not everything that was dumped onto the IO monad) is easily made compatible with purity! |
| 2026-05-17 20:44:08 +0000 | Eoco | (~ian@128.101.131.218) Eoco |
| 2026-05-17 20:41:45 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) (Ping timeout: 246 seconds) |
| 2026-05-17 20:40:23 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2026-05-17 20:36:32 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) |
| 2026-05-17 20:35:19 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-17 20:35:02 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) (Ping timeout: 244 seconds) |
| 2026-05-17 20:34:45 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-05-17 20:30:53 +0000 | Eoco | (~ian@128.101.131.218) (Ping timeout: 272 seconds) |
| 2026-05-17 20:30:43 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) |
| 2026-05-17 20:30:31 +0000 | x9 | (~x9@91-157-105-12.elisa-laajakaista.fi) |
| 2026-05-17 20:30:19 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-17 20:26:09 +0000 | Eoco | (~ian@128.101.131.218) Eoco |
| 2026-05-17 20:18:49 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds) |
| 2026-05-17 20:17:42 +0000 | Eoco | (~ian@128.101.131.218) (Ping timeout: 255 seconds) |
| 2026-05-17 20:16:52 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) (Ping timeout: 276 seconds) |
| 2026-05-17 20:14:03 +0000 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-05-17 20:13:32 +0000 | Eoco | (~ian@128.101.131.218) Eoco |
| 2026-05-17 20:11:15 +0000 | tri | (~tri@ool-4a5ac1f4.dyn.optonline.net) |
| 2026-05-17 20:09:43 +0000 | Inline | (~noOne@ipservice-092-208-182-236.092.208.pools.vodafone-ip.de) (Quit: KVIrc 5.2.8 Quasar http://www.kvirc.net/) |
| 2026-05-17 20:08:22 +0000 | tjbc | (~tjbc@user/fliife) fliife |