- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Admin
Actually, the sort of jobs where you need to coordinate with people around the world are generally the sort of jobs where you don't need daylight that much. They're mainly office jobs.
(Things like travel don't count, as while they're coordinated around the world, and daylight helps, they normally just happen in their own time anyway, not related to a '9 to 5' life)
The sort of jobs where daylight will be a real benefit tend to only have timing relationships locally - eg farming, building, road maintenance, schools etc.
As long as there's an overlapping time period (eg for shops, government services etc), it doesn't really matter if some work on a different 'work day' to others. In fact, having, for instance, schools run from 7am to 1pm and office workers work from 9 to 5 may actually help with traffic congestion etc.
Admin
Back in my day when we wanted to do diffs we'd take the new punch card and put it on top of the old punch card and hold it up to the light.
And we were happy.
Admin
Admin
...and this is why everyone should operate on UTC.
Admin
So... Given that the parameter is passed across as a string, why not simply add the standard color names to the list of cases and then new applications can use something sensible without breaking the old ones?
Just because you can't make it beautiful doesn't mean you can't make it easier to use.