Like I said, within the context of UTC, leap seconds should not be accounted for. UTC is an arbitrary time system and can have both static rules, like leap years, and dynamic rules, like leap seconds. Every conforming UTC system should operate like the leap second never occurred. All interval calculations will remain correct under those conditions.

Such a time system should not be used for "real" time sensitive systems like celestial mechanics, crypto certificates, or medical devices. There are better time systems for that. Accordingly, mapping between UTC and some other system will not necessarily yield a one-to-one mapping.

unless your problem domain needs to store the occurrence of leap seconds, when they appear are irrelevant. Regardless of when they appear, time monotonically increases. There is simply a skip. By its nature, the skip is meant to be invisible. Any time system based on UTC shouldn't try to factor in leap seconds while doing arithmetic because every UTC system will see that leap second as never existing in the first place. Systems that involve motion like satellites or systems that involve crypto should use an alternate time system and map between the two.

I am optimistic this strange concept will be overturned in good time, perhaps even by the Ninth Circuit, upholding the district courts decisions in Vernor and Augusto in pending appeals.

I think you'll be waiting quite a while. Google Blizzard vs Glider for a taste of what the courts have to say about EULA's. You might also want to pop over here for more information about the Psystar/Apple battle.

Really, what good are the dots? It doesn't prevent someone from looking over your shoulder. A villain can just look at your keyboard while you type. Maybe its of some use on a public terminal, but I check my six before I type in a security password anyway.

The obscured pass(word|phrase|key) has been the most aggravating while trying to type in a strong WiFi password on an IPhone (pre 2.something-or-nother update). Try it. The aggravation is pure ecstasy. Luckily Apple has wised up and shows you the last character you've typed at least.

And how about disabling paste from a security box. You can't verify your passkey when you're troubleshooting. A determined villain can get to it anyway, especially if they have access to your machine. Don't even get me started on the 'super' secure entry boxes where you can't paste TO the security edit box.

I don't think that'll work. You're setting up a system where more unscrupulous individuals could make a mint. If there's a big demand for a $250 laptop in richer countries, someone is bound to try to capitalize on the difference in price. What will happen is that those free or near-free machines going to third world kids will be stolen or 'lost'. They'll wind up on the grey market for $200 or thereabouts.