2026/04/09

Newest at the top

2026-04-09 20:40:02 +0000arandombit(~arandombi@user/arandombit) arandombit
2026-04-09 20:40:02 +0000arandombit(~arandombi@2a02:2455:8656:7100:5d3a:927c:20e1:5d86) (Changing host)
2026-04-09 20:40:02 +0000arandombit(~arandombi@2a02:2455:8656:7100:5d3a:927c:20e1:5d86)
2026-04-09 20:34:01 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds)
2026-04-09 20:29:19 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-09 20:26:23 +0000comonad(~comonad@2003:d0:2701:9d00:9435:23f:d7f3:6a1f)
2026-04-09 20:25:11 +0000comonad(~comonad@p200300d02717df00adc247ef70bd7367.dip0.t-ipconnect.de) (Ping timeout: 272 seconds)
2026-04-09 20:18:26 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2026-04-09 20:13:56 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-04-09 20:11:10 +0000weary-traveler(~user@user/user363627) user363627
2026-04-09 20:06:27 +0000uli-fem(~uli-fem@115.128.112.118) (Ping timeout: 255 seconds)
2026-04-09 20:05:25 +0000 <acarrico> I guess we are off topic.
2026-04-09 20:05:23 +0000 <monochrom> Yeah I keep it simple.
2026-04-09 20:05:13 +0000 <acarrico> monochrom: make is the way to go, but you gotta keep it simple. Zig added a build system and then suddenly I couldn't program in Zig anymore.
2026-04-09 20:03:44 +0000 <monochrom> Once upon a time when that Ant thing for Java just came out, I took a look with high hope. Nope, it's more redundant than makefiles. I went back to makefiles.
2026-04-09 20:02:58 +0000merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2026-04-09 20:02:37 +0000 <monochrom> The only burning from Make I have got so far is just that it doesn't do well with filenames that contain spaces.
2026-04-09 20:01:59 +0000 <EvanR> make is life
2026-04-09 20:01:47 +0000 <monochrom> "call me by your name" should inspire a joke language for the next April 1. :)
2026-04-09 20:01:27 +0000 <acarrico> Nobody has been spoiled by make, only burned.
2026-04-09 20:01:07 +0000 <monochrom> <--- spoiled by GNU Make
2026-04-09 20:00:57 +0000 <mauke> call me by your name
2026-04-09 20:00:46 +0000 <monochrom> Whereas POSIX Make, I know nothing. :)
2026-04-09 20:00:39 +0000 <tomsmeding> where N = name
2026-04-09 20:00:36 +0000Guest3956(~puke@user/puke) (Ping timeout: 250 seconds)
2026-04-09 20:00:26 +0000 <tomsmeding> := is CBV, = is CBN I guess yes
2026-04-09 20:00:11 +0000 <tomsmeding> oh right, Make has mutation in there too, I forgot
2026-04-09 20:00:04 +0000wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2026-04-09 19:59:45 +0000 <monochrom> I think GNU Make has "v = ..." vs "v := ..." for by-name vs by-value, I forgot which is which.
2026-04-09 19:59:32 +0000 <tomsmeding> fun
2026-04-09 19:59:28 +0000 <acarrico> Correct, think about it with interning and memoization!
2026-04-09 19:59:13 +0000 <tomsmeding> acarrico: as in, if you'd literally write `(4 + 4) + (4 + 4)`, only two additions would get executed?
2026-04-09 19:59:07 +0000 <acarrico> mauke: In Makefiles maybe there are two ways to expand shell variables.
2026-04-09 19:58:17 +0000 <tomsmeding> mauke: fair
2026-04-09 19:58:10 +0000 <acarrico> yes because it is simple, but also it is super lazy, since thunks only replace values in certain known locations, but memozition replaces them everywhere, so (4 + 4) + (4 + 4) is more lazy than by need.
2026-04-09 19:58:07 +0000 <mauke> no, shell variables are eager
2026-04-09 19:58:03 +0000uli-fem(~uli-fem@115.128.112.118)
2026-04-09 19:58:02 +0000 <tomsmeding> which is I guess technically true, but string concatenation is not really a programming language in my mind :p
2026-04-09 19:58:00 +0000pyookpuke
2026-04-09 19:58:00 +0000pukeGuest3956
2026-04-09 19:58:00 +0000pyook(~puke@user/puke) puke
2026-04-09 19:57:41 +0000 <tomsmeding> if you call that call-by-name, then shell variables are too, as is string interpolation in any language
2026-04-09 19:57:05 +0000 <mauke> hey, aren't make variables just call-by-name (without the 'call' part)?
2026-04-09 19:56:37 +0000 <tomsmeding> it's cute
2026-04-09 19:56:35 +0000Lord_of_Life_Lord_of_Life
2026-04-09 19:56:35 +0000 <acarrico> memoisation + interning
2026-04-09 19:56:34 +0000 <tomsmeding> right, this is an approach I hadn't thought of yet
2026-04-09 19:56:24 +0000 <acarrico> correct.
2026-04-09 19:56:16 +0000 <acarrico> I've been toying with using it in a macro system the same way.
2026-04-09 19:56:15 +0000 <tomsmeding> presumably :p