One, merely having a monopoly is not illegal. You have to abuse your monopoly to be convicted under anti-trust. Two, the search market still has more than two players. Yahoo and Ask are still around, among others. And MS is unlikely to simply shutter Bing. They're more likely to sell it off to someone who isn't Google--like the aforementioned Yahoo or Ask. Bing is hardwired into too much stuff to simply shut it down.

Ok, that's clearly a terrible idea, since moving the clock forward is what causes major increases in accidents every year. But how about the opposite notion. Move the clocks back twice a year, and forward never. I bet a whole lot of people would support getting an extra hour of sleep twice a year! That extra hour of sleep is the only good thing about the whole deal. :)

A programmer who isn't familiar with the standard libraries that come as part of the core language probably isn't a programmer who should be paid. I can't even look at the docs for time(2) without seeing mention of localtime(3) and gmtime(3). And similar for pretty much every other language I've used in the last dozen years.

And this is why I had trouble deciding how to vote. I'd prefer it to either be eliminated or extended to 100%. But I don't have a strong preference between those two.

Actually, if you go fast enough, you don't need life-extension. The stuff you left behind may be 50,000 years out of reach, but you might only have experienced a couple of dozen years.

Unfortunately, we're probably at least as far from the necessary accelerations (and cushioning) as we are from the necessary life-extension techniques, so it's probably a moot point, but I value completeness. :)

You realize this makes no sense, right? DST is only in effect from March to early November. The time during winter is the same as it always was.

I'm no fan of DST, but lets try to stick to arguments that make a lick of sense, mm-kay? The fact that you used to come home before 4pm but no longer do (the only possible explanation for what you wrote) is hardly the fault of DST.

I wish he weren't already modded to five, because I *do* have mod points, and have rarely seen something so deserving of one. :)

Um, Arizona is in the Mountain Time Zone, so it's never on PST *or* PDT. https://en.wikipedia.org/wiki/File:US-Timezones.svg

A zone is a physical part of the planet. Whether parts of that zone happen to observe daylight time is irrelevant. Zones are defined in terms of the *standard time* they observe. Though I admit that parts of AZ may have to use a different setting for the TZ variable than other MT places, which somewhat undermines my original post. But officially, it's all one zone. Daylight time is a time, not a zone.

EST and EDT are times, not zones. ET may refer to the zone or the time within that zone, depending on the context, but there is no "Eastern Daylight Zone". Just an Eastern Time Zone.

time zone (n): a geographic region within which the same standard time is used.

(From Webster's on-line, emphasis mine.)

ATI Linux drivers have traditionally been crappy, but since they were bought by AMD, they've opened up a lot, and have been steadily contributing to the main kernel. The kernel drivers (as opposed to the proprietary Linux drivers) have been improving by leaps and bounds lately. Kernel 3.5 saw 3D performance improvements of over 35% with some AMD cards, and 3.12 is supposed to have a similar huge boost.

I don't know how they compare to the closed source drivers from Nvidia *or* ATI, but I'm currently running 3.10, and the in-kernel drivers are definitely working very well for me.

Phoronix on 3.5 drivers

Phoronix on 3.12 drivers.

West coast *zone* is US/Pacific. The actual clock time may reflect PST or PDT, but the zone doesn't change. I don't have to adjust my TZ= variable twice a year.

You do realize we're talking about a woman who's been dead for over a century and a half, yes? One who died while Queen Vicky was still middle-aged?

(Not that I disagree with you....)

Nope, Lovelace was her title.King was her married name. And, because of the peculiarities of these things, "Lady" would be properly attached to "Lovelace" in this case, but not to "Ada" (or "Augusta"). So, Ada, Lady Lovelace would be one correct rendering, as would Ada, Countess Lovelace, or Augusta, Countess Lovelace (though she seemed to prefer Ada) or Augusta Ada King, (with or without added titles afterwards), but not Lady Ada or Lady Augusta, and not Ada Lovelace.

At least, as far as I've been able to figure out. People more adept at the nuances of British nobility may be able to provide a more accurate assessment.

There was reportedly a huge jump in performance with the 3.5 kernel series (as high as 38% in at least one case), and a lot more work was done with 3.6 through 3.10.

No the reason to mention the NSA is that the NSA's hackery has been all over the news recently, so it's an obvious leap that many people would have made if he hadn't mentioned it. In fact, for all we know (reporting being what it is), it was a direct response to the question, "do you think the NSA is responsible?"