XPost: misc.phone.mobile.iphone, comp.sys.mac.advocacy
From: walterjones@invalid.nospam
badgolferman wrote
> The vague description of the problem will lead to a vague description of
> the solution.
>
> iOS 17 has been installed on my work iPhone 11 and I havenąt noticed any
> problems, but then I only use Outlook to view email.
>
> iOS 16.7 has been installed on my personal iPhone 14 and I will hold out
> for the vague solution to be released.
Hi badgolferman,
If we use our adult cognitive skills and our well-remembered history of
what Apple does to cleverly hide their (repeated) lack of testing...
*A pattern emerges*
Do you see the pattern?
I do.
What's patently obvious to any adult is Apple forgot to test this latest
device in the real world (which includes Instagram & iOS 17 for example).
Right?
That's a fact as had they tested it, this never would have happened.
So we have to agree - as adults - Apple didn't sufficiently test it.
That pattern has already been well established with Apple products.
Need I elaborate?
I hope not.
Now to the blame game that Apple _always_ plays.
*You're holding it wrong* and "The batteries that made me do it*.
It's a pattern with Apple to blame everyone but Apple, right?
Well lookey' here.
Apple just blamed a dozen (or so) entities for the problem, right?
Now, here's the adult question to ask of you (or anyone else)...
*How many of those entities that Apple blamed - did not exist prior?*
The answer is zero, right?
Right?
Every single entity that Apple blamed existed _prior_ to the release!
That's just a fact.
This means the real problem is as simple as what I've proven for years.
*Apple forgot to sufficiently test their design before releasing it*
It's really that simple, is it not?
Do you agree?
Or disagree?
Why or why not?
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
