Hi, I’m a software developer. DST is a nightmare because it makes the clock jump (skip an hour in one direction, meaning there are wall clock times which don’t exist, or backwards, meaning there are wall clock times that exist twice). I don’t care whether we will settle on summer or winter time but please, just don’t make it jump.
As a software dev myself: if time in your application’s internals jumps on DST, something has been implemented incorrectly. That’s what zone information is for, to make times uniquely identifiable and timers run the correct length.
Getting the implementation right is hard, though. So, abolishing DST is very well worth it.
Hi, I’m a software developer. DST is a nightmare because it makes the clock jump (skip an hour in one direction, meaning there are wall clock times which don’t exist, or backwards, meaning there are wall clock times that exist twice). I don’t care whether we will settle on summer or winter time but please, just don’t make it jump.
As a software dev myself: if time in your application’s internals jumps on DST, something has been implemented incorrectly. That’s what zone information is for, to make times uniquely identifiable and timers run the correct length. Getting the implementation right is hard, though. So, abolishing DST is very well worth it.
I know, but many of our colleagues don’t. I’ve seen so many systems storing and processing their local wall clock time it’s not even funny.