> This is no different from Apple having a whitelist for TRIM support of SSDs in earlier versions of macOS. People were under the impression that there was some good technical reason for this.

I used to force-enable TRIM on my non-Apple SSDs for years, it was irritating but I think they were right to be cautious. Disk controllers have a history of serious bugs being triggered by external commands.

My go-to example is my Samsung HD204UI drives, they shipped with a firmware bug[1] that led to write corruption whenever a specific command was issued to the drive. Samsung issued a firmware fix without bumping the firmware version, so even today several years later, smartmontools prints a warning every time it runs, because it's impossible to tell which drives have been fixed.

Stuff like that is so common[2][3][4] the Linux kernel maintains a list[5] of devices that certain commands shouldn't be used on for various reasons. One has TRIM completely disabled, several have NCQ TRIM disabled due to known corruption issues, including one I still own: the very same drive I used to force-enable TRIM on when it was in my Macbook.

[1] https://www.smartmontools.org/wiki/SamsungF4EGBadBlocks

[2] https://github.com/torvalds/linux/commit/cda57b1b05cf7b8b99a...

[3] https://bugzilla.kernel.org/show_bug.cgi?id=71371

[4] https://bugs.launchpad.net/ubuntu/+source/fstrim/+bug/144900...

[5] https://github.com/torvalds/linux/blob/master/drivers/ata/li...