Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy. This forum is not for asking programming related questions.
NEW YORK -- Just when you thought it was safe to stop worrying about Y2K, some technology experts are warning that we might need to be on our toes once the U.S. starts switching to daylight-saving time earlier than usual.
The switch is to come in 2007, in keeping with a law President George W. Bush plans to sign Monday extending daylight hours as an energy-saving measure.
One thing it might mean is that your VCR or DVR may record shows an hour late. It may also affect cell-phone calling plans, especially if billing is based on what time calls are made.
As was the case with Y2K, there is disagreement over how serious the problem will be.
Some observers say any effects from the change will be small, since it only affects the time a device operates, rather than pose the risk of it crashing altogether.
Our whole notions about "time" is fundamentally flawed because we have to make 24 hours equal one day (not the same), plus all the jumps and changes needed to be made for timezones, daylight savings, etc.
What we should have is sorta like a Unix Timestamp, but have no correlation to actually days (if you tack on an extra second, the timestamp doesn't care, but you'll have to change the algorithm that processes the timestamp).
Not only do we lose days (when it's not a leap year) but we also lose seconds too - I used to work for a time and attendance and these 'leap seconds' used to screw things up (and probably still do).
Unfortunantely, we as PHP programmers have it easy (it's a high-level language, so a lot of things are managed for us). Low-level languages have to do this all themselves... must be pretty awful for them.
Alan Perlis wrote:A programming language is low level when its programs require attention to the irrelevant.