fsv VS linux_kernel_map

There's a modern clone of it now: https://fsv.sourceforge.net/

fsv is a file system visualizer for comprehensive exploration and analysis. Utilizes a 3D layout, with both MapV and TreeV views, to facilitate unique perspectives on file hierarchy. For viewing permissions, phein4242 says, "It doesnt get any better than FSN/FSV."

Modern-ish version you can run on Linux: https://github.com/mcuelenaere/fsv

For a modern take on it: https://fsv.sourceforge.net/

With the upgrades to WSL in Windows 11 you can run fsv[1] with minimal hassle and get the true UNIX experience[2].

1: http://fsv.sourceforge.net/

Fun fact: this was a real application for IRIX, and there is an open-source clone of it.

There is fsv

fsn was proprietary SGI software for Irix. But a free clone exists : http://fsv.sourceforge.net/

My understanding of documentation * First and foremost, code should be readable and understandable after all comments are stripped out. * After code is understandable without comments, I add in comments anyway explaining the flow of the program and generally why something is being done. Perfect example of critically important commenting is that I note to self where sdl auto frees stream memory because this is not the way that C should work (I understand sdl did it to make code shorter and cleaner but it is still nonetheless wrongful to implicitly free any memory in c no matter the reason). * Anything I have to look up online I make comments about * If I must include garbage code, it always goes under the namespace MaybeBreakDontKnowHowToFix as a warning to myself and others. * Although I rarely use unmodified code from stackoverflow, I always comment the original inspiration the code came from. * I try to achieve 100% code coverage for projects. Combined with fsanitize=address, I’m able to fish out the vast majority of possible problems. * I make documentation about everything and don’t skimp on the opinions (which, sadly, most documentation does). I always comment on how things work together, possible issues you might have, errors you would encounter, and my opinions on how your code should be using my library optimally. * I try to make visual maps of my code. A particularly beautiful map by someone else: https://github.com/makelinux/linux_kernel_map * I always contain step-by-step build instructions of what commands to run to do what things (even though it’s usually just ./build --release or something simple) and openly disregard Windows because it’s not worth my time to port the development system to trashy useless operating systems. When I need to compile exes, I just use mingw and test in wine without ever touching Windows.