There is more than one way to skin a cat. And if your particular project has your arduino always connected to a PC, this may be exactly what you want.

Back when we had an electric hot water heater we just built a metal reservoir into our wood stove and plumbed it into line with the cold water feed to the heater. The heater still functioned normally, but whenever we were heating with wood the input water was already at temperature and the tank would only have to maintain (or slightly heat) the input water.

Its a start, and not hard to hack into your existing setup. What we had was pretty simple, but knocked a huge chunk from the electricity used by the heater. I don't think you'll find a good way to use paper/wood as the primary source of heat, but as a secondary that does most of the lifting you'll find a lot of options.

You're not as reliable of a repeat customer, and you probably aren't willing to pay out the nose for content like sports fans are.

Given the US government has given themselves the ability to perform wholesale monitoring of communications (Room 641A is the easiest proof to point to), we must also posit that there is an invisible Bigfoot, and that he frequently watches people masturbate.

No, its just interesting. The fact it isn't a rounder number makes it a curiosity of how they arrived at $27.63 exactly. Why not $27.50, or $27 or $28. What difference do those few cents in compensation make in the mind of the bill authors? Is it just the hourly wage of someone making $X a year where X is actually a round number? Was it chosen because of its point on the distribution curve of typical IT worker compensation? Did the sponsors of the bill sit late into the night, debating adding and removing provisions of the bill along with cents to and from the hourly rate cited? Does whoever paid congress for the bill pay their IT folk $27.64/hr?

Y'know, I think that if The Simpsons was the worst kind of programming we had to deal with, I'd call it a victory. Sure they've lost their charm for a lot of people, but even if their comedic voice has changed it still is a decent show with amazing production value.

As someone who recently came of voting age, its kind of jarring to see our government function like this. I'm used to seeing the public interest railroaded to benefit a corporate interest, a corporate interest railroaded to benefit a different corporate interest, but I've never seen the public interest held above a corporate interest like this. Hell, they didn't even decide anything and I'm excited to see this, I know they would be able to jam up the merger eventually, but right now they've just presenting findings.

Is this what democracy is supposed to look like? I fucking love it. Shit, even if government decisions continue to be against the public interest, I'd be psyched if they just had the balls to admit it with reports like this. That would be a huge step forward from the bullshit "someone is making money, therefore its good, fuck off" level of analysis I'm used to seeing.

You took the words from my mouth, the last few days the only impression I've been getting from AT&T is one of a crybaby.

My favorite part of TFA was Sprint's comment, they're basically using fancy words to point and laugh.

Really? Come on; how lazy can you get?

The city I live in started recycling pickup a month or so ago, I just put the recyclables list up on the fridge. Problem fucking solved.

Pretty well actually, too bad our congress is needlessly squeezing it dry to make up for gaps in the budget.

In this case specific case, sure, why the hell not? Its DNS, and you've found that you're in an impossible state. What else are you supposed to do? Even if the process hasn't been compromised, by the nature of the assert you've failed and don't know how to recover. Do you want to keep on serving DNS, assuming the process is in a state where it is fine to keep on trucking? Or maybe enter a do-nothing failure mode, which is just as useful as going down hard, but with the added bonus that the process is experiencing unknown problems and you want to rely on it to contain itself properly.

And I didn't say it was a substitute for proper exception handling, just that you're going to let exceptions you haven't prepared for to bring the process down, rather than blindly swallowing them. Or do you think this is good code:

try:
        foo()
except Exception, e:
      pass # EVERYTHINGS FINE, GO BACK TO WORK!
bar()

So your code, that you make sound more important and/or safety related than DNS, doesn't have any failsafes? Really?

Thanks for the clear explanation.

Very true. Its funny, that this morning I had applied security patches to a debian stable box and thought "hmm, looks like BIND is getting fixed, wonder what thats about" before this even got posted to slashdot.

YEAH! You're so right, just because privacy implications of using service X are well understood means you have NO excuse not to understand the privacy implications of Y. Even if X makes it clear by the inherent nature of X, and Y hides it from the user as much as possible, there is exactly no difference.