Seems like one of those calculated trade-offs. Piss off however many Mac users in NZ versus steal focus from finishing Leopard on time. Or maybe it's not calculated, just a side-effect. Getting a lot bigger due to success doesn't always lead to a smooth ride quality wise.
So, IANAMU (I am not a mac user), but I don't think it would take "many resources" to take the patch developed here and give it official sanction! (or at least, have an engineer go through it to ensure it's good - it is, as my understanding goes, just a modification to the local plain-text timezone file!)
Not even doing that shows that they they simply don't care.
Tim
On 9/30/07, Walter McGinnis <walter.mcgin...@gmail.com> wrote:
> Seems like one of those calculated trade-offs. Piss off however many Mac > users in NZ versus steal focus from finishing Leopard on time. > Or maybe it's not calculated, just a side-effect. Getting a lot bigger > due to success doesn't always lead to a smooth ride quality wise.
> Cheers, > Walter
-- Kei te kōrero tiki au. Kei te kōrero tiki koe. Ka kōrero tiki tāua. Kōrero ai tiki tāua.
> So, IANAMU (I am not a mac user), but I don't think it would take > "many resources" to take the patch developed here and give it > official sanction! (or at least, have an engineer go through it to > ensure it's good - it is, as my understanding goes, just a > modification to the local plain-text timezone file!)
> Not even doing that shows that they they simply don't care.
Apple's software engineering is a bit of a cluster f**k at the moment. Maybe a combination of a lot of things, but the iPhone is probably quite high on the list of reasons
As we all probably know, time is a bit tricky to get right on computers and when you through in time zones it makes it even worse. There are several places that time zones are handled in Mac OS X. Some of then are a bit odd. Glenn's patch does a pretty good job but today we have found that he may have missed a couple and a heap of unrelated time zone bugs have come to light. They appear to have been there for a while and are only obvious because everyone is paying a bit more notice this year.
So getting a patch out of Apple wasn't going to be trivial, but they have known about it for at least 6 months so that's no excuse.
Have a friend with a Windows Mobile phone whom has his time reset every time he syncs with his PC. The timezone issue is even sticky with Debian: Debian Refuses To Push Timezone Update For NZ DST<http://linux.slashdot.org/linux/07/09/30/1117241.shtml>
Even with a trivial fix, I imagine the QA (OS, plus all their apps) might be non-trivial and something they would rather bundle into another update. Anyway, having a few small bugs and features just waiting on myself to get to them (and a paying client for them), I can cut other coders some slack.
> Even with a trivial fix, I imagine the QA (OS, plus all their apps) > might be non-trivial and something they would rather bundle into > another update.
> Anyway, having a few small bugs and features just waiting on myself > to get to them (and a paying client for them), I can cut other > coders some slack.
Rubbish. It's not like this is the first time any country has changed its DST rules.
They just pushed out a bajillion iSoftware updates last week and a bunch of firmware updates - if they can update the firmware on millions of macs around the world they can certainly create a patch for NZDST.
Plain and simple, apple suck this time. I hope it's not an indicator of things to come.
From: WellRailed@googlegroups.com [mailto:WellRailed@googlegroups.com] On Behalf Of Walter McGinnis Sent: Monday, 1 October 2007 8:18 a.m. To: WellRailed@googlegroups.com Subject: [WellRailed] Re: OSX Daylight Savings Thirdparty Patch
Even with a trivial fix, I imagine the QA (OS, plus all their apps) might be non-trivial and something they would rather bundle into another update.
Anyway, having a few small bugs and features just waiting on myself to get to them (and a paying client for them), I can cut other coders some slack.
> Plain and simple, apple suck this time. I hope it's not an indicator of > things to come.
Just as a bit of a blame-spreading session. Today I couldn't check my P O Box, the security doors weren't DST safe. The till at my coffee-dealer also printed out the wrong time on my receipt.
Seems like lots of people have dropped the ball on this...
On 10/1/07, Michael Koziarski <koziar...@gmail.com> wrote:
> Seems like lots of people have dropped the ball on this...
Google for one. Right now all the times in my gmail are out by an hour and I don't seem to be able to change my timezone to +13 in google calendar. Anyone else experiencing this?
> On 10/1/07, Michael Koziarski <koziar...@gmail.com> wrote: > > Seems like lots of people have dropped the ball on this...
> Google for one. Right now all the times in my gmail are out by an hour > and I don't seem to be able to change my timezone to +13 in google > calendar. Anyone else experiencing this?
Maybe not explicitly in connection with DST (at least for a while) but in other ways. I'd just like an option to have a built-in International Dictionary with aluminium spelt correctly, but I'm not holding my breath ...
NZ is a small market in the world. We can't expect everybody to get it right for us all the time. That's the reality. I'm not suggesting that the implications can't be quite far-reaching, but if we set aside bruised egos (the product of perceived arrogance) then it's a matter of recording the fact that this could have been handled better and getting on. I am pretty disappointed - for example - that Apple's representatives (you know who) in this part of the world have not lobbied harder for this to be handled better - or are they just ticket-clippers? Maybe they did? Does anybody know?
A client of mine called this whole thing Y2K7!
Robin
On 1/10/2007, at 11:40 AM, Michael Koziarski wrote:
>> Plain and simple, apple suck this time. I hope it's not an >> indicator of >> things to come.
> Just as a bit of a blame-spreading session. Today I couldn't check my > P O Box, the security doors weren't DST safe. The till at my > coffee-dealer also printed out the wrong time on my receipt.
> Seems like lots of people have dropped the ball on this...
I applied the third party stuff and have a few kernal panics since. Seems tied to specific behavior (ah, yes, spelling is relative and I revel in it!), but not sure what exactly. So beware. Course it could be the EyeTV update I installed last week, or the numerous Apple ones that have come out, too...
> I applied the third party stuff and have a few kernal panics > since. Seems tied to specific behavior (ah, yes, spelling is > relative and I revel in it!), but not sure what exactly. So beware.
> Course it could be the EyeTV update I installed last week, or the > numerous Apple ones that have come out, too...
|
