Newest at the top
| 2026-01-26 02:10:24 +0100 | emmanuelux | (~em@user/emmanuelux) emmanuelux |
| 2026-01-26 02:08:23 +0100 | emmanuelux | (~em@user/emmanuelux) (Quit: bye) |
| 2026-01-26 02:05:27 +0100 | xff0x | (~xff0x@2405:6580:b080:900:41e3:7849:bdcf:b5e1) (Ping timeout: 250 seconds) |
| 2026-01-26 02:02:28 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 252 seconds) |
| 2026-01-26 01:56:16 +0100 | Tuplanolla | (~Tuplanoll@85-156-32-207.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2026-01-26 01:54:50 +0100 | trickard_ | (~trickard@cpe-86-98-47-163.wireline.com.au) |
| 2026-01-26 01:54:38 +0100 | trickard_ | (~trickard@cpe-86-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2026-01-26 01:50:02 +0100 | machinedgod | (~machinedg@d75-159-126-101.abhsia.telus.net) machinedgod |
| 2026-01-26 01:36:49 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 260 seconds) |
| 2026-01-26 01:33:47 +0100 | xff0x | (~xff0x@2405:6580:b080:900:41e3:7849:bdcf:b5e1) |
| 2026-01-26 01:32:48 +0100 | xff0x | (~xff0x@2405:6580:b080:900:572:fd16:77ee:a888) (Ping timeout: 252 seconds) |
| 2026-01-26 01:19:25 +0100 | xff0x | (~xff0x@2405:6580:b080:900:572:fd16:77ee:a888) |
| 2026-01-26 01:18:15 +0100 | xff0x | (~xff0x@2405:6580:b080:900:1b91:f7b5:c35c:b57e) (Ping timeout: 245 seconds) |
| 2026-01-26 01:12:11 +0100 | xff0x | (~xff0x@2405:6580:b080:900:1b91:f7b5:c35c:b57e) |
| 2026-01-26 01:08:15 +0100 | xff0x | (~xff0x@2405:6580:b080:900:3b58:3b23:6c7:a174) (Ping timeout: 245 seconds) |
| 2026-01-26 01:04:49 +0100 | mixfix41 | (~sdeny9ee@user/mixfix41) mixfix41 |
| 2026-01-26 00:44:23 +0100 | trickard_ | (~trickard@cpe-86-98-47-163.wireline.com.au) |
| 2026-01-26 00:44:10 +0100 | trickard_ | (~trickard@cpe-86-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2026-01-26 00:42:48 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 256 seconds) |
| 2026-01-26 00:36:42 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2026-01-26 00:28:35 +0100 | Pozyomka | (~pyon@user/pyon) pyon |
| 2026-01-26 00:20:27 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2026-01-26 00:20:07 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
| 2026-01-26 00:14:35 +0100 | Fijxu | (~Fijxu@user/fijxu) fijxu |
| 2026-01-26 00:13:16 +0100 | Fijxu | (~Fijxu@user/fijxu) (Quit: XD!!) |
| 2026-01-26 00:11:35 +0100 | trickard_ | (~trickard@cpe-86-98-47-163.wireline.com.au) |
| 2026-01-26 00:11:22 +0100 | trickard | (~trickard@cpe-86-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2026-01-26 00:08:29 +0100 | sp1ff` | (~user@2601:1c2:4701:900::32d4) (Remote host closed the connection) |
| 2026-01-26 00:04:34 +0100 | mulk | (~mulk@p5b1128da.dip0.t-ipconnect.de) mulk |
| 2026-01-26 00:02:34 +0100 | mulk | (~mulk@pd95143a6.dip0.t-ipconnect.de) (Ping timeout: 256 seconds) |
| 2026-01-25 23:59:10 +0100 | Square3 | (~Square@user/square) (Ping timeout: 255 seconds) |
| 2026-01-25 23:58:41 +0100 | <EvanR> | oop, everything's an object. FP, everything's a function! |
| 2026-01-25 23:44:26 +0100 | <tomsmeding> | our functions either recurse or traverse |
| 2026-01-25 23:44:23 +0100 | <monochrom> | https://www.slideshare.net/slideshow/fp-patterns-buildstufflt/41936137#13 >:) |
| 2026-01-25 23:43:32 +0100 | <monochrom> | But we are worse than calling everything "recursion" aren't we? We call everything "function". |
| 2026-01-25 23:42:36 +0100 | <monochrom> | Oh yeah all of us should just say "least fixed point" and be done with it! |
| 2026-01-25 23:42:05 +0100 | <monochrom> | (It had to go through a delay. I also had a "part (b)" in which the students had to show what would go wrong in Haskell if there were no delay.) |
| 2026-01-25 23:41:59 +0100 | <tomsmeding> | monochrom: conversely, functional programmers call everything recursion that we have more precise words for :) |
| 2026-01-25 23:41:08 +0100 | <monochrom> | I once posed a homework question that defined infinite streams of Bool to represent timing diagrams of digital circuits, then had students code up a flip flop using a feedback loop. (One more "plain English" word for recursion!) |
| 2026-01-25 23:38:36 +0100 | <monochrom> | People invent all sorts of "plain/simple English" words to avoid saying "recursion". :) |
| 2026-01-25 23:35:27 +0100 | <geekosaur> | plus most other events scheduled other events for later, since it was a population simulator so it was simulating various life events |
| 2026-01-25 23:34:01 +0100 | <EvanR> | in arrow FRP you wouldn't use recursion but ArrowLoop |
| 2026-01-25 23:34:00 +0100 | takuan | (~takuan@d8D86B9E9.access.telenet.be) (Ping timeout: 244 seconds) |
| 2026-01-25 23:33:49 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2026-01-25 23:33:25 +0100 | <EvanR> | e.g. interpreting recursion doesn't necessarily need anything cyclic |
| 2026-01-25 23:33:08 +0100 | <EvanR> | but whether that counts as some sort of cycle, might depend on your concept of the underlying implementation |
| 2026-01-25 23:33:07 +0100 | <geekosaur> | I wasn't using FRP but a PSQ for a simulation, and one of the events was a status report that triggered every so often in simulated time and rescheduled itself for later |
| 2026-01-25 23:32:35 +0100 | <EvanR> | early versions of FRP exploited recursive definitions (why you might be thinking of as cycles?) to implement some sort of state |
| 2026-01-25 23:31:14 +0100 | <tomsmeding> | as I said, I dunno, maybe this is nonsense :) |
| 2026-01-25 23:31:05 +0100 | <tomsmeding> | the update to the time triggers an update to the time again, after a delay? |