Re:Apple: March 9th 'Spring Forward' Event
by PinnBrain on Thursday February 26, 2015 @01:26PM
(#9114163)
Yes, tangent, but please support the movements in several states to abolish daylight savings time. Having time move out from under us has long been a pain for programming robust systems. Perhaps the 5th or 6th generation of Apple watch will not need to do such an archaic adjustment.
[ Parent
| on HN ]
Re:Apple: March 9th 'Spring Forward' Event
by spacehome on Thursday February 26, 2015 @01:44PM
(#9114329)
Daylight Savings Time has some ill effects, true, but if you think that making life easier for programmers is a point that should convince the general public, you're sorely out of touch. For one, it's not all that difficult in the scheme of things. For another, programmers dealing with dates in the past will always have to consider it. Lastly, the general perception is that programmers get paid quite well enough and can suck it up and deal with this minor annoyance.
Re:Apple: March 9th 'Spring Forward' Event
by uptown on Thursday February 26, 2015 @01:51PM
(#9114407)
Just wait till we travel to other planets' timezones. That's when programmers will really earn their paychecks.
Re:Apple: March 9th 'Spring Forward' Event
by happyscrappy on Thursday February 26, 2015 @01:56PM
(#9114443)
Or when timezones depend on how fast you are traveling.
[deleted]
Re:Apple: March 9th 'Spring Forward' Event
by padmanabhan01 on Thursday February 26, 2015 @02:44PM
(#9114903)
//We have enough digits to print 1424978922 on a watch face - that is standard Unix time. Why humans can't just learn to read that simple number is beyond me
You really think people should be using 1424978922 instead of 5:30 or 9:30? That kind of thinking is what's beyond me..
Re:Apple: March 9th 'Spring Forward' Event
by schoen on Thursday February 26, 2015 @02:57PM
(#9115024)
The parent commenter's post was definitely intended as satire.
Re:Apple: March 9th 'Spring Forward' Event
by ecobiker on Thursday February 26, 2015 @02:02PM
(#9114507)
I have worked on a fairly large scale distributed system where we had to deal with DST. The week before the switch was always the craziest. Until... we switched the boxes and the database to UTC. Even if DST is abolished, leap second will be something to deal with.
I have so many things I hate about DST - like switching all our cross timezone meetings but programming is not one of them - always set your machines and DB to UTC and do the conversion in your app.
Re:Apple: March 9th 'Spring Forward' Event
by jewel on Thursday February 26, 2015 @02:27PM
(#9114755)
You could even set your servers to TAI and adjust for leap seconds in your app, so that you don't have to worry about timestamps going backwards during leap seconds.