Does this sound like Apple response on a bug? I guess this is second such response, first one being the phil schiller's comments on scratches and scuffs on new iPhone 5. I do not get it, am I missing something ? Oops... my bad I totally forgot its post Jobs era Thank you Apple, we apple fan boys will tune to this new frequency.
Does this sound like Apple response on a bug?
I guess this is second such response, first one being the phil schiller's comments on scratches and scuffs on new iPhone 5.
I do not get it, am I missing something ?
Oops... my bad I totally forgot its post Jobs era
Thank you Apple, we apple fan boys will tune to this new frequency.
Nah, Apple is still beyond reproach and this is just another media beat-up by the Android-loving press, everyone knows Android is way worse. Apple will find the culprit anyway and fire that executive, because he refused to sign an apology letter, but Tim Cook will say it's to "improve teamwork".
Business as usual, nothing to see here, everything still hunky-dory at Apple HQ.
We measure a "year" according to the duration of the earth making a complete orbit of the sun and that duration is slowing down (albeit minutely), therefore we measure that duration in "days." However, "days" are measured by the duration of the earth making one complete rotation on its axis and that rotation is slowing down as well. Therefore we measure our days in seconds. We have been adding "leap seconds" and "leap days" when required to keep our measurement of time in allignment with the position of the earth in relation to the sun (while largely neglecting lunar events at all).
All this adjustment is really to keep the peasants (read: all of us) happy and not confuse us about what "time" it is. I wish we could move off the current calendar that was inspired in BCE and move to a more accurate and modern device.
I feel bad for the software engineers that have to write code that recalls all the colloquial names we have for the time we keep.
Or perhaps software engineers should do what they're supposed to do? Oh wait, this bug wasn't the fault of Apple, it's the fault of the Earth going around the Sun. Got it.
C'mon people, even a long-time (recently former) Apple fan like myself sees these apologetic comments as a little bit... stretched.
Something is up post-Steve Jobs, and we need to get to the root (pun unintended) of it.
If a butterfly flaps its wings in the Amazon could it cause rain in Africa? One bit or stack modified way over there could start the dominoes falling. Why do you think it takes so long for some bug fixes to be released? Fix a bug over here and it causes another bug over there sometimes.
You saw their code? So, no, you don't know any more than I do. Less actually, since I at least know you have no idea what you are talking about and you don't.
A developer can take an educated guess at how the functionality is implemented. A lot of software problems have a single sensible solution (and that's why software patents are bad). Either Apple has used NSDate (as stated - a public and widely used API) or has reinvented in the wheel. The former seems more likely, though the latter would explain why Apple has been the victim of so many end-of-year bugs.
A developer can take an educated guess at how the functionality is implemented. A lot of software problems have a single sensible solution (and that's why software patents are bad). Either Apple has used NSDate (as stated - a public and widely used API) or has reinvented in the wheel. The former seems more likely, though the latter would explain why Apple has been the victim of so many end-of-year bugs.
Apart from the fact that there are more than two possibilities involved, he still doesn't know what he's talking about.
You don't think that all code changes are vetted by at least two programmers and testing is done? You seem to have a negative view on programmers in general.
That's an odd assumption, since I am a programmer.
One who has coded many date bugs that went undetected, and one who has found many bugs in date routines in others' code.
So no, I don't have a negative opinion of programmers, I have a realistic view of which functionality is complex and therefore likely to harbor bugs, and the motivations that cause programmers to hit these same bugs over, and over, and over.
I'm surprised that the statement from Apple wasn't something more like "this is a bug that will fix itself on January 7 and we will be fixing it as quickly as possible with our next software update as well." Just saying that the problem will go away on its own on the seventh kind of implies that they don't think it's a huge issue and they're not immediately working on a fix, which I'm sure they are, but they really should make that clear.
Actually, this is important. The solution is to fix the bad code, yes. That they say it will fix itself is incorrect. The problem will stop, yes, for now. But the code clearly still calculates human time and date changes incorrectly. It will return in some other fashion some other day.
Except that doesn't explain why it reappears in 2014. And when it is based on time of day, why does it care about the week number?
I agree it does not explain why it appears again in 2014, as for the scheduling of Do Not Disturb, I would have to assume that if it will fix itself on a set day that it would be taking in to account some other information, other then just the time of day. After all, there is not much difference between 6 AM today, and 6 AM next Monday.
Quote:
Originally Posted by einsteinbqat
But why does it seems like it is only Apple that is having new year bug?
Apple is not the only one having problems this week, they simply have a larger user base in which experiences these problems. A good friend of mine is a developer for a local company and has also had problems this week, however his were a result of the leap year issue I was describing in my other post.
Comments
I guess this is second such response, first one being the phil schiller's comments on scratches and scuffs on new iPhone 5.
I do not get it, am I missing something ?
Oops... my bad I totally forgot its post Jobs era
Thank you Apple, we apple fan boys will tune to this new frequency.
Nah, Apple is still beyond reproach and this is just another media beat-up by the Android-loving press, everyone knows Android is way worse. Apple will find the culprit anyway and fire that executive, because he refused to sign an apology letter, but Tim Cook will say it's to "improve teamwork".
Business as usual, nothing to see here, everything still hunky-dory at Apple HQ.
Or perhaps software engineers should do what they're supposed to do? Oh wait, this bug wasn't the fault of Apple, it's the fault of the Earth going around the Sun. Got it.
C'mon people, even a long-time (recently former) Apple fan like myself sees these apologetic comments as a little bit... stretched.
Something is up post-Steve Jobs, and we need to get to the root (pun unintended) of it.
Quote:
Originally Posted by lkrupp
If a butterfly flaps its wings in the Amazon could it cause rain in Africa? One bit or stack modified way over there could start the dominoes falling. Why do you think it takes so long for some bug fixes to be released? Fix a bug over here and it causes another bug over there sometimes.
UNIT. TESTING.
Quote:
Originally Posted by jagv
...
Oops... my bad I totally forgot its post Jobs era
Thank you Apple, we apple fan boys will tune to this new frequency.
Quote:
Originally Posted by sr2012
...
C'mon people, even a long-time (recently former) Apple fan like myself sees these apologetic comments as a little bit... stretched.
Something is up post-Steve Jobs, and we need to get to the root (pun unintended) of it.
So, how exactly are your talking points and sites assigned? Clearly there's been some sort of foul up here. You aren't supposed to be that obvious.
more like:
if(week > 52){
exit;
}
Quote:
Originally Posted by anonymouse
You saw their code? So, no, you don't know any more than I do. Less actually, since I at least know you have no idea what you are talking about and you don't.
A developer can take an educated guess at how the functionality is implemented. A lot of software problems have a single sensible solution (and that's why software patents are bad). Either Apple has used NSDate (as stated - a public and widely used API) or has reinvented in the wheel. The former seems more likely, though the latter would explain why Apple has been the victim of so many end-of-year bugs.
wonder if its anything along the lines of Decimal 31 (Dec-31) is equal to Octal 37. Extra 6 units there, so the fix is on the 7th day
or maybe not... long shot
Quote:
Originally Posted by RichL
A developer can take an educated guess at how the functionality is implemented. A lot of software problems have a single sensible solution (and that's why software patents are bad). Either Apple has used NSDate (as stated - a public and widely used API) or has reinvented in the wheel. The former seems more likely, though the latter would explain why Apple has been the victim of so many end-of-year bugs.
Apart from the fact that there are more than two possibilities involved, he still doesn't know what he's talking about.
Quote:
Originally Posted by coolfactor
You don't think that all code changes are vetted by at least two programmers and testing is done? You seem to have a negative view on programmers in general.
That's an odd assumption, since I am a programmer.
One who has coded many date bugs that went undetected, and one who has found many bugs in date routines in others' code.
So no, I don't have a negative opinion of programmers, I have a realistic view of which functionality is complex and therefore likely to harbor bugs, and the motivations that cause programmers to hit these same bugs over, and over, and over.
Actually, this is important. The solution is to fix the bad code, yes. That they say it will fix itself is incorrect. The problem will stop, yes, for now. But the code clearly still calculates human time and date changes incorrectly. It will return in some other fashion some other day.
Quote:
Originally Posted by muppetry
Except that doesn't explain why it reappears in 2014. And when it is based on time of day, why does it care about the week number?
I agree it does not explain why it appears again in 2014, as for the scheduling of Do Not Disturb, I would have to assume that if it will fix itself on a set day that it would be taking in to account some other information, other then just the time of day. After all, there is not much difference between 6 AM today, and 6 AM next Monday.
Quote:
Originally Posted by einsteinbqat
But why does it seems like it is only Apple that is having new year bug?
Apple is not the only one having problems this week, they simply have a larger user base in which experiences these problems. A good friend of mine is a developer for a local company and has also had problems this week, however his were a result of the leap year issue I was describing in my other post.
I hope it does get fixed soon enough as Apple has promised. It is causing quite an amount of issues.
http://arstechnica.com/apple/2013/01/ask-ars-why-will-apples-do-not-disturb-bug-fix-itself-next-week/