The guy leading Microsoft's port of Ruby to .NET has warned of a potential Balkanization of Ruby, which could impair the language's success.

In an interview, John Lam said Ruby could benefit from "a Guy Steele Jr" to help define the language, and help establish a common specification that everyone could refer to. Computer scientist Steele was hired by Sun Microsystems early in the life of Java to help articulate clear specifications for the language.

"Frankly I don't think it's going to happen," Lam said.

Lam is a long-time Ruby advocate. Before joining Microsoft to put Ruby to the .NET Common Language Runtime, he worked on building the RubyCLR bridge creator.

He thinks people are often more interested in features development on Ruby - as they are in other areas of IT - than in writing specifications. Currently there are five funded Ruby implementations, including Microsoft's IronRuby and JRuby, each with different behaviors. That can mean things run differently, without real reason.

Some may argue that Microsoft is increasing Balkanization by working on IronRuby. Speaking last week at the Silicon Valley Rails Conference, Lam said customers want Microsoft to build Ruby.

Speaking ahead of his Uberpulse interview at the conference, Lam outlined Microsoft's thinking behind IronRuby. He said Microsoft is getting "really close to running real Ruby applications".

The company is not trying to convert people wholesale to .NET, but IronRuby is part of an attempt to regain ground lost among a generation of developers who've gone to Mac and open source and frameworks. "We are not fools, and think: 'Hmm, people are suddenly going to transition.' We think there are some interesting combinations, where people can use Ruby the language on top of our libraries, which will be appealing and interesting," he said.

Click here for John Lam's Uberpulse interview, and for more on the strategy and thinking see the full Ruby Conference presentation here.®

Related stories

• Is SproutCore worth the Flash and Java iPhone snub? (2 July 2008)
• Converting Groovy to Ruby (1 May 2008)
• Developer leads buff the Ruby slippers (25 April 2008)
• Why is Ruby on Rails so darn slow? (21 April 2008)
• Hands on part 2 Pump some IronPython with Studio IDE (17 April 2008)
• No Borg-like release train for Ruby on .NET (17 March 2008)
• QCon 2008 Other languages key to Java's future (14 March 2008)
• Hands on, part 1 Quick scripting for .NET with IronPython (13 March 2008)
• QCon 2008 preview Relax JCP and Java license process - Spring father (7 March 2008)
• Ruby project yields to Microsoft (5 February 2008)
• NetBeans and Ruby, part 1 Polished NetBeans means Ruby (31 January 2008)
• Uncertainty for Ruby and Rails despite changes (8 January 2008)
• Latest NetBeans thinks big for scripting (12 December 2007)
• Stob Programming with Marigold gloves on (13 November 2007)
• Book review Learning Ruby (1 November 2007)
• Groovy way to MySQL (25 October 2007)
• PHP victory over Ruby: was Gosling right? (25 September 2007)