Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage CLR Content on InfoQ

  • Interview: Neal Ford On Programming Languages and Platforms

    In this interview made by Sadek Drobi during QCon San Francisco 2007, Neal Ford talks about the tendency of having multiple languages running on one of the two major platforms existing today: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.

  • Programming languages in future systems

    The trend seems to be clear; in the next few years there will be an increase in adoption of new programming languages and systems will be written in multiple languages. But what does the mix look like, and which languages are suitable for what? In a recent post, language explorer and JRuby developer Ola Bini describes what future systems may look like.

  • Is it too late for Parrot VM?

    The Parrot Virtual Machine recently had it’s sixth birthday. Parrot is a VM that sprung out of the Perl6 development, which primarily targets dynamic languages, but also for instance .NET and C99. But six years is a long time, and both Microsoft and Sun is targeting this segment. Is it too late for Parrot?

  • .NET to Ruby connector available

    The Ruby Connector allows communication between .NET and Ruby. This brings the power of .NET to Ruby, and allows to use Ruby to power Visual Studio generated GUIs.

  • IronRuby now on Rubyforge

    IronRuby, Microsoft's implementation of Ruby for .NET, is now hosted on RubyForge. The current state of the code is available via the Subversion repository.

  • Catching up with Phoenix

    This past year Microsoft introduced Phoenix a project aimed at transforming the traditional blackbox compiler into a transparent one.

  • Java Language Runtime (JLR) project created

    A new project aims to increase collaboration among JVM based languages. The Java Language Runtime aims to collect code that is common among languages targeting the JVM and prevent duplication among the providers of JRuby, Jython, Groovy, and many others.

  • Presentation: Justin Smith on CLR Internals

    Justin Smith, Technical Evangelist for Windows Communication Foundation at Microsoft, delivered this devLink presentation on the .NET CLR Internals. Justin begins with an overview of the memory management model and then focuses different areas of the CLR and primarily the Garbage Collector.

  • Gardens Point Ruby.NET internals interview

    An option for running Ruby on the CLR today is the Gardens Point Ruby.NET compiler. A lot of work has gone into compatibility with Ruby and, recently, interoperability with other languages on the CLR. We talked to John Gough, of the Ruby.NET team, about technical details, compatibility and future plans for community participation in the project.

  • Ruby.NET 0.8 release

    While IronRuby will make its debut in late July 2007, another Ruby implementation for .NET has been available for a year: the Gardens Point Ruby.NET compiler. The project has an interesting relationship with IronRuby - it provides its parser. Its latest release adds improved interoperability with other .NET languages.

  • JRuby Team members doubtful about IronRuby

    Two members of the JRuby core team, Ola Bini and Charles O. Nutter, wonder whether Microsoft's IronRuby could possibly be a fully compliant Ruby implementation and run Rails, given Microsoft's policies. A viable alternative to IronRuby, the Ruby.NET compiler, is suggested.

  • Silverlight to Support Multiple CLRs in One Process

    A long standing problem with Microsoft's implementation of the CLR is that only one can be loaded into a process at a time. With Silverlight, that will no longer be a problem.

  • Microsoft Surpasses Java's Dynamic Language Support?

    Microsoft's announcement of the Dynamic Language Runtime (DLR) has caused quite a stir in many areas, also in the Java space. Many voices seem convinced that the DLR has given .NET a major head start over the JVM, because it solves many problems Java is only just starting to realize. We look at the current situation of dynamic language support and how it compares to the DLR.

  • Dynamic Language Runtime Announced

    Microsoft has announced that they are building an extension to the Common Language Runtime called the Dynamic Language Runtime (DLR). This extension is being designed to enable interoperability between dynamic languages in the same manner that the CLR enabled interoperability between statically typed languages.

  • Microsoft announces IronRuby

    Microsoft has just announced IronRuby at their MIX 07 conference. This also kicks off a bigger effort to support dynamic languages on .NET. Based on the experience gained in developing IronPython, a common Dynamic Language Runtime (DLR) builds the foundation for IronRuby, IronPython, JavaScript (EcmaScript 3.0) and Visual Basic.