401–410 of 501 posts
Earlier quoted context omitted.
Didn't the iphone 4 antenna issue happen under Jobs? With him claiming you're holding the phone wrong or something like that.
You mean the iPhone 4 antenna non-issue? Lots of bugs and issues happened under Jobs, but this was the usual press BS. The iPhone 4 went on to sell 50 millions of devices or so with that antenna and nobody in the real world had much of an issue with it.
Earlier quoted context omitted.
> It's enough to make me want to give up privacy and switch to Android. It's sadly no better on the Android side of the fence either. How many times I've had to wait for the keyboard app to decide to load…
I think that might be dependent on the keyboard your flagship provider ships with, and some are better than others. Thankfully, you can switch out the keyboard handler. That is, Android suffers from similar problems, some sometimes Android's modularity and allowing for choices comes through to save you. But still, the perverse incentives of Google make privacy a real question. Then again, if I was willing to put up o…
Earlier quoted context omitted.
Antenna-gate (the iPhone antenna not working well enough if you held the phone) happened while Jobs was in charge.
Not the best example. Lots of bugs and issues happened under Jobs, but this was the usual press BS. The iPhone 4 went on to sell 50 millions of devices or so with that antenna and nobody in the real world had much of an issue with it.
As soon as I upgraded my 6s to 11, I saw performance seriously degrade. It takes -seconds- to bring up the iMessage editor. My immediate thought was that Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more and I'd realize, as they do, it's time to upgrade. Or... maybe they are running every key stroke through the new Azure-enabled Cray com…
This. My 6 Plus is barely usable now, to the point where it is annoying the hell out of me. On iOS 10 i was fine with the 6 Plus and thought i could easily use it another year, but right now it's barely usable. I compared loading a banking app on my 6 and my colleagues 7 (closed it before) and the difference is astounding (2-3 seconds slower). Also everything is just laggy including typing and taking photos.
For a 3 year old phone, it's frustrating but still miles ahead of the last Android phone I kept for 18 months. It's still frustrating that the iOS update is basically forced on us instead of being an optional upgrade like on desktop. (Of course it's technically optionally, but the constant nag annoyance makes it effectively forced, imo.)
Earlier quoted context omitted.
Isn't 'never' an oversimplification? Sometimes there is a feedback loop between UI effects and user input, or the user input changes the way the UI registers hits, which means subsequent input depends on complete processing of prior inputs. On a static view like a calculator grid, you should default to non blocking animation, but sometimes blocking is the desired behavior.
What's a concrete example of this?
As soon as I upgraded my 6s to 11, I saw performance seriously degrade. It takes -seconds- to bring up the iMessage editor. My immediate thought was that Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more and I'd realize, as they do, it's time to upgrade. Or... maybe they are running every key stroke through the new Azure-enabled Cray com…
More annoying than performance is the ever increasing nagging for apple paid services, apple pay, apple icloud, etc. The platform is literally becoming a junk adware platform. It feels like an infected PC that pop ups ads randomly.
The iPhone is a rather one size fits most device. If you don't want to go along with Apple's idea of how to use the device, you will be unhappy with it.
Right now I'm fighting the practically forced upgrading of a particular app for which the update will remove functionality. But in order to not update one app, I'm forced to manually update every other app individually. Which is about 40-50 updates a week that I have to approve.
Using the phone forces me to realize the extent to which I don't really own it. I'm just sort of renting services from it with an all-or-nothing set of features.
I probably own more Apple devices than most people here (even considering this is HN we're talking about) because I do a lot of iOS programming and I have to use them as test devices. I also own the latest devices. But this problem is not some stupid complaint coming from uninformed people. This calculator thing was a perfect symbolism for all this bullshit that's been going on since iOS 11 release because the bug is…
Was going to upgrade to an iPhone X. After this iOS 11 nonsense, I'm honestly considering going back to Android. It's absolutely unforgivable how terrible my iPhone 6S has been running since the update. Same as you: constant crashes, random freezes and reboots, abysmal battery life, not to mention an insane bug where when someone calls you (or you call them), they can't hear you and you can't hear them. This bug pers…
I think Android 8 has some flaws atm that are really kneecapping things. I had constant app crashes. Loading problems. All sorts of little things that seemed to be super buggy. Windows appearing behind other windows, adds not properly being put into their space. I went back to my iPhone 6s.
That said, you might have a better experience, those things might get fixed. I am sure they will be fixed both on iOS and Android. I am just saying, the latest and greatest on Android kind of sucks too.
Earlier quoted context omitted.
> My immediate thought was that Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more and I'd realize, as they do, it's time to upgrade. That was actually recently debunked by Futuremark https://www.futuremark.com/pressreleases/is-it-true-that-iph... . Important excerpts found at the bottom of the page: > Our benchmarking data shows that, ra…
What is debunked? That the CPU has not changed during the upgrade? No shit sherlock. Synthetic benchmarks tell nothing of the end-user experience. Does Apple sprinkle wait()? No. Does the system become more and more complex and Apple taking less time to optimize because it runs “fine” on the [latest - 1] hardware? Yes.
Fucking loser
People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. The actual issue is that some developer at Apple screwed up their animation configuration when implementing the calculator redesign, and nobody tested adding more than two numbers together quickly. Multiple failures, none involving system performance. What's happening is: the operato…
Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms. What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely. Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy probl…
But I feel my first suggestion was exactly what you're suggesting -- immediately register the input and apply the operator -- I just phrased it in terms of what happens to the animation.
Also! I certainly feel there are times when letting an animation block your logic is valid. That would be any time when an animation has the UI in a potentially confusing state, such that the meaning of an input is ambiguous. (You should avoid these states as much as possible, of course. And this sort of button-flash comes nowhere even near that category.)