Summary: The recommendation of an Intel marriage with Microsoft (even in units that deal mostly with Linux) is an insulting slap across the face of developers employed there; we take a look at recommendations made to IoTG (Intel) by a firm with Microsoft orientation (screenshot to the right)

LAST night we looked at the firm Intel had hired to recommend Microsoft (push polling seems likely), allegedly after Intel's decision. Some tell us that a year earlier the nontechnical 'suits' at Intel finalised that strategy regardless (see this series' index in the relevant wiki page for additional information and context). Why seek consultation other than 'arse-covering' (seeking to reaffirm a bad strategy, albeit with the veneer or guise of 'professional' 'research')? A few dozens, 50 or so men from Denver, Colorado (without much industry experience) would not know any more/better than Intel's own in-house engineers.

Here is an image, extracted from the above report, which shows the summary of recommendations to IOTG/IoTG (the IoT Group at Intel).

"Disappointing," told us a source, "but not surprised."

This angered quite a few Intel insiders. The last thing they want is Microsoft at the job... especially those who work on "IoT" 'things', i.e. mostly Linux.



"Is there a way to find a public source," asked us one person, about "the graphic which was attached? [It had been circulated internally for a while] It shows a bad Microsoft infection via partnership obligations."

We've gotten the full report, which we plan to release at a later stage. It's not a "public source"; as we explained before, Intel worked hard to keep this sort of stuff concealed. These sorts of reports, we've been told, are largely responsible for the horrible direction and the demise of Intel. Shades of Nokia...

The video mentions Microsoft AstroTurfing. We have documented and assembled many examples of Microsoft AstroTurfing. In the past few days in our main IRC channels we've had to cope with trolls based in Washington, promoting GitHub using anonymous accounts and looking to discredit us using a bunch of Microsoft lies. Are these Microsoft employees? AstroTurfing? Hard to tell...

"One last thought is the Microsoft move to design chips," told us an informed source about all this, "maybe this will turn around the adoption of proprietary tools and partnership with Microsoft. I guess we'll see."

The way we see it, Microsoft is all vapourware and PR stunts. There's already intense competition in this space and Windows is a misfit.

"Wintel is an acknowledged problem," told us one person earlier this month (having seen portions of these leaks), "but it is probably forgotten by the old crowd and unknown to the younger generations. Thus it would be very important to review and add weight to the review by including new material. The material described is very interesting.

"So many in US business are loser zero-sum-gamers and don't get the nature of collaborative development. However, look at this oldish link to see what's happening at OpenStreetMap regarding open data collaboration."

Intel does not seem to understand community. It doesn't understand developers. It does not 'get' software freedom. Does it insist so strongly on dying with Microsoft? And if so, whose idea is it? An Intel loyalist or Microsoft moles? Stay tuned... ⬆