(#f57rmoq) @movq That's what I figured, since `ncdu` shows it at the bottom. ;-) But it's actually pretty smart, to be honest. More space for precious content. And the title bar exists anyway, so why not make use of it with something helpful? Also, with entries being in descending order, it's actually natural to show the sum as the even higher number above the largest entry and not at the bottom in another status line widget. 8-)

(#f57rmoq) @lyse Yeah, I was too lazy to introduce a new widget for that (and the current directory), so I just (ab)used the titlebar. %)

(#f57rmoq) @movq Oh nice, it even shows the sum in the title bar.

(#f57rmoq) PMdusage is nearing completion. The table items are clickable now.

(#f57rmoq) @movq Cool, nice progress! :-)

(#f57rmoq) There you go, multithreading. 🥳 I tested this in QEMU, which luckily supports throttling disk I/O, so I can make sure that scanning the disk actually takes a while. (Still boggles my mind a bit. When OS/2 2.x came out, DOS was still the norm for us and I didn’t even know what multithreading was. I really didn’t appreciate this operating system enough back then – only now.)

(#f57rmoq) @movq @prologic The several megabytes of Go binaries always feel so wrong. Hello world is 1.8 MiB, with `-ldflags '-w'` still 1.3 MiB. Growing with each Go release.

(#f57rmoq) @movq I don't mind the binary size. It's a taxed odd between size, portability and feature.

(#f57rmoq) @lyse The magic of dynamic linking (and C). 😅 It has pros and cons, smaller binary size surely is one of the advantages. Go’s huge binary sizes is something that I’ve never gotten used to. 🫤 (Rust *can* be a little better at it, but they’re still very large as well.)

(#f57rmoq) @movq 50 kB executable sizes, nice! I can't even recall when I came across one this small. The good old days.