Newest at the top
| 2025-12-01 03:34:12 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-01 03:32:01 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2025-12-01 03:31:54 +0100 | Googulator91 | Googulator |
| 2025-12-01 03:28:48 +0100 | tuxpaint | (~a@put.gay) (Read error: Connection reset by peer) |
| 2025-12-01 03:28:40 +0100 | Pozyomka | (~pyon@user/pyon) pyon |
| 2025-12-01 03:28:10 +0100 | firesquidwao | (~a@2600:3c06::f03c:93ff:fea6:ef0e) |
| 2025-12-01 03:27:55 +0100 | jrm | (~jrm@user/jrm) jrm |
| 2025-12-01 03:27:41 +0100 | jrm | (~jrm@user/jrm) (Read error: Connection reset by peer) |
| 2025-12-01 03:27:28 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Excess Flood) |
| 2025-12-01 03:26:33 +0100 | ChanServ | +v haskellbridge |
| 2025-12-01 03:26:33 +0100 | haskellbridge | (~hackager@96.28.224.214) hackager |
| 2025-12-01 03:25:57 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2025-12-01 03:25:35 +0100 | haskellbridge | (~hackager@96.28.224.214) (Ping timeout: 240 seconds) |
| 2025-12-01 03:24:55 +0100 | <EvanR> | what is the program |
| 2025-12-01 03:22:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-01 03:21:46 +0100 | <Guest62> | okay, I was able to learn heap profiling, but my graphs seem empty.... |
| 2025-12-01 03:21:07 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Remote host closed the connection) |
| 2025-12-01 03:18:49 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-01 03:08:24 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-12-01 03:03:26 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-01 03:02:03 +0100 | wickedjargon | (~user@64.114.24.74) (Remote host closed the connection) |
| 2025-12-01 03:01:47 +0100 | wickedjargon | (~user@64.114.24.74) |
| 2025-12-01 03:01:33 +0100 | <jreicher> | DRAM's pretty crazy too actually. As funky as flip-flops are, they are probably the most straightforward of all the techs. |
| 2025-12-01 03:01:22 +0100 | monochrom | is an echo relay memory and a large language model. |
| 2025-12-01 03:01:13 +0100 | <EvanR> | this would be like, read the poem aloud really loud in the grand canyon, then wait |
| 2025-12-01 03:01:11 +0100 | iqubic | (~sophia@2601:602:9203:1660:c137:59bd:3f5b:b4a7) iqubic |
| 2025-12-01 03:00:45 +0100 | <monochrom> | I mean, I worked like that when I was a child, too. Whenever required to memorize a story or a poem, I read aloud and listened to myself, repeat. |
| 2025-12-01 02:59:00 +0100 | iqubic | (~sophia@2601:602:9203:1660:c137:59bd:3f5b:b4a7) (Remote host closed the connection) |
| 2025-12-01 02:58:55 +0100 | peterbecich | (~Thunderbi@172.222.148.214) (Ping timeout: 240 seconds) |
| 2025-12-01 02:58:45 +0100 | <jreicher> | monochrom: delay line memory was always my favourite. |
| 2025-12-01 02:58:11 +0100 | <Guest62> | uh yes. I think I need heap profiling. I think my primary question is "Does the total memory allocated section count reuse of memory as a separate additional allocation?" and how to not make it do that if it does. |
| 2025-12-01 02:58:01 +0100 | catties | Catty |
| 2025-12-01 02:55:44 +0100 | <glguy> | Have you seen this already? https://ghc.gitlab.haskell.org/ghc/doc/users_guide/profiling.html |
| 2025-12-01 02:55:01 +0100 | <Guest62> | I'm profiling my haskell functions (pitting them against each other to compare their memory usages). Could someone help me understand how profiling works? I have basically never done this before. |
| 2025-12-01 02:54:18 +0100 | Guest62 | (~Guest62@38.49.92.193) |
| 2025-12-01 02:53:45 +0100 | Pozyomka | (~pyon@user/pyon) (Read error: Connection reset by peer) |
| 2025-12-01 02:52:03 +0100 | <monochrom> | I hadn't thought of it that way until I read both a Turing biography (so there was his team using CRTs and mercury tubes for early computers) and Harper's PFPL in which he pointed out "state comes from self-reference" and exemplified with using recursion to make an RS latch. |
| 2025-12-01 02:51:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-12-01 02:50:25 +0100 | jmcantrell_ | (~weechat@user/jmcantrell) (Ping timeout: 264 seconds) |
| 2025-12-01 02:45:24 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-12-01 02:45:08 +0100 | <monochrom> | (More precisely, there must also be a non-zero time delay between sending output and reading back input. Today, you use logic gates to make flip flops, same difference.) |
| 2025-12-01 02:43:59 +0100 | <monochrom> | (The two popular choices were mercury tube and CRT.) |
| 2025-12-01 02:43:30 +0100 | <monochrom> | (In general, any output device combined with a sensor could be memory: To store 1, output 1 and have the sensor read back that 1, repeat.) |
| 2025-12-01 02:43:30 +0100 | <glguy> | HE SAID: "THE MOST BONKERS WAS WHEN... |
| 2025-12-01 02:43:03 +0100 | <haskellbridge> | <iqubic (she/her)> WHAT?!?!?! |
| 2025-12-01 02:41:59 +0100 | <monochrom> | The most bonkers was when CRT was memory rather than display. >:) |
| 2025-12-01 02:35:55 +0100 | <geekosaur> | degaussing my monitor every month was fun |
| 2025-12-01 02:35:44 +0100 | <geekosaur> | some of us were still using them in the early 2000s |
| 2025-12-01 02:34:26 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-12-01 02:30:30 +0100 | jmcantrell_ | (~weechat@user/jmcantrell) jmcantrell |