IRC channel logs
2024-04-08.log
back to list of logs
<sneek>I've been aware for 25 seconds <sneek>This system has been up 3 weeks, 5 days, 23 hours, 2 minutes <grtcdr>Hey y'all, I very recently used Haunt to build a website for a personal project. If David is receiving requests to for his https://awesome.haunt.page/ list then I'd love to submit mine :-) <grtcdr>I was talking about contributing my own, recently published, website that I'd built with Haunt to https://awesome.haunt.page. Let me know if you're accepting new additions to that list :) <dthompson>send filip a patch, I'm sure they'll be happy to add you to the list :) <ArneBab>janneke: my experience with build systems is that once I stray from exactly the path they expect, every other build system is worse than autotools. <ArneBab>After being fascinated with build systems and trying many, I went full circle and now only use autotools for my own projects. <dthompson>autotools is simultaneously horrible and somehow still better than everything else <dthompson>something that takes the good parts of autotools, uses a sane language, and figures out how to avoid generating spaghetti code shell scripts could maybe change things... but also existing build systems are so entrenched that I don't know if something good could even catch on at this point. <cbaines>any tips on what can cause Guile to run different code to that which you're editing? <cbaines>e.g. writing some scheme, not going great but adding debugging output <cbaines>then Guile just seems to be running different/old code, not what's in the file currently, but what was? <civodul>it could be ignoring your .scm because it found a .go file that appears to be newer <cbaines>I think that might have been the issue, although it seems like this was across modules <cbaines>as deleting a .go file for module A affected behavior of a procedure exported by module B <rlb>cbaines: iirc the lookup algorithm isn't currently the one (I think) I would want -- if that was your issue, I've hit something similar. Something like if the preferred file is a newer .scm, it'll try to compile, and if the compilation fails, it'll go with a stale .go, rather than (as I'd prefer) just failing. <janneke>ArneBab: yeah, fully agree, i also went full circle <freakingpenguin>dthompson: Mind expanding on why other build systems are worse than autotools? <freakingpenguin>I've only really used the gnu toolchain and some language-specific ones (e.g. bundler, cargo) myself <dthompson>ArneBab's comment before my messages sum up my feelings. just feels like every other build system isn't as expressive or accomodating of edge cases/unusual needs. <dthompson>I've also done my fair share of guix packaging and every other build system adds complications to the packaging process. <dthompson>the assumptions those systems make stand out like a sore thumb in the guix build environment. <dsmith>Well, that was entertaining. (eclipse) <civodul>peval leaves (null? (list 1 2)) unchanged <civodul>(convervative one could have thought, since โlistโ allocates)