After a bug in the Open Watcom OS/2 resource compiler has been fixed (imagine that – they still fix bugs related to OS/2! 🤯💚), I was able to make some more progress with the OS/2 GUI version of my little disk usage tool. It now has a menu bar and a dialog to open another directory: The video includes the ZMODEM transfer process of the 50 kB `.EXE` file from my laptop. It’s a bit lengthy, but I kept it in for nostalgia. 😅 Next up is probably multithreading: Do the disk scanning in a background thread so the UI doesn’t freeze. (This is running on a Compact Flash card, a real hard disk would be much slower.)

(#f57rmoq) And, of course, at some point the directory items should be clickable, so you can navigate the tree as usual. That’s much less interesting than delving into threading, though. 😅

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

…#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. …

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

(#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) 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 min…

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

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

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