Foo - Daylight savings time sucks...

...and so do time zones for that matter. It would be a lot simpler if everyone was on GMT time with no DST.

My 2 cents.

Also, I'm curious how computer software deals with the fact that there's two of the same hour on a particular day. For instance, if you say 1:30AM on Sunday November 6th, 2011, it's ambiguous because there are two 1:30AM's.

Also, I'm curious how computer software deals with the fact that there's two of the same hour on a particular day. For instance, if you say 1:30AM on Sunday November 6th, 2011, it's ambiguous because there are two 1:30AM's.

What? I use the 24 hour clock: 0000 to 2359. There is only one 0130. Are you actually talking about 1:30 am vs. 1:30 pm?

What? I use the 24 hour clock: 0000 to 2359. There is only one 0130. Are you actually talking about 1:30 am vs. 1:30 pm?

No, I'm talking about the first 1:30 am vs the second 1:30am.

Also, I'm curious how computer software deals with the fact that there's two of the same hour on a particular day. For instance, if you say 1:30AM on Sunday November 6th, 2011, it's ambiguous because there are two 1:30AM's.

Generally we use a timestamp for processing purposes which is a unique number for any given date and time, and then convert it and laboriously account for daylight savings and time zones when presenting the time in a format for humans. Even so the code is prone to error.

In Unix the date corresponding to a "0" timestamp is in December 1969 which is why you'll see that pop up occasionally.

I think you're right that we'd be better off without DST adjustments. Just change the hours your business opens or closes when you want to - we don't really need the clock to give us permission for that.

No, I'm talking about the first 1:30 am vs the second 1:30am.

There is only one 1:30 am per day. Please explain where the second one is.

If you go to sleep before 9:00pm the day before (total accident), daylight savings changes are no problem at all.

Time sucks.

I don't like dst and going through a time zone, getting to work with jet lag, etc. It is sort of like going through a time zone when you lose an hour's sleep, and you don't even get to a nice vacation spot, just to work. (sigh)

A Canadian insurance group came out against it a few years ago. On the time change when people miss some sleep, there is an increase in accidents and deaths the Monday after.

When the benefits are debatable, there is no point for that kind of damage. (or for my jet lag)

Generally we use a timestamp for processing purposes which is a unique number for any given date and time, and then convert it and laboriously account for daylight savings and time zones when presenting the time in a format for humans. Even so the code is prone to error.

In Unix the date corresponding to a "0" timestamp is in December 1969 which is why you'll see that pop up occasionally.

I think you're right that we'd be better off without DST adjustments. Just change the hours your business opens or closes when you want to - we don't really need the clock to give us permission for that.

Ah, yes. That's Unix Epoch time, no? I think Thinkgeek had an alarm clock that told time in that format. I remember some folks spazzing a while back over the fact that from 1969 to 2037 (or 2038) would be 2^32 seconds and then everything would go to s**t. Of course, it seems we'll be well out of 32bit technology by then.

There is only one 1:30 am per day. Please explain where the second one is.

Once a year, November 6th (today) this year, the clock happily passed 1:30am on it's way to 2:00am. When it hit 2:00am, BLAM! time turns back to 1:00am as DST is ended for the year. Clock continued it's happy little march across the minutes, crossing 1:30am again, one hour after it did earlier.

Make sense now?

Also, I'm curious how computer software deals with the fact that there's two of the same hour on a particular day. For instance, if you say 1:30AM on Sunday November 6th, 2011, it's ambiguous because there are two 1:30AM's.

Well-written software handles it flawlessly as stated by other posters.

Not all software is well-written. I had to support a horrible application. It tracked packages in a sorting facility. Each day was divided into shifts. DST completely crashed the system twice a year. We only had authorization to get the system running again, not fix the underlying issues.

The problem? The "timestamp" was the local computer time, after adjusting for DST. Gah! Who thought that was a good idea?

... and to further confuse things, in the spring there is a day without a 2:30am. When the clock hits 2:00am, it "springs forward" to 3:00am.

So the date/time 3/13/2011 02:30 doesn't actually exist.

BF is in the future...posts are listed as an hour ahead. This is Future Me posting now...I mean soon.

http://www.youtube.com/watch?v=VeZ9HhHU86o

I love it. I got an extra hour of sleep, and now for my morning rides sun comes out sooner.

... and to further confuse things, in the spring there is a day without a 2:30am. When the clock hits 2:00am, it "springs forward" to 3:00am.

So the date/time 3/13/2011 02:30 doesn't actually exist.

That's because there are only 12 months in a year not 13, unless, of course, you are not talking about lunar months.

I like it when the time changes in the Fall, but not the Spring. In Fall I can either get an extra hour of sleep, or change my schedule so I'm waking up an hour earlier, without even trying. In Spring I simply lose an hour of sleep. And in TN it meant that hot weather was just around the corner, which I hated more than anything.

So are you glad Daylight Savings Time is over if you think it sucks? We're on Standard Time now.

That's because there are only 12 months in a year not 13, unless, of course, you are not talking about lunar months.

Oh quit your pansy date formats. Real men use MM/DD/YYYY. :D

So are you glad Daylight Savings Time is over if you think it sucks? We're on Standard Time now.

It's the change that sucks for me... both Spring and Fall. I'd prefer it just didn't change. I don't care what time it is, I just don't want to adjust my sleep schedule twice a year.

Once a year, November 6th (today) this year, the clock happily passed 1:30am on it's way to 2:00am. When it hit 2:00am, BLAM! time turns back to 1:00am as DST is ended for the year. Clock continued it's happy little march across the minutes, crossing 1:30am again, one hour after it did earlier.

Make sense now?

OK, so you are referring to the special case of the actual day of the DST change. Yes, I would agree with that.

it's the change that sucks for me... Both spring and fall. I'd prefer it just didn't change. I don't care what time it is, i just don't want to adjust my sleep schedule twice a year.
word.

For least ambiguity and easiest machine sorting, YYYY-MM-DD (or simply YYYYMMDD) for the win.

Sure, I do that when writing SQL queries, but If I started putting dates as 20111106 in my normal correspondence, I'd be considered even weirder than I am.

Sure, I do that when writing SQL queries, but If I started putting dates as 20111106 in my normal correspondence, I'd be considered even weirder than I am.

I date all my personal stuff like this. Quick Books updates, SD card dumps, etc. Auto sorting can't be beat.

I think I'm almost old enough to be eccentric enough to start using it in regular correspondence. It shall commence on my next birthday.

Living under the DST regime is one of the few things that makes me want to move back to Arizona, the land of milk and honey for time-change haters.

None of the bars seemed to observe the changes until after they'd closed on Saturday nights. Back in my youth I'd kinda hoped they'd stay open an extra hour for the fall change.

Besides, weird would be using the Unix epoch instead.

Come to my party! 1320610914 and not a second later!

What about the COM datetime thing used by VB6? It used a floating point number, where the decimal portion was the time.

The date time just a minute ago was "40853.6957291667"

Much better, right?

Hey, at least you're not apple.
They can't get DST working right.

http://www.neowin.net/news/apple-still-doesnt-understand-how-dst-works-issues-reported

I approve of DST. I used my free hour for a bike ride.

http://www.thinkgeek.com/homeoffice/a7c5/

225998

Hey, at least you're not apple.
They can't get DST working right.

http://www.neowin.net/news/apple-still-doesnt-understand-how-dst-works-issues-reported

If this is an iPhone only issue (and I think it is) it's probably more the cell phone network. Stupid carriers (all of them) broadcast time in local time. Have you noticed your phone will change time as you drive across (or even near) a time zone boundary?

The carriers should broadcast two things 1) UST time/date 2)Time zone they're in.
Then it would be up to the phone to show correct time and handle and DST changes.

My dumbphone updates the time when Verizon gets around to broadcasting the change - which a few years ago was horrible. Has been better recently.