Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Is that kind of like if you get more and/or "better" women you'd be able to produce a baby in less than 9 months?


Give me more woman and I can produce more babies in 9 months!

Give me women without any genetic abnormalities or hereditary diseases and I can produce better babies in 9 months.

If you had bothered to read my entire comment you would know that I suggested the possibility that Apple's developers need more time. I suggested 18 month development cycles. So your comment is both stupid and dishonest.

"Thank you," to the other comments for explaining why my line of reasoning was wrong.
 
If you had bothered to read my entire comment you would know that I suggested the possibility that Apple's developers need more time. I suggested 18 month development cycles. So your comment is both stupid and dishonest.

Then maybe you shouldn’t call for “more or better OS developers“, thus implying the developers at Apple are somehow incompetent. That’s a rather insulting generalization.
 
  • Like
Reactions: C DM
Give me more woman and I can produce more babies in 9 months!

Give me women without any genetic abnormalities or hereditary diseases and I can produce better babies in 9 months.

If you had bothered to read my entire comment you would know that I suggested the possibility that Apple's developers need more time. I suggested 18 month development cycles. So your comment is both stupid and dishonest.

"Thank you," to the other comments for explaining why my line of reasoning was wrong.
Perhaps it might make sense to read the rest of my comments regarding the rest of it? Certainly makes that stupid and dishonest part quite ironic.
 
And this whole time I thought Apple was reinventing Mathematics ;)
Turns out Apple not as rich a company as reported. Seems they been using their own calculator. Seems like Apple only worth one quarter of 800 billion. Adding to quickly. Similar results 6 real 24 when keyed too fast. :D
 
What we are saying is that it would have been nice if it was fixed sooner, or wasn't even there to begin with, but it's harder to make a call as far as when it could have been fixed not knowing the details of it all (on technical side, as well as business side as well, given that it all plays a role). For example, the assumption there would be that the fix was simply something in the app itself and didn't involve something outside of it (like some system library/framework or something else of that nature) that might have required more changes and more testing. It also doesn't factor in other business needs as far as other things that are being worked on and timelines and and all of that. Not having something addressed sooner doesn't necessarily mean that it's being ignored.
I just don't buy that, sorry. Especially considering the "fix" has been to disable the animations on the button. Yes, the real world is complicated, in business, software development and everywhere else, really. But if it had been a priority, of course this could have been fixed earlier assuming Apple knew about it (which they must have pretty early on). Meaning for some reason or another it simply had not been a priority until fairly recently. The fact that the story blew up not just on tech website but news outlets worldwide, twitter etc. about how Apple's calculator is embarrassingly broken might have just encouraged them to finally get cracking on it..
 
11.1, which includes the fix, will probably come out any day now, possibly later tonight.
The latest 11.1 beta doesn't have the calculator fix.

I suppose there is a chance there could be an 11.1.1 update which includes the fix.
 
I just don't buy that, sorry. Especially considering the "fix" has been to disable the animations on the button. Yes, the real world is complicated, in business, software development and everywhere else, really. But if it had been a priority, of course this could have been fixed earlier assuming Apple knew about it (which they must have pretty early on). Meaning for some reason or another it simply had not been a priority until fairly recently. The fact that the story blew up not just on tech website but news outlets worldwide, twitter etc. about how Apple's calculator is embarrassingly broken might have just encouraged them to finally get cracking on it..
Well, you are considering that's what the fix was, but we don't actually know what it actually was and might have involved, none of us really do. It's a fair assumption to make, but it's not a given by any means.

There's also the consideration that it was fixed after it all publicly blew up. It's also a fair assumption to make, but given that 11.2 code has been in the works for some time and the build that has been released to developers today has more than likely been in internal testing for at least some time as well, it could just as easily be that the issue was fixed a few weeks ago, before much publicity about it has surfaced.
 
What do you know, bugs exist in code, even in that which is written by "someone that can write code".
I already said what I know: the keyboard uses animation and does not screw up at high typing rates, and other calculators like pcalc have animations that don't limit entry speed. Sure, bugs exist in anyone's code, but we know this is not intrinsic, so a good coder should be able to debug it without losing the animation.
 
  • Like
Reactions: rGiskard
It's also a fair assumption to make, but given that 11.2 code has been in the works for some time and the build that has been released to developers today has more than likely been in internal testing for at least some time as well, it could just as easily be that the issue was fixed a few weeks ago, before much publicity about it has surfaced.

Maybe the case but I doubt it. Apple is the company that once released an iOS version that had completely killed cellular service for some devices. How'd that make it past internal or even beta testing?
 
The new Apple has no shame. They'll make "Accurate Calculator" a sales point.

probably since they couldn't bother to make a statement about the issue to the public. A simple, " this is a problem that we are aware of and are working on" goes miles....
 
Maybe the case but I doubt it. Apple is the company that once released an iOS version that had completely killed cellular service for some devices. How'd that make it past internal or even beta testing?
In that particular case it seems like it was some sort of a build distribution issue as I recall which happened as the update was being distributed or getting ready for it essentially. Certainly doesn't excuse it or anything of the sort, but it's somewhat different than that issue being there during normal testing and all that.

That said, it is also a company that released an iOS version like iOS 4 that actually (not just seemingly) came close to essentially severely crippling some iPhone models, to the point that Steve Jobs had to personally address it and promise a forthcoming software update that would rectify it.
[doublepost=1509403340][/doublepost]
I already said what I know: the keyboard uses animation and does not screw up at high typing rates, and other calculators like pcalc have animations that don't limit entry speed. Sure, bugs exist in anyone's code, but we know this is not intrinsic, so a good coder should be able to debug it without losing the animation.
And as I mentioned just because two things might seem similar doesn't mean that they are in fact similar, let alone the same. Just because keyboard animations are working fine or because other calculator apps which might not use animations or use one version or another that's available to them, doesn't mean that it all directly applies to another app in the same manner. We can make conjectures, but we still don't know the actual details.
 
Well, you are considering that's what the fix was, but we don't actually know what it actually was and might have involved, none of us really do. It's a fair assumption to make, but it's not a given by any means.

There's also the consideration that it was fixed after it all publicly blew up. It's also a fair assumption to make, but given that 11.2 code has been in the works for some time and the build that has been released to developers today has more than likely been in internal testing for at least some time as well, it could just as easily be that the issue was fixed a few weeks ago, before much publicity about it has surfaced.
I guess that's possible.
 
probably since they couldn't bother to make a statement about the issue to the public. A simple, " this is a problem that we are aware of and are working on" goes miles....
Or "We didn't have time to make the new and improved calculator actually work so please refrain from using it. We expect to have it resolved in 20-30 releases and we think you are going to love it!"
 
  • Like
Reactions: Act3
You don't have to type the number that fast in order to trigger the bug. Doing it with 1 finger does the trick.
 
  • Like
Reactions: trifid
In other words this means all the iP5 and iP5c users will stay with a malfunctioning calculator!?
Well done Apple!
Based on quite a few people who were complaining about the issue in iOS 11, it seems like it doesn't exist in versions prior to iOS 11 (or at the very least not anywhere even close to the degree that it's to in iOS 11).
[doublepost=1509406509][/doublepost]
You don't have to type the number that fast in order to trigger the bug. Doing it with 1 finger does the trick.
You can still be fast with one finger too. But that's not that important really at this point--the issue is there and now has been fixed and will be out to the public in general in an upcoming update.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.