Requires MacOS 10.4.0 or newer (if you try to run it on an older version, it will now display a dialog box instead of just crashing.)
I expect those of you in the western hemisphere to all be running this in full-screen "countdown" mode at your parties tonight!
Update: But I see that all my Linux boxes just spat out this syslog:
Dec 31 15:59:59 cerebrum kernel: Clock: inserting leap second 23:59:60 UTC
(Nothing logged on OpenBSD.)
According to Bulletin C of the International Earth Rotation Service:
The sequence of dates of the UTC second markers will be:
2005 Dec 31, 23h 59m 59s 2005 Dec 31, 23h 59m 60s 2006 Jan 01, 00h 00m 00s The difference between UTC and the International Atomic Time TAI is:
from 1999 Jan 1, 0h UTC, to 2006 Jan 1 0h UTC : UTC-TAI = - 32s from 2006 Jan 1, 0h UTC, until further notice : UTC-TAI = - 33s
In other words, the year will be longer by one second just before midnight, new year's eve, GMT. That's 4:00 PM PST, 7:00 PM EST.
Please take that second to just go nuts. One second. All to yourself. Use it wisely.
I also recommend reading Paladin of the Lost Hour by Harlan Ellison.
The reason leap seconds are needed is because there are two different definitions of the length of a second: the solar time that you use every day, where the there are 60×60×24 seconds per day (meaning the length of the second varies as the speed of rotation of the earth varies) and the engineering definition, where a second is defined as 9,192,631,770 oscillations of a cesium-133 atom: the atomic clock.
Mostly humans are concerned with time as it relates to the comings and goings of the Sun, but you need to be a little more accurate if you expect that satellite to be where you left it, so you need the length of your unit of measure to not change. That would affect everything else, too, since the official definitions of other units like the volt and the meter are based on the second. (You thought the meter was still defined by the length of that platinum-iridum bar in France, didn't you? Get with it!)
So the time system we use day to day, UTC ("Coordinated Universal Time") is a compromise between solar time (UT1, "Universal Time", formerly GMT, "Greenwich Mean Time") and atomic time (TAI, "International Atomic Time"): in UTC, seconds are of a fixed length, but leap seconds are periodically introduced to prevent "solar" noon and "atomic" noon from drifting away from each other.
But really it's all a lot more complicated than that!
And then of course there was the switch from the Julian to the Gregorian calendar at various dates (mostly) between 1582 and 1752, in which 4-Oct-1582 was immediately followed by 15-Oct-1582, in order to correct for the inaccurate leap-day-insertion algorithm in the Julian system, which over the centuries since its introduction had caused the calendar to detach from the observed equinoxes by ten days.
It can be really hard to know what time it is.
Top ten spam subject lines:
- Donald Trump Wants You - Please Respond
- Double Standards New Product - Penis Patch
- Body Wrap: Lose 6-20 inches in one hour
- Get an Apple iPod Nano, PS3 or Xbox 360 for Free
- It's Lisa, I must have sent you to the wrong site
- Breaking Stock News** Small Cap Issue Poised to Triple
- Thank you for your business. Shipment notification
- Your Mortgage Application is Ready
- Thank you: Your $199 Rolex Special Included
- Online Prescriptions Made Easy
I thought I hadn't bought much new music because I spent four or five months going through my old music and rating every song, and I wasn't actively seeking out new music during that period. But that doesn't seem to have had the throttling effect I expected.
As in previous years, a few of these were released earlier than 2005, but that is when I discovered them, so I'm allowing a little slack. In only approximate order of favoriteness, here is my year-end wrap-up.
( --More--( 9%) )
All I'm able to understand from Shark is, "yup, spending all your time pushing bits to the screen." Shark seems to suggest that the Quartz way is faster, but Top disagrees. Grumble.
Is there an Aqua way to draw a 1bpp bitmap with a given fg/bg, besides dropping all the way down to CGContextFillRect? Because (as you can see in drawRect) that's a fuckin' pain in the ass when you're dealing with foreground and background colors that can have different amounts of transparency (e.g., making it continue to work when the numbers are a "hole" in the window.)
