Newest at the top
| 2026-02-05 01:07:26 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-05 00:56:40 +0100 | <haskellbridge> | <loonycyborg> dense that is |
| 2026-02-05 00:56:28 +0100 | <haskellbridge> | <loonycyborg> maybe even just above average thermal fluctuation, given how small chips are now |
| 2026-02-05 00:56:17 +0100 | <EvanR> | https://esolangs.org/wiki/Entropy |
| 2026-02-05 00:56:03 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
| 2026-02-05 00:54:54 +0100 | <EvanR> | space radiation over here, the material your chip is made of has a % of radioactive material in it, ... |
| 2026-02-05 00:54:27 +0100 | <haskellbridge> | <loonycyborg> and probably many other sources of bad things that could happem.. |
| 2026-02-05 00:54:24 +0100 | <EvanR> | I need to find this page by superkuh, which lists all the reasons the bits could flip |
| 2026-02-05 00:54:01 +0100 | <haskellbridge> | <loonycyborg> but there's some possibility that space radiation could flip a bit in any chip |
| 2026-02-05 00:54:00 +0100 | <haskellbridge> | <loonycyborg> I remember random flips from alpha particles were actual problem for some ram chips |
| 2026-02-05 00:53:38 +0100 | qqq | (~qqq@185.54.21.178) |
| 2026-02-05 00:53:23 +0100 | <EvanR> | instead of assuming we have this luxurious ideal computer |
| 2026-02-05 00:53:20 +0100 | <lantti> | oh, sorry I didn't read back far enough |
| 2026-02-05 00:52:57 +0100 | <EvanR> | where code is deterioriating around you, and it's up to the programmer to somehow deal with it |
| 2026-02-05 00:52:55 +0100 | <jreicher> | I wish my workplace tested with chaosmonkey |
| 2026-02-05 00:52:43 +0100 | <EvanR> | that's the esolang I was talking about |
| 2026-02-05 00:52:39 +0100 | <lantti> | if it is not then the programmer must take that into consideration and have reduncancy and whatnot |
| 2026-02-05 00:51:48 +0100 | <lantti> | isn't it still a programmers decision if it is acceptable that such malfunctions cause a program to fail (considering severity and probability etc.)? |
| 2026-02-05 00:50:38 +0100 | <EvanR> | not just faulty ram, unless it's by definition, even space grade chips will be giving a rating in terms of probability |
| 2026-02-05 00:49:23 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-05 00:44:07 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 264 seconds) |
| 2026-02-05 00:41:26 +0100 | <haskellbridge> | <loonycyborg> good luck figuring out what is because of such a malfunction and what comes from programmer brainfarts :P |
| 2026-02-05 00:40:50 +0100 | <haskellbridge> | <loonycyborg> There still are actual malfunctions out there, like faulty ram modules that flip some bits. |
| 2026-02-05 00:38:15 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2026-02-05 00:33:40 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-05 00:28:55 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 240 seconds) |
| 2026-02-05 00:24:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2026-02-05 00:24:13 +0100 | paddymahoney | (~paddymaho@pool-99-250-10-137.cpe.net.cable.rogers.com) |
| 2026-02-05 00:19:53 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-05 00:18:37 +0100 | paddymahoney | (~paddymaho@pool-99-250-10-137.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2026-02-05 00:15:24 +0100 | mange | (~mange@user/mange) mange |
| 2026-02-05 00:08:56 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2026-02-05 00:04:09 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-05 00:01:34 +0100 | tromp | (~textual@2001:1c00:3487:1b00:10a6:5d4a:b26:4065) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2026-02-04 23:56:22 +0100 | xff0x | (~xff0x@2405:6580:b080:900:d171:1c19:51a5:d6b5) |
| 2026-02-04 23:54:03 +0100 | skum | (~skum@user/skum) skum |
| 2026-02-04 23:52:55 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2026-02-04 23:48:48 +0100 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2026-02-04 23:48:18 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-02-04 23:46:29 +0100 | <EvanR> | this code is provided without any warranty or even an implied warranty of merchantability or fitness for a particular purpose! |
| 2026-02-04 23:45:54 +0100 | skum | (~skum@user/skum) (Quit: WeeChat 4.8.1) |
| 2026-02-04 23:43:37 +0100 | <jreicher> | Yeah, this is specific to "bugs" |
| 2026-02-04 23:43:16 +0100 | <EvanR> | at a much slower pace |
| 2026-02-04 23:42:45 +0100 | <EvanR> | one of these esolangs has your code devolving as it runs, due to "entropy"... annoying until you accept this is happening to your real computer all the time xD |
| 2026-02-04 23:41:15 +0100 | <EvanR> | (except for surface level consumer hardware does experience random errors for reasons... though that's just another instance of the same point) |
| 2026-02-04 23:39:48 +0100 | <jreicher> | EvanR: I know you're joking, but in all seriousness I "lecture" to every non-techy I meet that when a bug hits it's not a computer malfunction. The computer did exactly what it was told to do. It's the developers who malfunctioned. |
| 2026-02-04 23:37:22 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-02-04 23:35:36 +0100 | <EvanR> | technology, industrialization absolving people of accountability |
| 2026-02-04 23:34:49 +0100 | <EvanR> | jreicher, sure... blame the computer! |
| 2026-02-04 23:32:45 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |