Live data from Hacker News

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

reddit.com

291–300 of 501 posts

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

#291
post #208

Earlier quoted context omitted.

I never noticed anyone anywhere wearing an apple watch. Not that I spend any time looking at people's wrists, but you'd think if it was a massive success everyone would notice.

Interesting. Where do you live? Here in London they are really commonplace - you see them on people on the tube all the time and I notice them being used fairly regularly by all ages and sexes for contactless payments, running, etc. In fact they seem so widely adopted that it’s not uncommon to see even people with them who you would not necessarily expect to be wearing them.

They are given out for free to anyone signed up to Vitality health care (and stay 'active'). A lot of companies in the city use them as the health care perk.

I wonder how much that has bolstered the amount of people using one.

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

#292
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…

This shows how important UX really is. UI can be all glam and shiny, but the software with the most accessible of UX wins, more often than not. I always come back to the example of WhatsApp and how it took on SMS, IM, and emails and won. People claiming WhatsApp went in mobile first are getting it only partially right. WhatsApp defined itself as a replacement for SMS: No login passwords, no chat history, cross platfo…

> Similar thing for AMP pages: It just works and it is blazing fast.

It is already blazing fast with only HTML and CSS, as the Web was designed to be.

EDIT: typo

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

#293

Earlier quoted context omitted.

If all inputs are in hh:mm format, then there is no ambiguity of 930 as 9:30 am/pm. There could be a toggle for AM/PM. Who puts seconds as an input for setting their morning alarm? MAD!

What's the unambiguous setting of 73:45 in hh:mm format?

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.

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

#294
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 so easy to replicate, but there's much more going on than just this calculator bug.

Before I go on, note that I have the latest iOS installed, and I do iOS development. I'm not a clueless newbie.

Anyway here are some examples:

1. my iPhone apps crash 50% of the times when I bring them back from sleep.

2. Even the ones that DO load, takes around 8 seconds on average to start up. This includes Email and iMessage. Yes, I have to wait 8 seconds for my mail app and messages app to "boot up" before being able to check a message I just received. This is ridiculous. I have talked to several of my friends who have been experiencing the same thing.

3. I had to turn off animations. Otherwise I couldn't my screen will freeze when i try to type into imessage, etc. Remember, all of the above are happening WITHOUT the animation turned on.

4. I started getting emails from "No Sender" with empty content, couple of times a day. I'm just assuming this has something to do with some fucked internal clock (I have double checked and my iCal and preferences are correctly set) but who knows.

5. Yesterday I was trying to take a picture and opened the camera. And YES, I mean the native camera app that ships with iOS. I saw the camera UI launch, but there was no "camera". It was just a black screen. I've become accustomed to this type of lag in app loading so i waited for my camera to "boot up". It never did. The camera app was open and there were all the UI components, but it wasn't capturing anything. I have never seen anything like this before.

Please stop saying "haha it's funny how these idiots think some calculator problem means Apple's future is doomed" because last time something like this happened was when I switched from Windows to Mac.

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

#295

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…

If Jobs was in charge this wouldn't have happened

Antenna-gate (the iPhone antenna not working well enough if you held the phone) happened while Jobs was in charge.

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

#296

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…

Are you a programmer? If so, is not getting yelled at what motivates you to write good software?

I am a programmer. And if I shipped a crap like this, I would agree that I deserve to be yelled at.

But the problem is probably not at developer level, it's higher ups who don't care about quality control, which permeate downwards.

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

#297
post #94

Earlier quoted context omitted.

Does iOS runtime not use evented I/O? Coming from web, I would expect tap events to queue up while the thread is busy with an animation.

CoreAnimation runs animations on a background thread using state snapshots. The event loop is processing events during the animation. It is up to the programmer to decide if events are ignored or processed during animations because what that means depends on what you want to happen: is the animation interactive and reversible? Does tapping reset the animation or does it start animating to the new state from its exist…

Correction—CA animations process and render in a render server process. This is why even when the main thread is blocked, animations can continue.

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

#298

I've not worked at Apple before, but it wouldn't surprise me that a lot of these quality issues come from their supposed culture of secrecy and compartmentalization where no one knows what anyone else is doing for the most part. This makes it hard to test things end-to-end as an integrated whole before things get released. At my employer, our culture is almost the polar opposite -- everything is open unless there's a…

They did just fine while Steve Jobs was around. It's not the secrecy (although it does help to have transparency), it's complacency.

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

#299
post #182

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…

> 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.

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

#300

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 persists until you reboot your phone. Like, wtf?

This feels like Apple has crossed the Rubicon. The Steve Jobs era is officially over.

Post reply on HN