I'm amused that the author rants about the importance of being able to easily analyze code and then wants to produce (presumably) a different binary per language to analyze all over.
Their commit messages are also rather colorful. This is an interesting project, but seemingly not someone I'd enjoy working with.
Looks like it; the author also says he sticks to certain paradigms like an indentation style I've not seen in the wild before and making as many things as possible 'const'.
I don't mind, I can respect people having Strong Opinions, it's an improvement over having too weak opinions which lead to inconsistencies in a codebase.
I'm guilty of the const / final thing... it really does help in the language I use for work all the time, but that's because its compiler and analyzer are built around using those hints to do static analysis in my editor.
fwiw, we went from in-memory to sqlite and had massive performance gains for a language model trie we were working with in an app. Best part: cross-platform! I just find this so odd, the gall of the forker who literally started with someone else's code then, after asking about a collab, told them "sorry, I think better." So weird. Ah well, 7 years old, I'm sure they've both gotten over it.
Old SpaceMonger[0] and now SpaceSniffer[1] present a much better visualization of folders while also letting you adjust the granularity of how deep you want to see through.
The subdivision algorithm and display style are intended to mimic the old version of spacemonger. For whatever reason, that was always my favorite way of visualizing disk space, and I wanted to use something similar on Linux.
I wanted to replace the Tk renderer with an SVG one using SMIL [1],but got discouraged when I learned it was deprecated. Looking it up just now, I see that the deprecation is apparently suspended, so maybe I'll get around to that after all...
I'm a big fan of the original project, so I'm curious what the changes amount to. (It claims there are performance improvements, but nothing detailed.)
Voidtool's Everything is one of those things I pretty much can't use a PC without. It's just stunningly useful and performant. MSFT's file search is so slow in comparison it feels almost like a malicious prank.
The "date" column and sort order in Explorer is a "deep state metadata inspection" kind of deal. For ordinary files this makes no difference, it's the same as Date modified, but sorting by date in a folder full of media files generally ends badly and in any case takes a long, long time until Explorer has parsed every last one of them. Explorer also seems to be rather unable to cache the results of this operation.
Pretty sure they said it's because it doesn't support permissions, so you could see anything on your hard drive, that's why they don't support it and do indexing instead
The operating system doesn't need permissions to see anything on your hard drive and it is the operating system that is enforcing the permissions so it can filter the results afterwards. Also, an index can be stale and show files whose permissions have changed that you shouldn't be able to see so the permissions have to be checked on the search results either way.
It and WinDirStat are some of the first things I install on any new instance of a computer. But I may check out this fork and Whiztree for other inspiration.
Disk Inventory X has been a little hit or miss for me. Works OK on my two Macs (Catalina), but can’t index the whole (128GB?) drive on my wife’s MacBook Air (Mojave). Just crashes at some point.
I've also been using WizTree for quite a while, but recently learned WinDirStat scans the filesystem instead of trusting the NTFS metadata because it can sometimes be incorrect(?) and is a bit tricky due to poor documentation.
The WDS developer actually addressed this in AWDS's issues 4[1] and 19[2] a few years ago, and even said he's contemplating supporting the MFT but it seems he hasn't gotten around to it.
GNOME comes with a useful utility which does that as well called Disk Usage Analyser. Usually installed by default via the gnome package on many distros.
DaisyDisk is very polished and nice, but I'd like to add GrandPerspective [1] to the discussion - it's not as pretty, but it's free and does a very good job as well.
If you don't mind spending $9.99, DaisyDisk is definitely worth it, though.
GrandPerspective is a quite delightful disk space visualizer, and was the app I used to replace the delightful workhorse 'Disk Inventory X'[0] since Disk Inventory X was infrequently updated and would routinely become incompatible on new OS X versions (this was almost 10 years ago).
I've never liked this nested pie chart style. I don't understand the purpose of a disk space visualizer where the area of an element on the screen doesn't really represent relative file size.
The homepage and download page haven't been updated, but I can confirm that Disk Inventory X works just fine for me in MacOS Monterey (12.3, Intel machine)
WinDirStat was a clone of KDirStat (KDE3-era); today there is Filelight. There's a Gnomeclone of it, but it's quite a lot worse (The sunburst only has only or two levels, which cannot be adjusted, and you can't have anything other than a 50:50 split).
I guess is this the subthread where we list other disk space analyzer tools.
I've been using TreeSize Free/Pro on Windows since as long as I can remember. Solid program, nice "old school" interface that I really enjoy using. Not open source, but worth paying for.
The only one that worked well for me on Windows is SpaceSniffer. It correctly treated symlinks and junctions (most tools duplicate those) and alternate data streams (which most tools ignore).
No idea about ADS, but junctions work exactly as they should with WizTree [0].
I have junction folders that are bigger than the entirety of C, so with that not working, the tool would have been uselesss.
At $DAYJOB all the commits have a particular uniform format and are quite restrained and professional. I wouldn't say 'amused' but I agree with you, it did bring me a smile to see this person showing their humanity in their side project, especially in such a deep technical context.
