Hacker News new | ask | show | jobs
by chubs 1691 days ago
IIRC, when the M1 first came out, there were a bunch of people saying their SSDs were being worn out super quickly, citing SMART statistics. Perhaps this safari process was the culprit?
3 comments

> Perhaps this safari process was the culprit?

No, for many people it was Rosetta apps.

BTW, Apple totally lied when they said they "fixed it" in an update and it was only a "reporting issue". It's not fixed, and it was absolutely f'ing not a reporting issue. People's SSDs have already failed because of this, and obviously they're soldered.

> People's SSDs have already failed because of this, and obviously they're soldered.

Any links to more info about this? I’ve had my eye on a 16” Pro with an M1 Max for a couple weeks now but want to make sure it won’t have issues like this.

I haven't actually seen any reports of SSDs actually dying. Can you provide some links? SSDs dying in less than a year of typical use is a huge deal.
https://tidbits.com/2021/05/27/an-m1-mac-cant-boot-from-an-e...

I don't see any reports but there is evidence that should the soldered on SSD fail the entire device is borked short of board level repair.

I haven't seen any conclusive evidence one way or the other.
wow Safari is the IE5 of browsers now, having to do so many work arounds like we used to have to do with IE5 and now its killing hardware that you can't even replace.
Chrome is IE of browsers now. 20+ years ago nobody cared about non-IE, today nobody cares about non-Chrome.
Chrome is the IE of browsers with respect to being the dominant player approaching monopoly status.

Safari is the IE of browsers with respect to being buggy and behind on features with a slower release schedule.

IE was both and more extreme on both issues.

It’s only “behind” relative to Chrome, the dominant browser which more or less sets the standards these days. Calling Safari “behind” is judging browsers by how similar to Chrome they are.
Also Firefox and even Edge when the IE version was being developed. They've also refused to implement features which would bring web apps in line with the the capabilities of native iOS apps (things like push notifications, offline support with data that doesn't get cleared every 7 days).
IE never killed hardware. It kept legacy Enterprise technologie alive ( eg. ActiveX )
Unsure whether it's Safari related, but it was solved on a regular macOS update. I didn't recall any specific Safari update, but I might miss it.