But I just had to create a web service to CALCULATE THE LOCAL TIME because Google Chrome -- which seems to be a pretty mature product -- has some sort of catastrophic time zone bug that somehow causes its time zone handling to get confused.
The debugger console shows the following ridiculous output (obviously today at 5:44 EDT):
> new Date()
Mon Apr 09 2012 10:44:42 GMT+0100 (Eastern Standard Time)
A quick search of the Chromium bug database reveals lots of users reporting bugs that are probably caused by this.
P.S. Even as I write this, all the timestamps on the Blogger edit screen show incorrectly...
Update 2012 May 16:It's a bug in how Chrome deals with the TZ environment variable on Windows. See the Chromium issue.