I agree that autodefrag is a btrfs feature. But IMHO it's not a good default setting on a SSD, since defragmentation isn't an issue here.
My concern is, that if useres are not aware of this default setting, they get some unnecessary wearing on their device.
IMO you should avoid unneeded write-cycles on a SSD.
Looking at the code:
https://github.com/calamares/calamares/blob/master/src/modules/fstab/fstab.conf
# Mount options to use for all filesystems. If a specific filesystem
# is listed here, use those options, otherwise use the *default*
# options from this mapping.
mountOptions:
default: defaults,noatime
btrfs: defaults,noatime,space_cache,autodefrag
# If a filesystem is on an SSD, add the following options. If a specific
# filesystem is listed here, use those options, otherwise no additional
# options are set (i.e. there is no *default* like in *mountOptions*).
ssdExtraMountOptions:
ext4: discard
jfs: discard
xfs: discard
swap: discard
btrfs: discard,compress=lzo
It seems they first make a fs based setting turning autodefrag on and later add some SSD specific stuff.
However, you also could argue that since Artix is targeted to advanced users, those will tweak around in their systems anyway.
And if they don't like autodefrag just kick it out of fstab.
Just wanted to point this out. To me it's not a big deal at all.
Thanks!