InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Inside IronRuby PreAlpha1

Posted by James Vastbinder on Jul 26, 2007

Sections
Development
Topics
.NET ,
.NET Framework ,
Dynamic Languages ,
Ruby
Tags
IronRuby

This week at OSCON, John Lam of Microsoft released IronRuby to the masses and promised to host the source code on Rubyforge under the Microsoft Permissive License by the end of August.  Many consider the Microsoft Permissive License to adhere closest to the ideals maintained by the OSI and some even speculate Microsoft will soon submit the license to the approval process.  Still speculation abounds on the decision to host the source code on Rubyforge which is not a Microsoft property.

Along similiar lines when asking John about the process to ship the code under an "Open Source" license and on a non-Microsoft property he responded:

No formal process at all - just lots of meetings with management and lawyers.

When asked about compatiblity with the Ruby specification John replied:

We are committed to building an implementation that is true to the language - compatible with the 1.8.x branch of Ruby. The only significant feature that we will not implement is continuations – this is consistent with the JRuby project’s position on this feature as well.

Possibly in response to Martin Fowler's prose on Ruby and Microsoft and to get around the dilemma where Microsoft employees may not look at the source code of Open Sourc projects, when asked how best the community could help John indicated:

Help us implement the existing C-based Ruby libraries in the standard distribution.

Looking to the future of IronRuby, John would like the community to assist in building out the .NET libraries and in spreading the word on IronRuby:

Help us build the libraries. Help us evangelize the technology. Help us build interesting .NET-specific libraries as well.

 Infoq has other great content on both IronRuby and Ruby at the community level.

MS and OSS by Alex Popescu Posted
  1. Back to top

    MS and OSS

    by Alex Popescu

    Why is this such a big deal? I think in those "lots of meetings" the managers should be explained that without opening it most probably IronRuby will never catch up with CRuby/JRuby. And the lawyers... well, I don't want to have to deal with lawyers :-).

    ./alex
    --
    .w( the_mindstorm )p.
    ________________________
    Alexandru Popescu
    Senior Software Eng.
    InfoQ TechLead&CoFounder

    PS: Is this the first time MS is considering open sourcing something?

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.