getting reelected by convincing the populous that they will get blown up if they vote for the other guy

Gee, when you say it that way it almost sounds like a threat...

A "Yankee" means anybody from a place north of the Mason-Dixon Line and south of Canada (or sometimes, to ignorant foreigners, it's a slang term for "American").

No, he's referencing the idea that authorities would rather shoot the plane down than let it crash into something important.

Wait a minute. How was APD already there to search for bombs? Their standard crime response time is at least two weeks.

No, the center of gravity isn't high enough that it would lead to a roll. A slide or a spin is more likely.

Lifting the inside rear tire is normal behavior for a small FWD car... but under racing conditions, not going around a freeway on-ramp!

It also means that, instead of just being charged with "distracted driving," the perp can be charged with "texting while driving" and "driving erratically" and "distracted driving," which adds up to triple penalty (including jail time!) unless he gives up his right to trial and allows himself to be railroaded into a "plea deal."

I can surf and ski in the same day too. ... My $130K/yr in Atlanta goes a long way.

You can surf and (snow) ski on the same day where near Atlanta?

Let's just enforce existing laws and get dangerous drivers off the road. THERE IS NO RIGHT TO DRIVE. If you are a dangerous driver you can and should be taken off the road.

A coworker of mine was hit a couple of weeks ago by a woman who, after fleeing the scene, was discovered to have had caused FOUR injury accidents in the trailing 12 months, had been dropped from her insurance two months prior, and who, despite all of that, had not had her license suspended, and was not even ticketed for leaving the scene of the accident she caused with my coworker.

It's our complete unwillingness to hold people accountable for their actions that has created the need for EVAN M0AR government regulation to "protect us from ourselves."

People who are incapable of driving shouldn't be driving. Period.

Do you have an example?

To my naive understanding, the output of any encryption should appear random. Then, encrypting anything random should also be random -- the only effective difference should be that you now need (some mathematical function of) both keys to decrypt it.

I could accept that the above could be wrong, but I'd love for you to explain why it's wrong.

Yes, it is, at least in some places.

AT&T has a 150GB cap on DSL and UVERSE, while our local cable company has a 250GB cap on their DOCSIS Internet.

He could crash the Millennium Falcon, let people teleport from Coruscant to Tattooine, and make Jedis be able to bring people back from the dead (and retcon it so that they could always have done it, making Vader's origins make even less sense).

Then you have Khan. Perfectly good movie. And you had nerds raging because herpaderpawhiteguynamedKhanNoonienSingh.

No, we had nerds raging because the damn thing had plot holes big enough to drive a fucking starship through (except you don't NEED to drive a starship anymore because we can just BEAM TO GODDAMN Q'ONOS now...)!

If Dish continues to exist, they will continue to need people to install the dishes -- whether they're outside contractors or Dish employees. Either way, you could still continue installing dishes.

If Dish went out of business (and DirecTV's sales didn't increase to take up the slack) and demand for satellite installations decreased to the point where your company went out of business, well, that's the owner's fault for not diversifying.

Regardless, concern for your well-being as a a Dish contractor is not a reason to disregard Dish's law-breaking!

AMD64 would never have reached the market unless Microsoft had ported Windows to run on it.

I don't believe that. Since x86-64 is backwards-compatible to 32-bit OSs, It would have been just fine for AMD to release it running 32-bit Windows. It was still as faster processor, after all, whether it was running in 64-bit mode or not.

Then customer demand would have forced Microsoft to provide x86-64 support, Intel's wishes be damned.

In fact, the way I remember it, that's pretty much what happened. The first x86-64 chips came out in 2003, but Windows XP Pro 64-bit didn't come out until 2005. Even then, and most desktop users with 64-bit CPUs continued using 32-bit XP and didn't switch to 64-bit Windows until Vista (2007) or even 7 (2009). (I distinctly remember dual-booting 64-bit Linux and 32-bit WinXP for several years...)