this post was submitted on 07 Aug 2023
438 points (93.6% liked)
Technology
59596 readers
3055 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.