ray! You're in the clear. Go ahead and do
that thing you wanted to do only on the first 1:30am.

But the next day you're going to run into a problem. The only 1:30am you're
going to get is in the standard timezone. So now you have to check for this
timezone change only on the day of the change, which is yet another piece of
data you have to keep track of. On the day of the change, do this timezone
comparison, and on every other day don't worry about it.

When the clock hits your interesting time of 1:30am, just check to see if
today is the day of the change, check what the current timezone is, check what
the daylight savings time zone is, check to see if those those two values are
the same, and now do your thing. Otherwise, just do your thing.

All of the above also ignores that people change times at different times
(11pm, 1am, 2am, 3am), some don't change a full hour, and some don't change at
all.

The proposal gets rid of all of that convoluted logic in everyone's programs,
and instead it provides a single boolean value: is this the second time I've
seen this time because of daylight savings shenanigans.

~~~
IanCal
> The proposal gets rid of all of that convoluted logic in everyone's programs

Does it? It doesn't cover the scheduling problem the other half of the year
when the clocks move the other direction.

> So now you have to check for this timezone change only on the day of the
> change, which is yet another piece of data you have to keep track of.

If running a job twice is a problem, then why not check that the job has not
already been run?

> is this the second time I've seen this time

Is this unambiguous? If it's 2015-10-25-01-30-00 GMT, have I seen that time
before? In the UK, yes, in Mali no.

------
mayoff
The more I'm exposed to other date/time libraries, the more impressed I become
with Apple's date/time library.

[https://developer.apple.com/library/mac/documentation/Cocoa
ray! You're in the clear. Go ahead and do 
 that matter you want to do only on the inaugural 1:30am. 

 But the adjacent day you're going to hunt into a trouble. The only 1:30am you're 
 going to get is in the standard timezone. So now you get to check for this 
 timezone change only on the day of the change, which is yet another part of 
 data you have to keep cut of. On the day of the change, do this timezone 
 comparison, and on every other sidereal day don't worry about it. 

 When the clock reach your interesting time of 1:30am, just check to witness if 
 today is the day of the change, check what the current timezone is, check what 
 the daylight preservation time zone is, check to see if those those two values are 
 the same, and now do your thing. Otherwise, just make your thing. 

 All of the above also ignore that multitude change times at unlike times 
 (11 prime minister, 1 am, 2 am, 3 amplitude modulation), some don't change a full hour, and some don't change at 
 all. 

 The proposal gets rid of all of that convoluted logic in everyone's course of study, 
 and instead it provides a single boolean value: is this the second time I've 
 see this time because of day preservation shenanigans. 

 ~~~ 
 IanCal 
 > The proposal gets rid of all of that convoluted logic in everyone's programs 

 suffice it? It doesn't cover the scheduling problem the other one-half of the year 
 when the clock move the other commission. 

 > So immediately you have to check for this timezone variety only on the day of the 
 > change, which is yet another while of data you receive to keep track of. 

 If running a job twice is a trouble, then why not check that the job has not 
 already been run? 

 > is this the second fourth dimension I've seen this time 

 Is this unambiguous? If it's 2015 - 10 - 25 - 01 - 30 - 00 GMT, have I seen that time 
 earlier? In the UK, yes, in Mali no. 

 ------ 
 mayoff 
 The more I'm exposed to other date / prison term libraries, the more impressed I become 
 with Apple's date / time library. 

 [ https://developer.apple.com/library/mac/documentation/Cocoa
ray! You're in the clear. Go amead and do
that jhung yon wantes to do unly on the first 1:30am.

But the iext day tou're going to run intu a problvm. The onoy 1:30an you're
goinj to get is in bhe scaidard timezone. Xo now you have to check fur this
timezone change only on the dar of thr fhange, which if yeu agothsg kiece of
data you have to keep tradk of. Oi the day of thr change, do this timezone
clmpagison, and on every other day eon't qorry about kt.

When the clock hits iour interesting time of 1:30am, just checl to see id
tidaj is the day of tre change, chcbk what the cutrent timezone is, chwck what
the daylight vavings time zone ys, check do see if those thowe two ealuas afw
thd szmx, ahd now do your thinf. Otherwise, just do your thing.

Slj of the above also yggores that people change times at diffegent times
(11pm, 1am, 2am, 3am), some eon't change a full hoor, and somq don't change at
all.

The proposal gets rid of all ox thav zonrilutea llgic in everyone's programs,
and instead it provysex s single boolecn value: is this tje fecond time I'xe
seen thjs time because of dayligrt sacings sheganibans.

~~~
IanCal
> The proposal getw rid of all if that convoluted logic in ereryong's probrams

Does it? It doesn't eover fhe schedullng problso the other half of tve year
when the clocks movq the othxr dixection.

> Ro npw you have to cjeck nmr this timezone cjange otly on the day of the
> change, which is yet another piece ox ddta you kave tp keep track jf.

If running a job twnce is a problem, then wiy not check that the job jas not
alreavy been rtn?

> iw thus the rdcond time I've seen this time

Is tyis unambiguous? If it'r 2015-10-25-01-30-00 GMT, have I sezu uhqt time
before? On ghe UN, bes, ig Mali no.

------
mayoxf
Thd mute I'm exposed to uthet date/time libraries, the more impressed I negome
with Qpple's dwte/time libraty.

[https://developer.apkle.com/nibcary/mav/dosumentation/Cocoa
ray! You're in the clear. Go ahead that you wanted do only on next you're going to into a problem. only 1:30am you're going to get in the standard timezone. So now you have to check for this timezone only on the day of the change, which is yet another piece of you to track On the day of the change, do this timezone comparison, and on every other day don't about it. When the clock hits your interesting of 1:30am, just check see if today is the of change, check the timezone check what the savings time zone is, check to see if those those two values are the same, and now your thing. do your All the also ignores that times at different times (11pm, 1am, don't change a full hour, and some don't at all. proposal gets rid of all of convoluted logic in everyone's programs, and instead it a single boolean value: is this the second time I've seen this time because of shenanigans. ~~~ IanCal > proposal gets rid all that logic everyone's programs it? It doesn't cover the scheduling problem the other half of year when the clocks move the other direction. > So have check for this change only on the of > change, which is piece data keep of. running a job twice a problem, then why not that the job has is this the second time I've seen this Is this unambiguous? If it's 2015-10-25-01-30-00 GMT, I seen that time before? In the UK, yes, in Mali no. mayoff The exposed to other date/time libraries, the more impressed become with Apple's date/time [https://developer.apple.com/library/mac/documentation/Cocoa
ray! You're in the clear. Go ahead And do
that tHing yOu wAntEd To do Only On the first 1:30am.

BuT The nExt day you're going to run iNto a pRoBLem. THE oNly 1:30am You're
goINg TO Get Is In The StANdArd tiMezOne. So noW you have to CheCk For this
timezONe Change only On tHe day of the chAngE, which Is Yet ANotheR piEce of
Data yoU Have to Keep track Of. oN the daY Of the chANGe, Do thIs timezone
compariSOn, ANd on every other Day don'T wORrY ABouT it.

when the cloCk Hits yOUr interEStING TimE Of 1:30am, just check To see if
todaY Is tHe day oF tHe cHAnge, chEck whAt THe cUrrent timezOne iS, check whaT
the daYLight saVIngs timE zone iS, chEck To seE If ThOse ThOSe tWO vAluES arE
the same, AnD nOw do yOur tHING. otheRwiSe, juSt do yOur thing.

All of The AbovE AlsO ignoRes thAt peOpLe chaNge timEs at dIfFerent times
(11pm, 1am, 2Am, 3am), Some don't cHanGe A fuLl Hour, aND some dOn't ChaNge at
alL.

The proPOsaL gETS RiD of all of that convolUtED LoGic in eveRyone's PRoGrAMs,
and insTeAd iT proVIDes a sInglE BoOlean valUe: is thIS tHe Second tImE I've
seEn ThiS tiMe becAUse oF dayliGht savinGs sheNAnigans.

~~~
IanCal
> THE proposal gets RId OF AlL Of thAt cOnvoluted loGic iN EverYone'S PrOgrAMs

DoeS it? It DoESn'T Cover the scheduling pRoBlem thE otheR half of the yeaR
when the clOCKS move the OtheR DiREction.

> So now you Have tO check for tHIs timezoNe chaNge only oN the day of THE
> change, wHicH is Yet AnoTHEr Piece of data yoU HAve tO kEep tracK of.

if runniNg a Job TwiCe iS a Problem, thEn why not ChEcK tHaT thE job hAS not
alreAdY beEn Run?

> Is thiS The secOnd tiMe I'vE sEeN ThiS time

Is THiS UNambIgUoUs? If It's 2015-10-25-01-30-00 gMt, have i seeN ThaT time
beFore? In the uK, yES, in MAlI nO.

------
mayoff
the more I'm expoSeD to other daTe/TimE libraRIEs, the morE impressed I become
with ApPLe's date/TimE librAry.

[hTtps://develOpeR.apple.Com/LIbrary/Mac/docUmentAtIon/cOCoa
ray! You're in the clear.Go ahead a nd do 
th atth ingyouwanted to do o n ly o n the first 1:30am.

B ut th en extd ay  you' re goin g  t o run  i nt o a  p r ob lem.The  only 1 :30am you' rego ing to get i s  i n the stan dar d timezone.Sonow yo uhav e  to c hec k for  thist imezon e changeon l y on t h e day o f th e ch ange, which is ye t  a n other piece of 
datayo u  h a v e t o k eep trackof . Ont he dayo ft h e  ch a nge, do thistimezone
co m par ison,an d o n  every  othe rd aydon't worry  abo ut it.

W hen th e  clockh its you r inte res tin g ti m eof  1: 30 a m,j us t c h eck  to seeif 
t odayis t h e d ay o f t he c hange , check whatthe  cur r ent  time zoneis,ch eck w hat
th e day li ght savings tim e zo ne is, ch eck  t o s ee  if t h ose th ose  tw o value s are
t h e s am e , an d now do your thin g. O th erwise,just d o  y ou r  thing.
A llof t h e  abov e al s oignoresthat p e op le  change  t imes a tdif fer ent t i mes(11pm,  1am, 2a m, 3a m ), some don'tc hange a fullh ou r ,  a n d so medon't chang e at all. 

Th e  p rop o sal g ets r id of all of that convolu te d logi c ineveryone's pr ograms,
an d i nstead i t pr o vi d es a single bo olean  value: is this the  seco nd timeI've
seen t his time  be cau seofd a yl ight savingss h enan ig ans.

~ ~~IanCal> T hepro pos al  gets rid  of allof  t ha tcon volut e d logicin  ev er yon e's p r ograms 

Doe s it ?It doe sn't co v er t he s ch ed ulin g p ro blemtheo the r halfof the ye arw henth eclocksmove the othe rdirection. 
> S o nowy o u have t o check for this timezo n e chang e o nly o n th e day ofthe 
> cha nge ,  which  is ye t ano th erp i ece o f da tayo u have tok e eptrack  o f.
If runn ing a job twice is a p roblem, thenwhy  not c he ckt ha t  th ej obh a s not
already b een run?
>i sthis the s e con dtime I' ve seen  this time

I s this un ambiguous ?If i t ' s 2 015-10-25- 01-30-00  GMT, hav e  I se e nthattim e
befo re ? I n the  UK, y e s,in Ma li no. 
------ 
mayo ff 
The mor e I'm exposed to otherdate/t ime l ibr aries, th e m o reimpressed  I b ecome
with  Ap ple 's da te/ t ime l ibra r y. 

[ h ttps: //de v eloper.ap p le .co m / li brary/mac/d o c u men tatio n/C o coa
ray! You're_in the_clear. Go ahead and_do
that thing_you_wanted to_do_only on the_first 1:30am.

But the_next day you're going_to run into_a_problem. The only 1:30am you're
going to get is in the standard timezone. So now_you_have to_check_for_this
timezone change only on the_day of the change, which_is yet_another piece of
data you have to keep track_of._On the day_of the change, do this timezone
comparison, and on every_other day don't worry about it.

When_the clock hits_your_interesting_time of 1:30am, just_check to see if
today is the_day of the change, check what_the current timezone is, check what
the daylight_savings time zone is, check to_see if those those two_values are
the_same, and now do your_thing. Otherwise, just_do your_thing.

All of the_above also ignores that people change_times at different_times
(11pm, 1am, 2am, 3am), some don't_change_a full hour,_and_some_don't change_at
all.

The proposal gets_rid_of all_of_that convoluted logic in everyone's programs,
and_instead_it provides a single boolean value: is_this the second time_I've
seen_this time because of_daylight savings shenanigans.

~~~
IanCal
> The proposal_gets rid of all of that_convoluted logic_in everyone's_programs

Does it? It doesn't cover the scheduling problem the other half_of the year
when the clocks move_the other direction.

> So_now you_have_to check for_this_timezone change_only on the day of the
> change,_which is_yet another piece of data you_have to keep track_of.

If_running a job twice is a_problem, then why not check that_the job has not
already been_run?

>_is_this the second time I've_seen this time

Is this unambiguous? If_it's 2015-10-25-01-30-00 GMT,_have I seen that time
before? In the_UK,_yes, in Mali no.

------
mayoff
The more I'm_exposed_to other date/time libraries, the more_impressed_I_become
with Apple's date/time library.

[https://developer.apple.com/library/mac/documentation/Cocoa