|
|
|
|
|
|
by IanCal
3958 days ago
|
|
|
> 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. |
|
|