It’s a standard USB device. It interacts with MacOS only via the USB bus, following the standard/spec. If it craps its pants and fails catastrophically when it receives specific, valid USB commands, then it doesn’t matter whether it’s only MacOS or TempleOS that sends the commands that trigger that particular failure case. It’s still the drive’s fault, because it’s failing to do its literal one and only job of safely storing your data over USB.
E.G.: If MacOS can trigger the failure now, then there’s no guarantee that any future update to Windows or Linux won’t also trigger the same failure.
Is this an issue with MacOS? Even the comment section in the article keeps mentioning that it happens on MacOS.
It’s a standard USB device. It interacts with MacOS only via the USB bus, following the standard/spec. If it craps its pants and fails catastrophically when it receives specific, valid USB commands, then it doesn’t matter whether it’s only MacOS or TempleOS that sends the commands that trigger that particular failure case. It’s still the drive’s fault, because it’s failing to do its literal one and only job of safely storing your data over USB.
E.G.: If MacOS can trigger the failure now, then there’s no guarantee that any future update to Windows or Linux won’t also trigger the same failure.