The last time the world was in panic for computer problems was 1999, when the Y2K approached. That's inevitable. After all, it has been 2000 years since A.D.
Lots of efforts were made to get ready for Y2K. No major problems were known. But how many people know some programmers merely pushed the problem of Y2K by assuming anything less than '50' is before 2050 so things appears to work? (Replace that 50 if any number if you like). Well that's another topic. Nobody worries about if 4 digits are enough for years when year 10000 comes. Well human civilization is only 6000 years? so we don't worry about it now, but inevitable assuming the earth is still going to be here in Y10k.
How many even know that Unix's unsigned 32-bit seconds since 1900 will overflow in 2036?
Y2K or Y10K are inevitable. What about the rather strange day light saving time? Note: not everyone in the world uses DST. Not everyone in US uses DST. It is self-imposed annoyance.
This year, daylight savings time is pushed a month ahead (by legislation), causing many computers to put patches to keep the right time.
Why do we do this? Why do we have daylight saving time at all?
The purpose is to save energy. By pushing people out an hour earlier there are more daylight, therefore saving some energy for lights at night. What is the net saving? Perhaps 1%.
Ok, we are used to the annoyance of having everyone set their clocks twice a year. We programmed it into the computers. And now you are going to move it? The little savings do not justify the potential programs of fixing all the codes and risking breaking stuff. Have a clue.
I think the only legitimate change to DST is to remove it altogether, and not moving it backward or forward. We have enough annoyance in life. Don't mess with the clock.
No comments:
Post a Comment