I'd expect it to work more like Google Voice, where instead of having a phone line for your cellphone that gets forwarded to your computer, you have a phone line for VoIP that gets forwarded to your cellphone, computer, and whatever else you want.

Yes, there most certainly is a reason to do so--to affect the balance of power between the parties.

If the election has runoffs (rather than immediately awarding the win to a candidate with only a plurality of votes) then voting for a third-party accomplishes that just as well.

What does being sick about the Republican party have to do with voting straight-ticket Democrat?

The answer is, "nothing." There is absolutely never any excuse whatsoever to vote "straight ticket" anything, except coincidentally because you independently evaluated the candidates for each office and your favorite candidates in each case happened to all be from the same party.

No, silly, they don't buy "cable service," they buy stock and politicians and end up with more money than they started with.

Why is it a big win for Intel? Regardless of how cool it is (and I think it's cool, and am maybe considering getting one -- especially if I can put normal Linux on it), Google isn't going to sell enough of them for anybody to care.

(I know this because no Nexus devices sell well enough for anybody to care... even things as comprehensively awesome as the Nexus 5 aren't marketed well enough to the dumb [m]asses to outsell the contract-carrier schmuck-phones like the Galaxy Note and iPhone.)

FYI, the Nexus 5 is GSM & CDMA, and works just fine on Sprint's network. The only reason it doesn't (or didn't -- maybe it's changed?) work on Verizon's network was because Verizon decided not to allow it, not technological incompatibility.

If you stuck me in front of a computer to mimic code someone showed me at 7, I'd have thought "okay, great, when is recess?"

Really? I got stuck in front of a computer at about that age (it might have been 8 instead) and learned how to use LOGO to draw pictures and Hypercard to make moderately-interactive "stacks," and I thought it was pretty cool.

I even took programming in high-school and just absolutely hated it. Sitting in front of crappy macs writing boring basic...

Well there's your problem: you had boring platform (and probably a shit teacher too).

Ask yourself this question. Should I use a standard protocol with tons of tools an an ecosystem to support it or should I use a totally custom protocol to handle everything?

Yes, you should use the standard protocol... which means you should not be shoehorning printer control stuff into some custom monstrosity layered on top of HTTP!

...except that lpstat etc. already exist, so there wasn't a need to do that in the first place.

What does a GUI have to do with a web server? You could write a graphical front-end to lpstat (etc.) without bothering with the HTTP and whatnot and it'd probably turn out better.

"The rest of you can go on ahead," they said, as if we mighty fly on despite the loss of a teenager.

I bet it would have given the airline an excuse not to refund the rest of your tickets, if you had missed the flight.

There's an easier way to think of it: consider how much space 500 houses take up. Now consider how much space one windmill takes up. The windmill isn't very big compared to the houses, is it?

Also, consider how much farmland it takes to feed the people in those 500 houses. Then consider that you can stick a windmill in the middle of a field and it only displaces crops in the area occupied by its tower's base (plus some room for maintenance and maneuvering), not the width of the blades.

If you take the example of a small town and plop a single windmill in Farmer Bob's cornfield, you can power the whole town. If you put a windmill in Farmer Joe's soybean field too, you can power that town and the next town over. If you put a few windmills near every small town you might (I haven't done the math) end up with enough leftover power for all the big cities.

The point is, 80k windmills sounds like a lot, but it really isn't.

The only trouble is that Netflix doesn't necessarily know who my ISP is. Maybe one day I'm watching it at home on Comcast, then another day I'm watching it on my phone with T-Mobile, then another day I'm watching it using a restaurant's wi-fi. For it to be "fair," Netflix would have to keep track of which ISP everybody was connecting through at any given moment and then pro-rate the surcharge.

The very reason Truecrypt died was because they couldn't trust future compilers for Windows.

[citation needed]

Or it could be church goers on the whole have a better attitude to marriage. Like 1cor13, exposing the selfless virtues of love, and the many endorsements of sticking with the partner you have chosen.