Feeds

Microsoft's dynamic languages on forced diet

.NETized scripting out of favor

Securing Web Applications Made Simple and Scalable

Microsoft appears to be backing off its initial commitment for .NETized versions of dynamic languages.

Jimmy Schementi, the program manager for Microsoft's implementation of Ruby, called IronRuby, has left the company as the IronRuby team has been run out town and reallocated.

Schementi has blogged about a "serious lack of commitment" to IronRuby and dynamic languages in general on .NET.

He wrote: "When my manager asked me, 'what else would you want to work on other than Ruby,' I started looking for a new job outside Microsoft."

According to Schementi, software engineer Tomas Matousek is the only person left working on IronRuby at Microsoft. Apparently the team was shrunk about a year ago.

In November, Microsoft moved John Lam, who'd built the RubyCLR for writing .NET applications in Ruby, onto another — unidentified — project.

Lam was hired in 2006 as part of an intake of brains from the open source and scripting communities to help tune dynamic languages to .NET. Jython creator Jim Hugunin was hired by Microsoft in 2004 to build IronPython for .NET.

Schementi said the team's shrinkage has severely limited its agility, and is the reason why IronRuby has not been added to VisualStudio, and that adding IronPython has been delayed.

Microsoft has reportedly refused to comment officially on the changes.

Reading between the lines, it would seem that Microsoft's push for Microsoft-versions of dynamic languages has fallen victim to overall budget cuts and changing priorities.

Microsoft last month released IronRuby, IronPython, and the Dynamic Language Runtime (DLR) under an Apache Software Foundation (ASF) license, releasing them from Microsoft's Permissive Licenses (Ms-PL).

Microsoft cited customer feedback as the reason for the change, but the move suggests that Microsoft is done with trying to build the languages itself. It either wants to let the languages slowly die without claiming responsibly, or hopes the new license will finally invite others into the effort and free it from the burden of developing and maintaining the languages and runtime.

The company appears to have decided it makes more sense to leave open source and dynamic languages to the de facto options such as PHP — that Microsoft has been busy tuning to Windows and Azure — while focusing on the languages it does best, such as Visual Basic and C#. Microsoft has also released tools to make Ruby and Java run on Azure.

Microsoft has certainly struggled to embrace the open-source development entailed in dynamic languages. It made a conscious decision in 2008 not to accept external contributions to the DLR, while saying contributions were welcome for IronRuby.

Microsoft has been wary of exposing itself to potential litigation that might result from code authors or others once it has accepted code contributions in products it ships.

It was the kind of limitation — combined with the Ms-PL — that helped ensure genuine open sourcers outside of Redmond didn't rally behind its dynamic platform and languages. ®

Bridging the IT gap between rising business demands and ageing tools

More from The Register

next story
NO MORE ALL CAPS and other pleasures of Visual Studio 14
Unpicking a packed preview that breaks down ASP.NET
DARPA-derived secure microkernel goes open source tomorrow
Hacker-repelling, drone-protecting code will soon be yours to tweak as you see fit
Cheer up, Nokia fans. It can start making mobes again in 18 months
The real winner of the Nokia sale is *drumroll* ... Nokia
Put down that Oracle database patch: It could cost $23,000 per CPU
On-by-default INMEMORY tech a boon for developers ... as long as they can afford it
Google shows off new Chrome OS look
Athena springs full-grown from Chromium project's head
Apple: We'll unleash OS X Yosemite beta on the MASSES on 24 July
Starting today, regular fanbois will be guinea pigs, it tells Reg
HIDDEN packet sniffer spy tech in MILLIONS of iPhones, iPads – expert
Don't panic though – Apple's backdoor is not wide open to all, guru tells us
prev story

Whitepapers

Designing a Defense for Mobile Applications
Learn about the various considerations for defending mobile applications - from the application architecture itself to the myriad testing technologies.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Seven Steps to Software Security
Seven practical steps you can begin to take today to secure your applications and prevent the damages a successful cyber-attack can cause.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.