[Jugurtha]

I'm not sure, but I think it's about resumable downloads and handling downloading errors.

I practically never download anything large through a browser: I get the link and then use `wget -c` to make sure I get the file, automatically retries when connection is lost and re-established, etc, instead of waiting a long time and then checking the download in the browser and find out it failed a few minutes after it started for whatever reason.

If it's a couple of megabytes, I use the browser. I don't trust the browser with larger downloads.

The "app downloader" may be doing similar things.

[chatmasta]

Maybe a useful tip: you can resume paused Chrome download files with wget -c

https://gist.github.com/milesrichardson/ca0d2b25baa8a0374910...

[Jugurtha]

Thank you. I'm aware of that. It's more work to delegate to one tool I know will often fail me and fall back on a second tool than to use the second tool in the first place.

[wicharek]

Well that probably made sense in times of IE5, but modern browsers can’t be worse than wget -c ...

[Jugurtha]

If modern browsers assume flawless internet connections, they'll be much worse than wget -c, at least at downloading large enough files for which there's a higher probability of something going wrong with certain internet connections.

I need to be able to leave something downloading and be sure that, when I come back, the file is there.

Now, would I do this if I had a 1Gbps? Probably not. But at 8Mbps, with an internet connection that only works if you offer intestines to gods, I have to.