今天打开我的OUTLOOK按惯例接收了一遍邮件，code project的22号的daily news shock了我一把，最近很少关注业界的动态，对这方面的消息有些麻木，但是这个标题用最近很时兴的一个形容词汇来描述叫做 ------ “很给力” ，虽然我觉得创造和传播这种下三滥词藻的人很无聊，但是我既然联想到了又已经用了，请看官原谅我。
Microsoft offloads IronRuby and IronPython languages to external developers
The handwriting was on the wall: Microsoft was leaning away from supporting the IronRuby language. It turns out that was true. And ditto with its complement, IronPython.
The handwriting was on the wall: Microsoft was leaning away from supporting the IronRuby language.
It turns out that was true. And ditto with its complement, IronPython.
IronRuby and IronPython, until November 1, are Microsoft-supported and .Net-targeted versions of the Ruby and Python dynamic programming languages. After November 1, they will belong to the community and won’t be Microsoft properties any longer.
For a while, it looked as if Microsoft was moving full-steam-ahead with dynamic languages. Adding the Dynamic Language Runtime to the Common Language Runtime made the Redmondians seem even more committed. Earlier this summer, Microsoft made IronRuby and IronPython available under the Apache 2 open-source license. Around the same time, Microsoft released version 1.1 of IronRuby and an alpha of IronPython 2.7.
But there were signs problems were afoot. There was talk Microsoft might be convinced to move IronRuby to the CodePlex Foundation (now known as the Outercurve Foundation) or to release it to the community in some way. Microsoft officials would not talk about their plans for the languages.
On October 21, the future became clear. Microsoft said it is donating both IronRuby and IronPython to the open source community. Microsoft is not killing off its support for the Dynamic Language Runtime, however; that will continue to be part of the .Net Framework, as it is currently, officials said today.
Microsoft isn’t simply casting off these languages, officials insisted. And, indeed, it does look like there’s been some forethought as to what to do to make sure they don’t simply whither. According to a blog post by Jason Zander, Corporate Vice President, Visual Studio:
“As part of these changes I’m happy to announce new project leaders external to Microsoft who will take over the projects and provide leadership going forward. The IronPython project will have Miguel de Icaza, Michael Foord, Jeff Hardy, and Jimmy Schementi as Coordinators. Miguel de Icaza and Jimmy Schementi will be the Coordinators of IronRuby. All of these guys have worked with or on the Iron projects since their inception and I have nothing but trust and respect for the new stewards of these community projects.”
Any IronRuby and/or IronPython developers out there? What’s your take?
Update: Jim Hugunin, the creator of IronPython, has just announced he is leaving Microsoft for Google. He says Microsoft’s decision to discontinue its support of IronPython was “a catalyst but not the cause” for his decision. Some good stuff from Hugunin’s eloquent goodbye post:
“I will suffer some pain when I have to write code in Java now that I’ve learned to love the elegance of C#. I will suffer some frustrations when I have to use Google Docs instead of the finely polished UI in Microsoft Office. More than anything, I will always value the chance that I had to work with and learn valuable lessons from some truly great people.
“As I leave Microsoft, I’m incredibly excited to be going to work for Google. I like to build projects with small talented teams working on quick cycles driven by iterative feedback from users. I like to have a healthy relationship with Open Source code and communities, and I believe that the future lies in the cloud and the web. These things are all possible to do at Microsoft and IronPython is a testament to that. However, making that happen at Microsoft always felt like trying to fit a square peg into a round hole - which can be done but only at major cost to both the peg and the hole.”
正如我已经离开了M$，我很兴奋，我可以为'谷歌'办事。我憧憬着和一小群高智商的天才一起工作在高速周期驱动的项目中不断收集和倾听用户的真实回馈。我憧憬着和开源项目及其社区建立一个良性的合作关系，同时我相信未来是云计算的天下(云端传来一个沧桑的细长怪异的回声 welcome on board~~~ young guy!) 这些都是M$可能去做的也是变异'金刚大蛇'的遗愿。不管这么说，对于M$，想要铸就这段故事就好比想要把一个方桩塞进一个大铅桶里去，终是可以完成但是桩和铅桶呢重要付出巨额的代价。
Signs are pointing to Microsoft backing away from IronRuby, the .Net-targeted implementation of the Ruby dynamic programming language that the company has been developing and funding for the past couple of years.
For a while, it looked as if Microsoft was moving full-steam-ahead with dynamic languages. Adding the Dynamic Language Runtime to the Common Language Runtime made the Redmondians seem even more committed. A couple of weeks ago, Microsoft seemed to up the ante again by making IronRuby and IronPython available under the Apache 2 open-source license. Around the same time, Microsoft released version 1.1 of IronRuby and an alpha of IronPython 2.7.
But all isn’t rosy in IronRuby land. According to a now former IronRuby developer, Jimmy Schementi, Microsoft has just one developer left on that project (who is committed to it half-time). Schementi recently quit Microsoft when his manager asked him “what else would you want to work on other than Ruby,” he blogged.
Schementi’s August 6 blog post about his departure from Microsoft has resulted in lots of questions about Microsoft’s intentions around IronRuby, IronPython and dynamic languages in general. Developers are wondering whether to continue with IronRuby projects; whether Silverlight and Azure support are in the cards and more.
(I’ve asked the Softies a bunch of these questions, as well as about the future of IronPython, but no official word back so far.)
Update (August 10): Microsoft is not commenting on the future of IronRuby. Here’s the official word from Chris Dias, Group Program Manager, Visual Studio:
“At this time, we have no announcements to make about IronRuby and IronPython beyond what we announced in July 2010 — that we were putting these under the Apache License v2.0. Clearly, there is customer and community interest in these languages. With many organizations running mixed IT environments, we continue to value community feedback on how we can support their interoperability needs, and we remain committed to supporting multiple tools and languages that provide developers with the most choice and flexibility.”
Members of the Ruby community already are talking about the possibility of transitioning IronRuby to non-Microsoft ownership, with members of the community taking charge of the project. For that to happen, however, Microsoft needs to be clear about its intentions, as Schementi told members of the IronRuby Core mailing list:
“Though IronRuby is licensed under an open-source license, it is copyright Microsoft. IronRuby.net is owned by Microsoft. The GitHub “ironruby” organization is managed by Microsoft. Etc, etc. If the intention is to cease funding IronRuby, then a non-profit foundation owning IronRuby, like CodePlex Foundation, would be ideal, so that we don’t need to jointly own the copyright.”
Some kind of an official transition is definitely in order, blogged Mono team member Jean-Baptiste Evain:
“The IronRuby team currently consists of one hacker. We don’t know much about the IronPython team. And everyone who wanted to work on .net with their favorite dynamic language is freaking out. To a reason. The good news is that the code of IronPython, IronRuby and the DLR is open source, and has recently been re-licensed under the Apache2 license. The official message is that IronRuby’s fate is now in the hands of the community.
“That doesn’t sound like a bright future. So far, the community has been excluded from the development process of IronRuby. It’s impossible to contribute code to the core compiler of IronRuby, let alone to the DLR which is now part of .net 4.0. The code in github is a mere mirror of an internal TFS repository, and may or may not be up to date. And until IronRuby’s divorce with Microsoft is completely consumed, it will stay like this. So, sure we can contribute to external libraries, but that’s definitely not where the fun lies, and from now on, nor where the real work will be required.
“So is the solution a fork?”