[borland]

He "only" saved 30%? That's amazing. I really doubt most people are going to get anywhere near that.

When I run it on my home folder (Roughly 500GB of data) I find 124 MB of duplicated files.

At this stage I'd like it to tell me what those files are - The dupes are probably dumb ones that I can simply go delete by hand, but I can understand why he'd want people to pay up first, as by simply telling me what the dupes are he's proved the app's value :-)

[bhouston]

> He "only" saved 30%? That's amazing. I really doubt most people are going to get anywhere near that.

You misunderstood my comment. I ran it on my home folder which contains 165GB of data and it found 1.3GB is savings. That isn't significant for me to care about because I currently have 225GB free of my 512GB drive.

BTW I highly recommend the free "disk-inventory-x" utility for MacOS space management.

[jeromegv]

Everyone misunderstood your comment for a reason.

You wrote: but it only found 1GB of savings on a 8.1GB folder.

It’s quite a saving and that’s what everyone understood from your comment.

[horsawlarway]

I think this is somewhat funny.

His comment is pretty understandable if you've done frontend work in javascript.

Node_modules is so ripe for duplicate content that some tools explicitly call out that they're disk efficient (It's literally in the tagline for PNPM "Fast, disk space efficient package manager": https://github.com/pnpm/pnpm)

So he got ok results (~13% savings) on possibly the best target content available in a user's home directory.

Then he got results so bad it's utterly not worth doing on the rest (0.10% - not 10%, literally 1/10 of a single percent).

---

Deduplication isn't super simple, isn't always obviously better, and can require other system resources in unexpected ways (ex - lots of CPU and RAM). It's a cool tech to fiddle with on a NAS, and I'm generally a fan of modern CoW filesystems (incl APFS).

But I want to be really clear - this is people picking spare change out of the couch style savings. Penny wise, pound foolish. The only people who are likely to actually save anything buying this app probably already know it, and have a large set of real options available. Everyone else is falling into the "download more ram" trap.

[wlesieutre]

Another 30% more than the 1GB saved in node modules, for 1.3GB total. Not 30% of total disk space.

For reference, from the comment they’re talking about:

> I then tried again including my user home folder (731K files, 127K folders, 2755 eligible files) to hopefully catch more savings and I only ended up at 1.3GB of savings (300MB more than just what was in the NodeJS folders.)