←back to thread

380 points rezonant | 8 comments | | HN request time: 0.654s | source | bottom
Show context
Krasnol ◴[] No.40207447[source]
Sounds like it's time again for the litany of fear, uncertainly and doubt or will we, now that the EU has hit so many times, finally hear the other one? The one where Apple came up with the idea by themselves, and they just needed some time to reassure quality?
replies(2): >>40207521 #>>40207946 #
hehdhdjehehegwv ◴[] No.40207521[source]
I’m guessing the EU is just holding it wrong.
replies(1): >>40207724 #
thebruce87m[dead post] ◴[] No.40207724[source]
[flagged]
josefx ◴[] No.40207896[source]
Jobs exact words where: "All phones have sensitive areas, just avoid holding it in this way."

Which is arguably worse, since all of Apples official statements on that case contained that bit of intentional gaslighting at the beginning. The iPhone 4 did not just have "sensitive areas", it completely exposed the antenna, causing it to short circuit from normal use.

replies(2): >>40207933 #>>40208100 #
thebruce87m ◴[] No.40207933[source]
I know the history of it, I followed it closely at the time. That’s why I pointed out that the quote was wrong ( and got downvoted ). I expect the same will happen to you since you posted the correct quote.
replies(2): >>40208066 #>>40208093 #
1. patates ◴[] No.40208093[source]
"All phones have sensitive areas, just avoid holding it in this way" practically means "you are holding it wrong".
replies(1): >>40208181 #
2. thebruce87m ◴[] No.40208181[source]
So if I tell a user a workaround for a software issue, and they turn round and accuse me of telling them they are using the software wrong I have to agree with them?
replies(2): >>40208257 #>>40208270 #
3. patates ◴[] No.40208257[source]
In that statement it wasn't 1) acknowledged that this is indeed an issue and 2) the word workaround was not used.
replies(1): >>40208436 #
4. andybak ◴[] No.40208270[source]
A workaround is literally "a way to avoid triggering a bug". So if it's a workaround, then you're admitting it's a bug.

So the distinction is between "We screwed up but at least you can do x to mitigate it" and "There's nothing wrong with us. It's you."

replies(1): >>40208431 #
5. thebruce87m ◴[] No.40208431{3}[source]
You are assuming they had done all the testing and knew the full extent of the issue. When you run in to an issue like this it could be a bad batch, a certain radio variant, firmware version, only 2G vs 3G and so on.

Nothing in the statement argues either way, it’s simply two statements- one factual and one bit of advice on how to mitigate.

6. thebruce87m ◴[] No.40208436{3}[source]
See my above statement. If someone reports issues with software you don’t immediately say it’s definitely a bug unto you fully understand it. Hardware is no different. We do not know if they were in a position to say either way at the time.
replies(1): >>40220873 #
7. patates ◴[] No.40220873{4}[source]
They simply said it's not a bug at first, then after the backslash, went back and admitted that it is.
replies(1): >>40220953 #
8. thebruce87m ◴[] No.40220953{5}[source]
I have been told by a mod that I am replying too much to this conversation (?) and I therefore cannot address your point.

It’s a shame as I think it is interesting to see how people perceive things with hindsight specifically related to apple and how engineers who presumably work on similar problems cannot apply the same logic to apple but I am forced to stop the conversation. This will be my last comment on any thread related to this and I am rethinking my contributions to HN.