Well, your argument so far has been little more than "State bad" which has nothing to do with the specific topic of renting homes. It's difficult to make ANY sort of counter-argument to that. So, consumer protection laws are good, so "State not bad?" How are we to divine from your current stated position where you draw the line?

Split the difference, it's actually remarkably close to the average of your number and his: 22.5 years, with the first kernel release on October 5, 1991.

I'm just double checking: You did know I was being sarcastic? Text isn't the best medium for that many times, but I couldn't help myself.

I don't get the whole nerd stratification anyway. I play Borderlands 2 (A "bro" game, as someone else called it, huh? Well, it's still fun.) regularly with an astrophysicist and her seismologist husband, etched my first printed circuit board at age 12, hacked on code that talks to spacecraft on Mars, written (admittedly kind of crappy) videogames, and done all manner of tech projects just for kicks. If anyone wants to question my nerd cred, let them. I do what I like; I couldn't give 2 shits what other people think.

Thank you, Ambassador Nerd, for speaking for all of us in our time of need.

Also, this: "The coordinates:When the coordinates are added to the fact that the photoâ(TM)s exif data does not match the Google coordinates or any other coordinates for Diego Garcia that are posted online, but is still within the boundaries of Diego Garcia, it proves that no one just pulled those coordinates off the web. It helps confirm that this was not just a hoax because the coordinates are exact to wherever on Diego Garcia the Iphone was when it took the photo."

Unless you're past day 2 of an "introduction to GIS" class, in which case, getting the lat and lon of any place in the world, not just "published" coordinates, is a trivial task. Really, the new Google Maps make this too easy.... Look!
https://www.google.com/maps/@-...
https://www.google.com/maps/@-...
https://www.google.com/maps/@-...

Check those URLs...It's SO hard to get lat and lons for Diego Garcia.

Then this: "Exif canâ(TM)t be rewritten with common software, it can only be added to in fields such as image credits with some advanced applications. It can be erased as well but NOT CHANGED. Photos with the exif intact will hold up in court. If the Exif is hacked and this is not real, the CIA or a really good hacker did this, which I doubt, Iâ(TM)d say itâ(TM)s probably real."

I don't have to go into why this is ludicrous with this crowd, do I? The only claim I'm not sure about is intact EXIF holding up in court. I hope to hell not, but I've seen dumber things.

If it makes you feel any better, my first reaction on seeing this was "Hmm, let me read the comments and see if anyone has a fix or workaround, and if not, hell, I'm sitting around in hospital bored out of my mind. I'm not familiar with the Xorg code tree, but this would be a great thing to spend a weekend to get my feet wet." I'd like to think that there were at least a few of us out here in the same place (well, maybe not the hospital part ;-)), leaving chuckleheads to post before the people who rolled up their shirtsleeves could say anything. In 2014 I don't consider /. to be quite the locus is used to be for open source developers it once was, but there's still a bunch here.

Glad to see there is a fix that might work already.

Yes, we don't know how to get to 300 km/s now.

Actually we have a pretty good notion how to do 300km/s and even faster, but when we have manned space programs that regularly have to beat the sofa cushions for change to keep afloat, the cost needed to fully develop something like that is so far out of whack with reality that you might as well wish for magic aliens to whisk you away because the odds are about the same.

Standards

Yes, and I would be right. ;-)

soundex

Levenshtein distance

Hamming distance

More like this, can't be arsed to go looking them up, though. Those were three I knew off the cuff.

Unless the Republicans start doing some coalescing like right NOW and get behind that, I think absent a significant event between now and November 2016, Hillary's odds look very good.

The Republicans will not get a president again until their primaries are more than "who can rush to the right the fastest?" The winner of that will have to choke on their own words in the general election and the swing voters who actually decide elections won't like the things said to garner the nomination nor the backpedaling to appear more middle-of-the-road once the nomination is sewn up.

What are they going to after Hillary about? Bengazi? The numbers show that didn't affect her approval at all: hardly anybody who railed on about that is anyone that up to that point would've voted for her anyway. Lewinski? Ancient history. Yes, let's remind the voters of the late 1990s when the economy was good and the federal budget even got balanced once or twice. Whitewater? Almost as much time between now and then as elapsed between Mossadegh's ouster and the Iran hostage crisis and practically nobody saw that connection. In the average American voter's mind, those stories might as well be written on papyrus in cuneiform.

And no, I'm not a Hillary supporter. Just a member of the reality-based community. :-)

If he's the judge, this would be a problem. Since (making a fairly safe assumption) he's not, there's nothing wrong with rooting for/against someone in a case for extralegal reasons.

You could delete the word "mental" from your last sentence and it would still be pretty accurate.

In the era this was written, compilers didn't optimize worth a damn. I totally agree it's not elegant but Duff wrote that to solve a problem that the "elegant" solution just couldn't solve. Even still, Duff's device isn't really that hard to understand if you're familiar at all with loop unwinding, especially if you've ever done it in assembler (and C isn't that much more than a semi-portable assembly language). Sometimes you have to write ugly things because the pretty structured/OO way just doesn't cut it.

Even today, "optimizing" compilers sometimes don't. On the other hand, this doesn't occur as often as some people think. I operate on a policy of "trust your compiler, until you can't."

And they don't ice and plow roads during snow worth a good golly damn. We took an Arizona to Ohio road trip in December and there was a biggish snow storm moving into Illinois, Indiana and Ohio. About the time we reached Effingham. Illinois plow trucks on I-70 were pre-positioning themselves every 5 miles even though the storm had not hit yet. We hit Indiana and there was nothing. The storm actually hit when we got to the western edge of Indianapolis and it took 6 hours to get to the Ohio border (usually a 2 hour journey). The roads were terrible, there was no salt down, and I didn't see a plow truck until about 50 miles in after the snow started. Also, it seemed like every bridge seam in Indiana was not graded with the road. Almost every time I got on or off a bridge I thought I was going to lose a wheel.

When we hit Ohio, despite the storm actually getting worse, the roads were clear (just wet) and I constantly saw the trucks. Because of Indiana though, I was too exhausted to make it to my destination (Canton) and had to stop just west of Columbus. 6 hours of white knuckled driving a 30' RV in a snowstorm kind of takes it out of you. :-)

Also, if you ever drive west, Oklahoma highways suck too, ESPECIALLY around OKC. To hell with that city.