All today’s fix confirms that this bug did exist, it was a problem, and it had something to do with database corruption. And by ignoring requests to comment publicly on the matter, it doesn’t impart confidence that this won’t happen again.
99.9% of Apple customers wouldn’t understand it if they explained this in any more detail. And they’re not gonna tempt fate by saying something stupid like “we guarantee this is fixed forever”. I get where this reporter is coming from but she should probably accept that this explanation is the last thing Apple will say about it.
Nothing prevents them from answering questions or making an blog post or announcement to talk about the issue. Not necessarily in the update change notes, but at least somewhere. It’s not like they can’t.
99.9% of Apple customers wouldn’t understand it if they explained this in any more detail. And they’re not gonna tempt fate by saying something stupid like “we guarantee this is fixed forever”. I get where this reporter is coming from but she should probably accept that this explanation is the last thing Apple will say about it.
Nothing prevents them from answering questions or making an blog post or announcement to talk about the issue. Not necessarily in the update change notes, but at least somewhere. It’s not like they can’t.
No, it’s like they won’t. Cost / benefit says no…