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.
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.
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'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.
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.
The two most popular managed environments (the JVM and the CLR) are in fact, nothing more than a set of shared libraries, each providing services to executing code such as memory management, thread management, code compilation (JIT), etc. Using both the JVM and the CLR inside the same operating system process is easy; in this new article, Ted Neward shows how and why.
Last week Microsoft released the feature specifications for the .NET Framework codenamed "Orcas" and the next version of Visual Studio. Among the more notable additions comes multi-targeting across versions of the .NET Framework, a feature that was noticeably absent from Visual Studio 2005.
The CLR has a major design flaw; each process can only have one. When you combine this with a ubiquitous process like explorer.exe, disaster can strike.
Hidden in the October CTP for Orcas, developers will find a new addition to the .NET Framework. The IPC mechanism called pipes has been introduced to managed code. The next version of the framework will support both anonymous pipes and named pipes.
With the 3.0 release of the .NET framework the IIS7 webserver will now support a new mode called "Integrated Mode". Integrated Mode brings to .NET the ability to write the equivalent of ISAPI modules, however now developers can code in C# rather than C++.
Craig and Vittorio release their Live Service Trace Viewer which is an enhancement to the one provided in the .NET 3.0 SDK. The differentiator: you can view the WCF interactions as they happen.
The videos (slides+audio) from the Microsoft-hosted LANG.Net Symposium are now available. Talks include "Dynamically Typed Languages on the Java Platform", " Ruby on the CLR", "Spec#", and "VB 9". The conference focused on programming languages that target managed execution platforms such as the .NET CLR.
On September 5, Microsoft released the first production version of IronPython. This implementation of Python runs on the Common Language Runtime 2.0. IronPython 1.0 can be downloaded from CodePlex, Microsoft's community development web site.
It suddenly seems everyone is interested in making Ruby on .NET a reality. The new IronRuby project was presented at RubyEnRails 2006 last week and this week we were notified of Brite, yet another Ruby interpreter/compiler effort targeting the CLR. The newcomers join John Lam's RubyCLR project and the joint Microsoft and Queensland University of Technology Ruby.NET headed for beta in late 2006.