I'd wager they'll draw far less - the demand for long battery life in the mobile space has made its way into desktop hardware. It's amazing what the engineers can come up with when they actually try to reduce power consumption. Today's crappy outdated system might have been a high-spec machine five years ago; unfortunately, that was near the peak of our "throw more electricity at the problem" phase in hardware design (Prescott, anyone?).

...recent Western culture has shown that a higher percentage of men have become fathers in the past few generations than before that.

As more and more males become adjusted to the instant high of popular culture, we'll just return to the times when a tinier percentage of men were having all the babies.

Marriage is already on a decline, in some races good husbands are hard to find so women have more biracial babies, and the powerful men won't stop spreading their seed.

Does it matter to me if the weak male class doesn't have kids? Hell no -- and they make good employees, too. Maybe better ones.

Because the interface hasn't been defined yet. They're making experimental functions with no standard interface, so the prefix indicates it's not designed for production use yet. Look at CSS gradients, and even border-radius: until relatively recently, there were multiple different ways to achieve the same effect depending on the browser and that vendor's prefix: -moz-border-radius-topleft vs -webkit-border-top-left-radius (the latter won out and is now the standard, sans prefix) further complicated by non-circular radii; see http://www.css3.info/preview/rounded-border/. And that's dead-simple compared to gradients - look at the output to get something cross-browser here

This is definitely a real problem. Too bad the proposal doesn't actually solve it. While it goes in the right direction by asking for support of non-prefixed properties from day one, that effectively ensures that the first implementation out there defines the interface, which can easily leave a huge mess behind (again, see webkit's gradient interface). The proposal's author is aware of this and dismisses it as a non-issue, which is incredibly ignorant.

Congratulations - you give a damn! You're well ahead of most geeks.

And when dealing with others, that's all it really comes down to. It either appears that you care or that you don't care, and the former tends to go a long way.

$200,000? In California? Try $2,000,000.

But yes, point taken.

I know you're commenting with extreme sarcasm, but I do think that's actually the case. An elected official using their power in a manner designed to undermine the Constitution isn't technically treason by most definitions, but I feel it should be punished just as severely.

Neckbeard like that? No doubt :p

You can perform that same hack with an extension cable.

Tweet something containing "iPad", "iPhone", etc. Wait about ten seconds. Check your @replies. It's definitely a real problem.

It's hard to detect whether this is being done by automated spamming tools or humans. We have a dashboard at our office that streams mentions of our company on twitter, and we'll often see spurts of a human spamming the link to their donation campaign at celebrities asking for handouts.

To be fair, you may want to solve that problem as well, but it sounds like Twitter is just trying to silence the bots.