Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Or they did QA but just happened to miss this issue. Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug, I'm betting Apple is among them.


Apple still hasn't put up any official page about the issue though, nor does it appear they've pulled the update. Even if it missed QA, why haven't they made any official comment?


You clearly don't know Apple as a company. Last most big companies, they never EVER publicly admit any faults or mistakes with their products (unless forced to by large scale fiascos) because that would damage their perfect brand image. It's why they have comments disabled on all their social media accounts.


Google this week seems to be going through a similar bug on their flagship Android 14 release, affecting users who have multiple accounts set up. They also seem to be favoring a "minimal" strategy when it comes to PR communication surrounding this issue.


Okay?


> they never EVER publicly admit any faults or mistakes with their products

Of course they do. They’re just secretive in general, and keep communications edited. Compared to the word salad of modern companies on social media, I find it refreshing. Just fix the problem, issue replacements for those affected and move on quietly.


>Of course they do.

Where? Do you have any examples?


> Where? Do you have any examples?

The whole battery gate saga. Touch Bar. The 2013 Mac Pro [1].

[1] https://www.theverge.com/2017/4/4/15175994/apple-mac-pro-fai...


Yeah but that only proves my original point that Apple only admits mistakes when the public scandals are so violent it can't possibly deny them anymore as the shit pile broomed under the carped has grown so large it makes even them trip on it, so then they just enter damage control mode and PR recovery but not out of the kindness of their heart but because of media backlash.

But they never have the common sense to release statements like "hey, the latest MacOS update might brick some systems so we're pulling the updated until we can do further testing and patching, if you've been affected by the bug already go to a Apple store and have it fixed for free".


They have pulled updates [1]. The one person I know who was affected was given a replacement.

I suppose I'm failing to see the need for a public statement if you've fixed the problem and provide service to those affected. Nobody can pull the faulty update anymore. And it's not like someone with a bricked device is more likely to see a PR statement than seek out support.

[1] https://osxdaily.com/2023/07/11/apple-pulls-rapid-response-u...


methinks you're the self-victim of some confirmation bias here, sir.


It's not "refreshing" to hide problems.


It IS refreshing not to be insulted by the usual "You are important to us and we're taking this very seriously" PR fluff.


> It's not "refreshing" to hide problems

Hiding entails ignoring the problem. They're not doing that. Their track record is to fix it. Not every action needs an accompanying tweet and blog post.


Of course they are not ignoring the problem, internally. The issue issue at hand is that they are not being open about the problem.


Maybe because it isn't that big of an issue? Have you heard about this anywhere besides HN? If it were a big deal you know all the websites would be all over it as if the Mac were doomed.


"You're updating it wrong." —Steve


> Most companies would consider "the upgrade sometimes bricks the device" to be a release-stopping bug

I've run into such horrific bugs during pretty normal use that I don't think this anymore.


That would be: not delivering while still charging a premium.


Used to be, while Jobs was still around.

These days it's just a bunch of wannabes trying too hard to be him.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: