It does this in iOS 10 too (just tested)
Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
411–420 of 501 posts
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#412I 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…
Many of your problems are not the common ones that people are having with iOS 11. And even ones like 2. which many people are having sounds more extreme for you. I think you might want to debug this like a problem rather than assume it’s all due to Apple errors. With all that’s going on I’d probably just jump all the way to a full restore.
Come on man, you don't have to go that far. just read rest of the thread and you'll see tons of people complaining about the same thing.
As I mentioned I have multiple devices and I observe these problems everywhere. And I have heard the same from friends too. And all these people on this thread are complaining about it.
Now where is your source on how my problem is just some extreme case and my own fault?
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#413Earlier quoted context omitted.
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.
You didn’t answer the question, but I’ll go ahead and suggest that you are motivated to create good software, not by a fear of being yelled at, but rather something else. Maybe you think the product you are making is of actual value, and are proud of it. Maybe you want to impress your boss with the quality so you can get a raise. Maybe you don’t want to be fired. In any case, I would be shocked if there was anyone, a…
If I'm at the sort of job where I get yelled at for doing my job as I saw fit, I will be motivated in the future to find a better manager.
But then again, I'd never block user input to play an unnecessary animation on my own initiative, so I must have been doing that because my manager told me to do it, or because I wasn't given enough time to do the job properly. So if I got yelled at in that situation, I'd wait to see if I was fired, and quit if I was not. Management by loud, abrasive, dominance-displaying histrionics is not something I can work with, ever.
Every company gets one freebie, where I go above and beyond the call of duty to make the kind of software that I am proud to stand behind. If that effort is not rewarded or recognized, and explicitly encouraged to continue, I fall back into line and do exactly as I am told thenceforth--no more, no less. I won't offer my opinion unless it is requested, and I won't go looking for extra things to do to improve the code base. If that freebie is actually punished or reprimanded, I start looking for other jobs. What I have found is that few companies are interested in doing anything well, or even technically correct. They desire extremely consistent mediocrity. They don't want a hand-crafted hamburger made from fresh-ground chuck and crisp, juicy vegetables; they want a McDonald's hamburger with exactly two pickle slices and one pinch of minced onion.
Anyone that yells at a grill cook for making a gourmet burger instead of the McDonald's standard probably shouldn't be hiring trained chefs and assigning them to the grill. But worse, anyone that yells at their grill cook because they put a third pickle slice on the burger--an extra pickle that was asked for, or even demanded--probably should not be in charge of anything, much less a bunch of grill cooks.
Fear of getting yelled at is actually fear of having to navigate the awful interview process all over again, while pretending to care about my current job long enough for an offer to come in. I avoid doing my work badly mostly because I don't want to be a person who does bad work. If I ever do bad work, it's because I was told to do it that way--or maybe yelled at to do it that way--and I hate every shortcut and kludge, even as I am typing them into existence. At that point, I am already mentally out the door, only sticking around until that paycheck can be replaced by a check from somewhere else. Yelling is bad management, and bad management motivates me to leave.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#414Earlier quoted context omitted.
What's a concrete example of this?
An example that comes to mind is a slider switch (iOS is famous for them) You don’t want the switch activated until it’s all the way left or right.
Slider controls might be a better example, I think. In that case, the position reached by the moveable element is the data, and it is appropriate to take the value from the UI element (of course, if it lags noticeably, that is a UI design issue.) With slider switches, you could argue it either way, so long as program and UI remain consistent, but again there is a problem if the UI response lags the gesture.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#415Earlier quoted context omitted.
Do we even have sales figures for the apple watch. All I see is made up numbers and guesses.
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.
I think it's one of those things you notice once you're looking for them. I certainly see them fairly regularly, in my smallish MidWestern city.
As a random example, yesterday I bought fast-food fried chicken for lunch. The woman who took my order was wearing an Apple Watch. The barista at my regular coffee shop wears one.
They're definitely showing up on non-tech people. I've also never seen a woman wearing a smartwatch that isn't an Apple Watch.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#416As 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.
Which would affect the 2017 iPad also. Why introduce a new iPad with the A9 if you're going to limit the performance. Is it to get people to buy... what exactly? An iPad Pro? Why not simply ONLY make iPad Pros?
This line of reasoning is immature and beneath the type of discourse that should occur on any tech leaning site.
I really hope you're just being sarcastic and mocking everyone who really thinks this.
Edit: I, personally, have a 6S and it's fine. Of course I DFU and set up as new for new OSs. It's even better on 11.1 beta 5.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#417Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#418I 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…
I’ve been having the same experience with iOS 11. I often open the phone app to call someone I recently talked to, see their name at the top, click it to call them, only for the phone to call someone else. What’s happening is that someone else had called me in the meantime and iOS showed me the cached image of the screen but registered my touch on the “real”/live view of the screen. Safari does the same thing on both…
Safari on the desktop is very, very bad about doing this. The browser benchmark tests really should include this metric: the average time to ready after navigating back. Showing a cached image but registering a click on a different image just seems like such an obvious thing to avoid.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#419Earlier quoted context omitted.
What's a concrete example of this?
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.
Re: Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
#420Let'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...
Grandparent isn't trying to condone the practice of berating employees but to demonstrate how Apple under Steve Jobs would've been much more likely to catch these kinds of screwups before production and much less likely to tolerate them once they occurred. The means of correction are less important than the standard of quality which was effectively enforced.