It's basically the same situation that arises when a developer tries to talk to the business. Many developers just don't know how to speak in plain english (or language of choice) when it comes to describing technology. As a result, developers don't seem to "get the business" and the business doesn't seem to "get technology". Enter the business analyst: the BA is the interface that has the ability to speak both technology and business.
In the case of the media, they seem to lack really gifted technologists who can also convey the *meaning* of the science without losing their audience. Let's face it: most information consumers want the basic facts as well as the bit of novel "shiny" associated with the science. Sometimes the journalist has to understand the science *and* it's place so that they can come up with the novel bits for the audience. It takes a gifted journalist to do that, and many, obviously, fall short.
This isn't news. This is how it's done. Ignoring the fact that it's about degrading performance, split testing is designed to attempt to optimize one variable. Sometimes it's difficult to isolate said variable. In this case, microsoft spends inordinate amounts of time and money to keep a high volume site snappy and responsive. The question is: are they spending *too* much money. So, they are attempting to answer that question using ye-olde-standard split testing methods.
Nothing to see here. Move along.
Then you haven't used it to track EVENTS (that affect more than one person) of personal importance to you: the first snippets of information to come out of Mumbai were via Twitter. Last night I used it to track snowfall (and traffic conditions) in Vancouver, BC. Coupled with instant upload of phone cam pictures, it was an amazingly realtime view of my personal geographic area.
"The most important thing in a man is not what he knows, but what he is." -- Narciso Yepes