diskmoose: An example to the contrary

I try to be blunt when I run into programs I don’t care for. In some cases I just don’t know how to use it, and when I can, I plead ignorance.

Others I just don’t … see the value in.


That’s diskmoose. And apparently that’s all it does. It has two dependencies: cowsay and go. One is miniscule, and the other is gargantuan.

It accepts no switches or flags. It has no man page. The home page gives no real guidance. All I can get it to do is what you see in the screenshot above.

I’m hoping something spectacular happens if any of those paths actually fill to less than 100Mb. Because as it is now, diskmoose has no real benefit I can garner.

For giving no details, for having no discernible controls, and for committing the cardinal sin of dragging in a massive dependency (43Mb!) that apparently adds nothing … I have to hand out an exceedingly rare un-smilie to diskmoose: 😦

2 thoughts on “diskmoose: An example to the contrary

  1. imgx64

    I think this is a mistake by the packager. Unlike Python, Perl, and other “scripting” languages, Go programs are compiled and don’t require anything to run on a system (and on top of that, they’re statically linked so they have even fewer requirements).

    As for what happens when disk space goes below 100MB, it just runs cowsay with a “Only XX MB free on YY” message.

  2. Ben Holroyd

    In diskmoose’s (and go’s) defence, even the smallest c file would require compiler + libs which would probably add up to 40mb+
    of dependencies, what about the python runtime?

    You can complain about the binary size though, a standard hello world in go is above 1mb, I’m sure you’ve probably come across
    an OS or 2 smaller than that ;-P.

Comments are closed.