The clock display is nice but not a killer for me. Here&There time comparison in different time zones is the best I have seen. Full page calendar with multiple months is very simple but works great for me.
This is becomes my favorite site for time/date related stuff.
Time.is
101–108 of 108 posts
Re: Time.is
#102Earlier quoted context omitted.
You also need to make sure your IANA tzdata is updated to account for this. I think this leap second was first added in tzdata2012a, but I'd have to check: ftp://ftp.iana.org/tz/data/leapseconds
If you use Unix time, you don't have to care: http://en.wikipedia.org/wiki/Unix_time "Unix time, (...) is (...) defined as the number of seconds elapsed since midnight Coordinated Universal Time (UTC) of Thursday, January 1, 1970 (...) not counting leap seconds "
You might not be able to ignore leap seconds if you are interacting with an external system (software or hardware) / API that expects actual UTC. General rule applies to everything.. know your system, know what systems you are connected to, know what standards you need to adhere to.
Microsoft apparently rejected the idea of using leap seconds because Windows just isn't accurate enough:
The W32Time service uses the Network Time Protocol (NTP) in
Microsoft Windows Server 2003, in Windows Server 2003 R2,
in Windows Server 2008, and in Windows Server 2008 R2.
...
The W32Time service cannot reliably maintain sync time to
the range of 1 to 2 seconds. Such tolerances are outside
the design specification of the W32Time service.
Re: Time.is
#103Earlier quoted context omitted.
If you use Unix time, you don't have to care: http://en.wikipedia.org/wiki/Unix_time "Unix time, (...) is (...) defined as the number of seconds elapsed since midnight Coordinated Universal Time (UTC) of Thursday, January 1, 1970 (...) not counting leap seconds "
You might not be able to ignore leap seconds if you are interacting with an external system (software or hardware) / API that expects actual UTC. General rule applies to everything.. know your system, know what systems you are connected to, know what standards you need to adhere to. Microsoft apparently rejected the idea of using leap seconds because Windows just isn't accurate enough: The W32Time service uses the Ne…
Do you happen to know "an external system (software or hardware) / API that expects actual UTC"?
Unix/Linux computers don't, Windows computers don't, GPS doesn't:
http://en.wikipedia.org/wiki/Global_Positioning_System#Timek...
Re: Time.is
#104Earlier quoted context omitted.
You might not be able to ignore leap seconds if you are interacting with an external system (software or hardware) / API that expects actual UTC. General rule applies to everything.. know your system, know what systems you are connected to, know what standards you need to adhere to. Microsoft apparently rejected the idea of using leap seconds because Windows just isn't accurate enough: The W32Time service uses the Ne…
Do you happen to know "an external system (software or hardware) / API that expects actual UTC"? Unix/Linux computers don't, Windows computers don't, GPS doesn't: http://en.wikipedia.org/wiki/Global_Positioning_System#Timek...
GPS doesn't, but GLONASS does:
GPS Time is designated as being coincident with UTC
(USNO) at the start date of January 6, 1980 (00 hours).
GPS Time does not count leap seconds, and therefore an
offset exists between UTC (USNO) and GPS Time (at this
date in April 2007: 14 seconds).
Unlike GPS, the GLONASS time scale is not continuous and
must be adjusted for periodic leap seconds. Leap seconds
are applied to all UTC time references as specified by
the International Earth Rotation and Reference System
Service (IERS). Leap seconds are used to keep UTC close
to mean solar time. Mean solar time, based on the spin of
the Earth on its axis, is not uniform and its rate is
gradually changing due to tidal friction and other
factors such as motions of the Earth's fluid core.
This is the best overview I've seen of all the pros/cons with regard to UTC and whether leap seconds should be abolished:
http://www.agi.com/downloads/resources/user-resources/downlo...
Basically, much in the same way that we all despise DST (or date differences between Julian/Gregorian calendars), a certain part of me wants to know, if we humans last on this planet long enough, that our descendants thousands of years from now won't look back and curse at us for being idiots and deviating from celestial time.
Re: Time.is
#105Earlier quoted context omitted.
You might not be able to ignore leap seconds if you are interacting with an external system (software or hardware) / API that expects actual UTC. General rule applies to everything.. know your system, know what systems you are connected to, know what standards you need to adhere to. Microsoft apparently rejected the idea of using leap seconds because Windows just isn't accurate enough: The W32Time service uses the Ne…
Do you happen to know "an external system (software or hardware) / API that expects actual UTC"? Unix/Linux computers don't, Windows computers don't, GPS doesn't: http://en.wikipedia.org/wiki/Global_Positioning_System#Timek...
A lot of RFCs, the first that comes to mind is the timezone seconds offset in DHCP replies and time fields in openpgp standard.
Google probably knows a lot more:
UTC site:rfc-editor.orgRe: Time.is
#106clever url folks.
I wasn't being sarcastic guys. I meant that, it's pretty clever.
Re: Time.is
#107Earlier quoted context omitted.
Mainly Win 7. Otherwise Mac OS X. Sometimes Win XP, and very rarely Ubuntu. But I almost never have a terminal open (and don't have a shortcut for that either) whereas Firefox almost always is. So I'm just 1 click away rather than 4 characters away. You taught me something though (I highly prefer typing on a keyboard than using a mouse or, worse, a touchpad) and I wish I had to spend more time in a terminal.
Why not? I usually have a terminal open for irc / bc -l / git / checking the headers of pages with curl -I, pinging things, WHOIS lookups, wgetting files, etc etc etc.
I'm no developer, so I never have to use the terminal. But now that you mention how you use it, I'll probably give it a try.