Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

reddit.com

Post reply on HN
Print view View original

461–470 of 501 posts

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#461

Post by free_everybody »

jcwayne wrote: post #374
kemayo wrote: post #53

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…

An even easier fix would be to drop the "Animate all the things!!!" mentality.

I think animations are pretty useful in this context. It reassures you that your sausage fingers didn't hit the wrong number.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#462

Post by drawnwren »

silviot wrote: post #255
laichzeit0 wrote: post #228

Let's just be frank: If Jobs was in charge, everyone that remotely touched that app would pulled into a room, berated and told how fucking dumb they are, and told to pack their shit and find another job. Remember, he was obsessive about the first calculator app and hand-tuned it to his liking, so it's not hyperbole to suggest that he would be fucking livvid. [1] Asshole, but perfection requires assholes. Apple is reg…

TIL some people think berating your employees when they do a mistake is a good way to run a company. WOW! It's just so wrong at so many levels, I don't even know where to start. I'll leave a link to this video: https://www.ted.com/talks/brian_goldman_doctors_make_mistake...

So against we have Brian Goldman, MD. And for, we have Steve Jobs, Bill Gates, and pretty much every other tech/entrepreneur darling of the 20th century. I'm pretty sure the results speak for themselves here.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#463

Post by KozmoNau7 »

lobster_johnson wrote: post #443
KozmoNau7 wrote: post #293

Earlier quoted context omitted.

3 days, 1 hour, 45 minutes. Simple. The Android clock app silently corrects 73 minutes to 1 hour 13 minutes. So for 1:13:45 (hh:mm:ss) you can input "7345" on the keypad and It. Just. Works.

But an alarm clock sets a relative point in time that happens every day. Putting "3 days" into a calendar is fine, but for an alarm clock it makes no sense.

So you add basic input validation.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#464

Post by sholnay »

11thEarlOfMar wrote: post #3

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…

I was using a 6 Plus up until a few weeks ago. Every upgrade caused serious performance decreases and I avoided iOS11 entirely (anticipating an upgrade to a new device). My partner upgrades yearly and I gave up all phone tasks to him when we were out together as my performance was so bad. Unlock? slow. Open chrome? 2-3 seconds. Open safari? 2-3 seconds. Fancy webpage? Forget it. We use google keep a lot, it basically didn't work on the 6 Plus. Sometimes the app would load quickly, sometimes it would take minutes or not load (or maybe if I kept waiting, it would eventually?). Scrolling in the app hardly worked. Screen touches became more hit or miss. Reflexively, I built in a 2-3 tap routine for most screen touches as it took that many for them to register. Scrolling any sort of content was difficult, stutter-y, and inconvenient. Siri didn't work - but I'm not sure if it does now either. I also had all animations off in an attempt to squeeze some performance.

Anyway, whatever apple did or didn't do, worked. I upgraded to an 8 Plus and couldn't be happier.

I run in to others who have version 6 phones and have no problem, so I don't know why I'm an outlier. Part of it is probably my storage habits, I was almost always within 5-10% of capacity. Now I have 256gb version and am hoping I don't get near the limit so that this phone will last me 3 years.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#465

Post by lobster_johnson »

KozmoNau7 wrote: post #463
lobster_johnson wrote: post #443

Earlier quoted context omitted.

But an alarm clock sets a relative point in time that happens every day. Putting "3 days" into a calendar is fine, but for an alarm clock it makes no sense.

So you add basic input validation.

Yes, but the person who originally proposed this argued that there was no ambiguity.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#466

Post by grzm »

sah2ed wrote: post #183
sogen wrote: post #2

As the thread says, I can confirm this bug, the answer: 24 :( iOS 11 must be the buggiest piece of s I've ever tried. Stuck animations, apps that take ages to load, widgets not working, more stuck animations, text overlapping everywhere. Related: Flat design was supposed to make things leaner... EDIT: Worst of all, every single operation is wrong: 7+8+9 = 96 4+5+6 = 60

I'm able to reproduce the bug on iOS 10.3.3 on an iPhone 6 so it appears the bug has existed before iOS 11.

Another datapoint: iPhone 4, iOS 9.3.5 does not exhibit the bug.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#467

Post by ratiofarming »

I see so many people here saying that their performance in older iPhones has declined with iOS 11.

I would like to point out that most (if not all) the lag issues and other performance related issues can be reproduced on a current iPhone 8. I have one. The flashlight has a noticeable delay when turning it on, the calculator is broken as described, the UI gets stuck a lot, apps crash a lot etc.

This is not a money grabbing scheme by apple. iOS 11 is just really bad software. Not the calculator though, this problem is older and has been there in iOS 10 aswell.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#468

Post by singingboyo »

chasd00 wrote: post #453
whatever_dude wrote: post #366

Earlier quoted context omitted.

That's what happens when you read from a keyboard buffer. Since the buffer is not being read (and not cleared) until a prompt is in the screen, you can type whether you want and it'll get dumped and processed whenever needed. Not that long ago really, that's how it worked in DOS and most other terminals.

Isn't the keyboard buffer a part of the physical keyboard circuitry and interface? Hitting enter triggers an IRQ to flush the buffer, so if the CPU is too busy to handle the IRQ then things queue up until the CPU can get around to handling it. If that's the case, for this "feature" not to work would require a very low level architectural change to keyboards. (it's been many years since i've thought about this though)

Keyboard buffers are decidedly not on the physical keyboard. The keyboard might have a very small one, but the IRQ is triggered on every input.

The buffer in question is, for a tty, a driver-level buffer that holds on to the data until something reads it. If a command doesn't read it (which things like apt-get update don't) then it'll get read as the next command.

Of course, most terminals these days are ptys accessed via emulators, so the buffer is actually part of the emulator, but the same idea applies.

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#469

Post by chasd00 »

singingboyo wrote: post #468
chasd00 wrote: post #453

Earlier quoted context omitted.

Isn't the keyboard buffer a part of the physical keyboard circuitry and interface? Hitting enter triggers an IRQ to flush the buffer, so if the CPU is too busy to handle the IRQ then things queue up until the CPU can get around to handling it. If that's the case, for this "feature" not to work would require a very low level architectural change to keyboards. (it's been many years since i've thought about this though)

Keyboard buffers are decidedly not on the physical keyboard. The keyboard might have a very small one, but the IRQ is triggered on every input. The buffer in question is, for a tty, a driver-level buffer that holds on to the data until something reads it. If a command doesn't read it (which things like apt-get update don't) then it'll get read as the next command. Of course, most terminals these days are ptys accesse…

ah, the more you know :) I would have been shocked if i remembered all that correctly

Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator

#470

Post by maccard »

whalesalad wrote: post #419
maccard wrote: post #406

Earlier quoted context omitted.

Video games use animations as easy to project information to a player. If your character is “stunned” and can’t move, the animation should play for the duration of the status effect.

Sure. But that’s an inherent feature of the animation. In this case the “never” rule doesn’t apply. If animations are a side effect, you want to treat them as such.

The never rule not applying what what I was giving an example of!
Post reply on HN