following the same reasoning why we do not have a encryption mode default any more in borg 1.1, we should remove the compression mode default and thus require the user to give --compression X for borg create.
Having --compression none as default (as now) is similarly bad as having --encryption none as default (as in early borg/attic).
let's discuss here whether we want to remove the default (see top post) or switch the default to lz4.
Pro remove:
Contra remove:
--compression X needs to be always specified (interactive use, unit tests, ...)Pro lz4:
Contra lz4:
Thumbs up here for "removing the default".
Thumbs up here for "lz4 as default".
Contra remove:
is a bit of a pain, --compression X needs to be always specified (interactive use, unit tests, ...)
I think that initializing new repositories is not done often, so it's a very minor annoyance, as is having to choose a value for --encryption.
Edit: Never mind, I forgot about the possibility of using different compression methods for each archive. It's a different situation from --encryption.
I think having some default compression level (lz4 or zlib) is the right choice. Having to specify it every time a backup is done is annoying, and for most regular users, one of those two will be fine. Just like we don't force people to read up on chunker parameters and set them, we can allow those who care to read the docs and adjust as needed.
(As a separate issue, I think it might be good to allow a per-repo default to be specified at repo creation time.)
Since I use a cron job -> wrapper script for my backups (and I kind of feel borg is ment to be scripted) I see the removal of a default as a non issue to everyday use, with some positives (which you already listed).
I vote having a compression as default however removing the default is still better than how it is currently.
ok, looks like lz4 as default compression is much more welcome (than having no default), so we'll take that.
Most helpful comment
Thumbs up here for "lz4 as default".