Summary: FUD against Java is on the rise (Microsoft partly accountable), Miguel de Icaza receives another role from Microsoft, and more Microsoft projects which are complementary to .NET are now dead
SEVERAL weeks ago we wrote about signs that .NET is suffering, not Java. There are some new Microsoft hires that throw FUD at Java and Microsoft boosters who work as journalists lend their pen to this Slog, too (we prefer not to give examples as they would feed the FUD). Frankly, however, Oracle has supplied a lot of ammunition to those who are trying to injure Java. It’s not deliberate and it’s why Oracle is making a strategic mistake.
“IronPython and IronRuby get kicked out into the cold by MSFT.”
–Jan WildeboerAnyway, this post is not so much about Java. It’s actually about IronRuby dying. We saw the writings on the wall back in August [1, 2, 3, 4] (also see recent posts about IronPython, such as this one) and now there is almost a funeral. Jan Wildeboer from Red Hat writes: “#IronPython and #IronRuby get kicked out into the cold by MSFT. #RIP? http://is.gd/gcCON thinks so, http://is.gd/gcCQn doesn’t. We’ll see ..”
The nymshifting CodePlex Foundation (this Microsoft front is now called Outercurve [1, 2]) has been used as somewhat of a basket for Microsoft in which to put projects ‘externally’ (it’s about impression and appearance, not practice). Microsoft's MVP Miguel de Icaza has been part of it and at sight of the situation with Java at Apple he already throws FUD at Java using the news, as well as other recent Java news. According to this Microsoft employee, de Icaza et al. are supposed to try and rescue IronRuby and IronPython for the sake of greater .NET relevance. This is another Microsoft job for Miguel:
Today signifies a big step in Microsoft’s commitment to open-source: Jason Zander announced new leadership for IronRuby and IronPython, namely Miguel de Icaza, Michael Foord, Jeff Hardy, and myself. Since Microsoft has officially put the project in our hands, both languages will be open to contributions from the community, not just the core team members. Also, any previously unreleased work as been released, include the IronRuby tools for Visual Studio and groundwork towards IronPython 2.7 and 1.9. You can find the appropriate releases on both IronRuby and IronPython’s CodePlex sites.
Also, Miguel is a big-shot at Novell, but I’ll let him comment on how his company is supporting the projects. =)
He is a big-shot to Microsoft. They groomed him (e.g. with interviews and other publicity like this recent example) so that he can help Microsoft from outside Microsoft. His job at Novell (it’s a team effort) is to promote Mono/.NET and apparently demote Java in the process (also with FUD in his blog and in Twitter).
“In Twitter, de Icaza speaks quite a lot with the mobbyists; like them, he pretends to be pro-FOSS whilst actually doing a lot of harm to software freedom.”Who is this man kidding? Just watch him blogging about Microsoft folks this week (Ozzie in this case [1, 2]). If he loves Microsoft so much, maybe it’s time to reapply for that job he wanted.
It would be so much more appropriate if he just worked directly for Microsoft. In Twitter, de Icaza speaks quite a lot with the mobbyists; like them, he pretends to be pro-FOSS whilst actually doing a lot of harm to software freedom.
Anyway, based on this post from Microsoft MVP Jeff Hardy, we are adding IronPython to our list of dead projects from Microsoft (if someone continues it outside Microsoft, then that’s not a Microsoft product, still). It symbolises the continued collapse of .NET, which also relates to Moonlight and other cancelled/failing parts of Microsoft’s stack.
Well, the shoe has finally dropped: IronPython and IronRuby have been axed.