#zig
Weeknotes for 2025, week 32: https://denisdefreyne.com/weeknotes/2025-w32/
Small code dump: a utility to forward any Bluetooth controller from one Linux box to another Linux box:
Memory management in #zig is an absolute disaster. You need to pull in a specific allocator after which you need to instantiate it, then call it. The same with releasing memory, if the allocator isn't in scope.
https://pedropark99.github.io/zig-book/Chapters/01-memory.html#sec-allocators
Whatever happened to simple things in programming. Allocating a block of memory is such a vital thing, it should be extremely compact and efficient to write. [1/2]
@ellisgl
1) would be functional
2) would compile to machine code
3) would come with decent dependency management (see #golang or #zig)
4) would have manual memory management with tool assistance to make it safe-ish
5) would use tabs for indentation (as an 8 space guy, I do actually care because I don't want to inflict this on others)
But since my brain is merely about average, this will likely remain a pipe dream.
Sharing this quite basic Bencode library in Guile:
https://github.com/4zv4l/guile-bencode
I am making this in case I decide myself to write a BitTorrent cli/daemon in Guile (one that could easily be used with Guix/Shepherd).
I originally wanted to write one in Zig but since it's going under heavy change, I could do a first try with Guile.
I looked at the Zig programming language this afternoon. None of the two different "hello world" snippets on their site compiled. These are old snippets and the language has evolved since. But their website never got updated. So, yeah. First impressions matter.
