Credit: unknown (Twitter)
IT IS no secret that Microsoft is trying to derail Android development or take over it, not just tax it using software patents or exerting influence/control using software patents. Then there's the antitrust aspect; it was Microsoft and its proxies/front groups that pushed European politicians to go after Google's Linux endeavours (we have covered this in dozens of posts going half a decade back).
"Then there's the antitrust aspect; it was Microsoft and its proxies/front groups that pushed European politicians to go after Google's Linux endeavours (we have covered this in dozens of posts going half a decade back)."Right now we find Microsoft's Jason Perlow [1, 2, 3, 4, 5] (a Microsoft employee who habitually attacks Microsoft's rivals) doing the anti-Java and anti-Android spiel at ZDNet, which foolishly employs Microsoft staff as journalists. Perlow's latest piece has a bait headline, "Android's existential crisis: Why Java needs to die on mobile devices" (attack on both Android and Java; two birds, one stone).
All we can say is, how typical. Agenda as 'news'. That's the modus operandi and the business model of CBS, which owns ZDNet.
To better understand why Perlow would wish to trash-talk/badmouth both Java and Android, consider the case of RoboVM, which Microsoft has just killed using its classic E.E.E. method. James Darvell's good new article about Microsoft's assassination of RoboVM (and by extension harm to Android and to Linux) goes as follows:
Microsoft recently made a big noise about its love and support of the Open Source community (especially Linux), but while it's making concrete steps toward improving its support for FOSS projects, its motives may not be entirely altruistic. Microsoft continues to fund legal attacks against open-source projects on multiple fronts, and it has crushed open-source projects when it suits the company.
Such is the case with RoboVM, a Java-to-mobile compiler that supported cross-platform mobile development.
RoboVM originally was an open-source project, although that changed after the parent company was acquired by Xamarin in October 2015. Xamarin had several similar products that support cross-platform development using different programming languages. Naturally, Xamarin saw RoboVM as a suitable addition to its stable.
Shortly after the acquisition, an announcement was made to the effect that the open-source development model "wasn't working out" for the RoboVM team. The project was closed, and licensing fees were increased to match the other tools in Xamarin's lineup.
Earlier this year, Microsoft acquired Xamarin, and while it's proudly touting the majority of Xamarin's suite of tools, it seems there's no place for RoboVM in Microsoft's cross-platform development plans. Last week, the RoboVM team announced that the project would be shut down.
But, there are some who will say that Microsoft just doesn't like Java. Microsoft did get its fingers burned back in 1997 when Sun sued Microsoft over its attempt to appropriate Java. Back then, Java was set to become the "language of the Internet", and bringing Java applet support to Internet Explorer was an important goal. In true Microsoft fashion, the Windows Java VM only partially supported the published Java standard—what's more, it added features that were not a part of the official standard.
The goal was to create a situation where code that ran on a Microsoft VM would not run on any other platform. By hijacking the Java standard, Microsoft planned to capture Sun's user base and dictate the future of Java. Of course, that plan resulted in an expensive debacle, which explains the company's lukewarm attitude to Java ever since.
"Don't underestimate Microsoft's malice. It's still run by virtually the same people."Microsoft has a history of using the corrupting influence of money to demolish competitors, e.g. by poaching employees, paying for non-compete clauses, taking over only to dismantle and so on. Don't underestimate Microsoft's malice. It's still run by virtually the same people. ⬆
“Linux infestations are being uncovered in many of our large accounts as part of the escalation engagements.”