i wonder in what state is explicit heap oom handling in #rust today. it was still pretty bad year ago.

especially i’m interested what has been already fixed when mirroring against a great #analysis from #crowstrike’s blog.

#rustlang #programming

Taking care of the #finance with #awk :-)

$ awk '!/Payer/ {amount[$1] += $2} END { for (i in amount) print i " " amount[i]}'  2023-08.csv
Jarkko 400
Lotta 515

File format:

$ head -1 2023-08.csv
Payer               Amount              Date                Type

linux-tpmdd pull request for v6.5-rc7: https://lkml.org/lkml/2023/8/11/1305 #linux #kernel #lkml

I always return to #ctags once tried on LSP. E.g. it does not have dependency hell bundled. It always works as expected. Even with LSP I always disable auto-complete, which takes away a lot of its value, assuming that you care about this feature in the first place.

Let's not forget that one of the two #cofounder's of #Gitlab is also #Ukrainian

git grep -l -v "\.ident =" | xargs git grep -l "\.callback =" | xargs git grep -l "\.matches = "

I wanted to find all files, which have DMI table entries with matches and callback set, but not ident. #git #note #linux #kernel

I used #container's and #docker for the first time in my work, and on #riscv #platform. #latebloomer

ugh, #tpm2 #tss #test suite does not allow me to run #integration tests: https://github.com/tpm2-software/tpm2-tss/issues/2677 #linux #kernel #vtpm

Bought an early access #ebook, very exciting! #fpga #nostarch @nostarch

I’ve became by accident pretty seasoned with cmake. Never wanted to learn it particularly but it is not too bad. I use it at work.

I like at least these two features of cmake:

• C_STANDARD and CXX_STANDARD
• configure_file

I also like that it is focused on C/C++ rather than trying to be everything, which is really a fresh breath of air these days. I rather use it at least than autotools :-)

#cmake #kitware

#embed is a welcome addition to #C, as using incbin has added a lot of unwanted boilerplate. #C23 #ISO #standard

four #hardware #loopback's is pretty amazing. afaik #rme uses #fpga in #babyface to manage the total 24 channels. #audio

Rest in peace Bram Moolenaar. I've been a #vim user since 1998. https://groups.google.com/g/vim_announce/c/tWahca9zkt4?pli=1

it would be a nice to have a #git #diff #option that would #pretty #format patched #patch files.

apparently folder’s can be cycled in #aerc with the cursor keys when the capslock is turned on. holding shift was getting painful to say the least. #email #shortcut

I wonder how to pick Message-ID from #email in #aerc, in order to pipe it to #b4. #rfc2822

i use #evolution to delete #email duplicates because i have no idea how to do it in #aerc.

reminder to myself. in order to plumb #kernel #config file for a particular #buildroot build:

make linux-patch
# edit output/build/<linux directory>/.config
make # continue with the build

#linux

ordered a new sound card, can't wait: https://www.rme-audio.de/babyface-pro-fs.html

#rme #audio #babyface #musicproduction

code generation with AI. i do not get it and it has enormous legal risks for commercial use. i’d wait at least to wait for precedent legal cases before seriously using it.

also even when manually written code paths, which in some level address the functionality in a an software package, it will take about 5-10% of the overall project time. 90-95% of the time goes into QA and finding out ways of fitting the implementation to the constraints defined by all sorts of non-functional issues.

that’s why case tools never succeeded, and that’s why i’m skeptical of the whole idea of AI code generation. there’s always someone offering a magic wand to write the code for you but it never works - at least if you aim for the highest possible quality, i.e. aim for offering more value for customers than your competitors.