Thursday, June 29, 2017

Are Windows blogs basically BS?

I have been reading some headlines recently, and thinking about how, one blog picks up on a small kernel of truth, interprets it, and all the other blogs copy that blog. And then this Chinese whispered distortion becomes accepted as fact.

And I just thought to myself, we really are living in a post-truth world. Maybe I'd have realised that already if I lived in another country. But it seems to me, that windows blogs have windows fans jumping and shadows and believing in faeries.

I just wish there was somewhere that stuck firmly to hard facts, and put the speculation in clearly speculative language.

For example, a member of the insider team said recently of windows 10 mobile "there are no current plans to move it from feature2" and "don't make a big deal of feature2" more or less. Now consider that the head of the insiders group recently tweeted that the insider team is not privy to anything beyond their current projects and workload.

I've seen people report "No more feature updates for win10m" and fans do all sorts of wild speculation based on this - which I DO NOT want to get into.

But the point being the original story was more or less "Is win10m coming off feature2 soon? Not that I know of", and "Don't freak out about feature2", and the response was basically a whole series of articles freaking out about feature2.

The same thing happens with rumours about new hardware, or talk about cshell, or almost anything.

Thurott reported that an insider had claimed "new hardware is being made, and paired with it a new _branch_ of windows 10 mobile". He somehow spun that into a "reboot" and how win10m is over.


He's not a happy man, and I can understand fan scepticism, but surely the art of unbiased journalism, and accuracy of reporting, if it still existed when the net took off, died in a large pit, the moment blogger and tweeters took it over.

The tiny gets exploded into mountains, and the storm is brewed in a tea cup.


from Windows Central Forums http://ift.tt/2sUxbLj
via IFTTT

No comments:

Post a Comment