Text isn't media? You've got a really bizarre definition of media! Even accepting that the word now has a separate meaning aside from its meaning as the plural of medium, the phrases "mass media" or "mainstream media" have always included newspapers and books. Which are, generally, text.

Most of my video, but almost none of my music. But I'm not sure how those two compare percentage-wise. And what about books? Do those count as media? I certainly don't stream even e-books. (Except, arguably, through O'Reilly's Safari program, which might count.) But then there's news media, which is almost entirely streamed. If you count visiting web-pages as streaming.

Honestly, I'm really not sure. Depending on how I measure, I might be able to come up with a number anywhere from 20 to 80.

Some meta-analysis of the actual study, along with some examination of how the media has generally thoroughly misrepresented the study, is available at Language Log.

A quarter plus a tenth of the test results were shown to be related at all (not in whole, but at all) to heritable traits. The grand total overall was just under 16% (a half of a quarter, plus a third of a tenth).

Now, I don't know about you, but I wouldn't describe 16% as "largely". I'd describe 16% as "partly", or "mildly", or "somewhat". But of course, reporters for Nat'l Geo and The Independent and the like aren't big on math.

It's still an interesting and intriguing study, of course, but so grossly misreported that it boggles the mind. We need a better grade of chimpanzee writing science articles for the general public! :D

That's nice if you're working alone, and never have to deal with other people's code, and don't have to fight management tooth-and-nail for any change larger than the bare minimum required to fix a specific problem.

Difference? There is no difference! I don't indent! I mark the beginning and end of blocks, and the code is automatically indented to match. I can, with some difficulty, defeat this mechanism, but I can't think of any reason why I'd want to.

Thank you. Not that I needed your permission, but I shall indeed continue to consider it an idiotic design.

Agreed. However the fact that it doesn't noticably harm my productivity doesn't mean it's a good feature.

In any case, we're discussing its potential use as a teaching language here, and people who are just starting to learn to program are, pretty much by definition, not good programers. So its impact on not-good-programmers is still very relevant.

There are people who have survived jumping out of "perfectly good" airplanes without a functioning parachute. Doesn't mean you should take up skydiving-without-a-parachute as a hobby. :)

There's a reason cases like you mention make the news: surviving a crash at those speeds is an impressive and newsworthy feat. (The reason this case made the news was not the fact that the driver died, but the fact that a Tesla was involved. Otherwise, it seems like a pretty unremarkable story.)

And I bet he was buckled in. Remaining in the vehicle during a high-speed crash greatly increases your chances of survival. Exiting a vehicle at 100+ mph is generally contraindicated! (Tip for future reference.) ;)

Nope. My editor takes care of indentation for me, in every common language except Python, and when I have to deal with a batch of code written by someone else, I run it through indent(1) first. So, in fact, it's just the opposite: when the indentation doesn't match what I expect, I know there's an actual problem in the code!

With Python, on the other hand, I'm actually more likely to have an error in the indenting, because there's no easy way to see how many blocks I'm terminating when I outdent by an arbitrary amount. Which is a real PITA when you're refactoring.

Of course, things may be different if you're using crappy tools. But professionals shouldn't be using crappy tools.

No, they're tools to make my job easier. Whatever the historical reason for them may be, they benefit the programmer! They make me more productive.

Now, I'll grant that Python is a remarkably good language despite its horrible flaw of relying on indentation. And many of its good features also make me more productive. But that doesn't mean that relying on the indentation isn't a horrible flaw.

Disagree. Large-scale habitats/SPS/O'Neill Colonies have always been the best option. No huge gravity wells to deal with, since rotation provides your G's, and, while they are extraordinarily expensive, they cost nothing compared to a full-scale terraforming effort, and can provide a shirt-sleeve environment in basically no time flat. The one remaining big knock on them was the issue of radiation shielding, and now, that may be solved.

Yup. Knotweed is fairly common in the area, but there's none in my back yard.

Indeed! In our back yard, they are losing the battle against the ivy and bamboo! :)

I do know, but nobody's complaining. I only know because one time, when a guy changed desks, he complained that it was too cold at his new location, and the building maintenance guy came up and tweaked his vent, which fixed the problem, and since then, nobody else has complained.

Which doesn't really leave me with anything to chose on this poll, but oh well. Par for the course. :)

Would violate clause six of the Open Source Definition (and the Debian Free Software Guidelines): No discrimination against fields of endeavor.

I find quite the opposite. The simplest case is one user, and a "distributed" VCS is clearly the easiest option in that case--no central repository needed, no environment variables to set, or separate paths to worry about. Just say "init", and you're off and running. (At least with Mercurial or Git, the two DVCSes I have experience with.)

With more than one user, it's slightly more complicated, but not enough to worry about. It all boils down to the distinction between "save this change" and "share my changes with my co-workers". Having those as separate commands really isn't that confusing, and once you're used to it (which should not take long), you'll have a hard time remembering how you lived without it! And that really is the entire difference, fundamentally, between distributed and non-distributed VCSes.

(Most of the things that are great about Git are unrelated to the distributed/non-distributed aspect, or at best tangential to it. For me, the big wins of either Git or Mercurial over, say, Subversion, are how much better/faster/easier/more powerful branching is, which doesn't really have to do with being distributed or not, and how much faster the whole thing is, overall, without all those network round-trips, which does.)

I started out somewhat skeptical, like you, but after my first pilot project, using Mercurial, I was a complete convert! YMMV but it Works For Me(tm)! :)

That's because TFS is the usual slashdot idiocy, and TFA is simply bad reporting. This report tells quite a different story:

...and...

So yeah, I'd say it sounds like a lot more than I'd expect was being shared.