2026/03/16

Newest at the top

2026-03-16 20:44:09 +0100emmanuelux(~em@user/emmanuelux) (Ping timeout: 248 seconds)
2026-03-16 20:43:30 +0100emmanuelux_(~em@2a02-8440-260d-61f7-ac71-fff7-5c29-395c.rev.sfr.net)
2026-03-16 20:39:48 +0100madresch(~Thunderbi@user/madresch) madresch
2026-03-16 20:34:37 +0100emmanuelux(~em@user/emmanuelux) emmanuelux
2026-03-16 20:34:06 +0100emmanuelux(~em@user/emmanuelux) (Ping timeout: 246 seconds)
2026-03-16 20:32:20 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-03-16 20:25:36 +0100malte(~malte@mal.tc) malte
2026-03-16 20:19:45 +0100arandombit(~arandombi@user/arandombit) (Ping timeout: 246 seconds)
2026-03-16 20:19:36 +0100peterbecich(~Thunderbi@71.84.33.135) (Ping timeout: 264 seconds)
2026-03-16 20:15:16 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2026-03-16 20:13:38 +0100lisbeths(uid135845@id-135845.lymington.irccloud.com) (Quit: Connection closed for inactivity)
2026-03-16 20:08:28 +0100 <EvanR> e.g. you might sabotage yourself second guessing whether the more narrow and defined objective is appropriate for the problem
2026-03-16 20:07:15 +0100 <EvanR> when you assert during the design process that what we're creating is not a random arrangement of machine code instructions to munge the computer words to and fro, but (exact or approximate in some sense) realization of some semantics, this latter objective is much more narrow and focused. And not everyone has the guts (or foolhardiness?) to try!
2026-03-16 20:01:54 +0100 <mesaoptimizer> what is a semantic ball
2026-03-16 20:01:49 +0100Square2(~Square@user/square) Square
2026-03-16 19:54:23 +0100peterbecich(~Thunderbi@71.84.33.135) peterbecich
2026-03-16 19:52:18 +0100target_i(~target_i@user/target-i/x-6023099) target_i
2026-03-16 19:51:05 +0100sord937(~sord937@gateway/tor-sasl/sord937) (Quit: sord937)
2026-03-16 19:50:48 +0100machinedgod(~machinedg@d172-219-48-230.abhsia.telus.net) (Ping timeout: 264 seconds)
2026-03-16 19:42:28 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-03-16 19:33:32 +0100 <monochrom> Just fill your type holes with semantics balls >:)
2026-03-16 19:32:44 +0100 <L29Ah> only type holes?
2026-03-16 19:28:14 +0100somemathguy(~somemathg@user/somemathguy) somemathguy
2026-03-16 19:26:09 +0100gabiruh(~gabiruh@vps19177.publiccloud.com.br) gabiruh
2026-03-16 19:25:40 +0100gabiruh(~gabiruh@vps19177.publiccloud.com.br) (Quit: ZNC 1.7.5 - https://znc.in)
2026-03-16 19:22:24 +0100 <EvanR> no semantic balls
2026-03-16 19:21:42 +0100 <EvanR> that is what happens when people think what's the big deal it's all 1s and 0s
2026-03-16 19:18:35 +0100arandombit(~arandombi@user/arandombit) arandombit
2026-03-16 19:18:35 +0100arandombit(~arandombi@2a02:2455:8656:7100:85dd:2465:f8d7:ee0a) (Changing host)
2026-03-16 19:18:35 +0100arandombit(~arandombi@2a02:2455:8656:7100:85dd:2465:f8d7:ee0a)
2026-03-16 19:05:44 +0100arandombit(~arandombi@user/arandombit) (Ping timeout: 244 seconds)
2026-03-16 18:53:21 +0100arandombit(~arandombi@user/arandombit) arandombit
2026-03-16 18:38:25 +0100arandombit(~arandombi@user/arandombit) (Ping timeout: 268 seconds)
2026-03-16 18:17:46 +0100 <mesaoptimizer> well, by a lot of people you mean
2026-03-16 18:13:31 +0100dyniec(~dyniec@dybiec.info) dyniec
2026-03-16 18:12:54 +0100dyniec(~dyniec@dybiec.info) (Remote host closed the connection)
2026-03-16 18:11:50 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 245 seconds)
2026-03-16 18:03:25 +0100st_aldini(~Betterbir@136.48.46.187) st_aldini
2026-03-16 17:59:50 +0100 <[exa]> it's tested by time
2026-03-16 17:57:52 +0100 <haskellbridge> <magic_rb> Sounds like great software ngl
2026-03-16 17:57:47 +0100 <dminuoso> Or maybe "recursion" is the wrong term here, reentrance seems more fitting.
2026-03-16 17:56:51 +0100 <dminuoso> less bugged"
2026-03-16 17:56:49 +0100 <dminuoso> While we protect recursion in our thunks with blackhole, django.conf.settings not only allows it, but of course you end up with at scenario where not only can a recursive evaluation end up with a different value, but because they mutate state you end up with scenarios where depending on the order of evaluation you have three possible states that range from "bugged, bugged and buggy, and slightly
2026-03-16 17:56:33 +0100Guest62t(~Guest62t@p200300ca8f03bb00982801fe38106b84.dip0.t-ipconnect.de)
2026-03-16 17:55:39 +0100 <dminuoso> django.conf.settings is an attempt at lazyness, but done in a grotesque and buggy way
2026-03-16 17:55:22 +0100 <dminuoso> Python strikes again.
2026-03-16 17:54:59 +0100danza(~danza@user/danza) (Remote host closed the connection)
2026-03-16 17:50:13 +0100craunts795335385(~craunts@152.32.99.2) (Quit: The Lounge - https://thelounge.chat)
2026-03-16 17:50:05 +0100euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2026-03-16 17:44:05 +0100madresch(~Thunderbi@user/madresch) (Ping timeout: 244 seconds)