Skip to main content

Dynamic Language Runtime (DLR), IronRuby and Advantages

What's being popular out there right now is something called IronRuby, which is an implementation of the Ruby language in .Net, which is built indirectly on top of the CLR.
So let’s talk a little about how IronRuby fits into the .Net world, something that you should know at this point is that Microsoft is building a common platform for dynamic languages called the Dynamic Language Runtime or DLR for the short, which runs as a service on top of the CLR.

DLR provides common functionalities like MSIL generation, GC, so that dynamic language implementers can focus on the implementing there dynamic language on top of this without worrying about the “gooing” part to the CLR.
All that the language implementer needs to do at runtime is to parse the language, tokenize it and create a tree structure containing the expressions and statements and pass it on to the DLR.
At the next step the DLR is going to generate MSIL from these trees, and the MSIL would execute under the CLR. Some pretty interesting things to note here is that when the DLR does not know how an operation should be actually executed, it looks at the currently executing dynamic language and ask it how the operation should be done, then the language responds with another tree on how the operation should be done, if the language does not know how the operation should be executed than the DLR takes a default action into evaluating the expression.

Something interesting to note here is that, these trees that the DLR gets back from asking questions on how to do certain thing in a language is actually cached, so that the next time the DLR encounters something like that, it looks at the cache for an answer, and does not go through asking the language for help.

The DLR is still being built and up to now developers involved in the DLR , says there are lot more work to be done.
The whole point of the DLR and the language actually complies into MSIL and gets executed under the CLR is interoperability between these dynamic languages built on top of the DLR and other .Net languages. This would actually mean that you can consume a library that was written on one of these languages inside C# or vise versa, i.e. consuming a C# library from these dynamic languages.

This brings us to the advantages of this hectic effort, something that most developers face is covering unit testing of there respective module, one the problems that they face is the time limit when writing these in something like C# or Java.
Now, with dynamic languages being able to interop, you can write your unit testing in a language like IronRuby and consume your .Net APIs. This is much easier cos' writing your test cases in a dynamic language is must faster, and increase your productivity.

Another area where this can help is in the area of domain specific languages (DSL), where your domain specific grammar can be written in a language like IronRuby or IronPython and where your actual code generation can happen in a statically type language like C#.
This effort is also worth while in places where we use XMl as “processing” language, like in build scripts, where your build "logic" can be written in a language like IronRuby, after all writing logic in a programming language is much easier then writing in XML, I never liked XML for these purposes anyway..

There are some dynamic languages that are being implemented now, like IronRuby and IronPython, and there initial implementation can be downloaded and played around with. I choose IronRuby as the language and trying it out a little bit now a days, you can try it out too, but before that, try learning the real power in dynamic languages and try playing around with Ruby before you go ahead with IronRuby.


Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down.
WCF applications can be hosted in 2 main ways- In a Windows service- On IIS 7 and aboveWhen WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services.With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications
Less development effort
Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementation is n…

Task based Asynchronous pattern, Async & Await and .NET 4.5

One of the key features in .Net 4.5 is to write asynchronous programs much easier. So if I was to write asynchronous programs in .Net 2.0/3.5, I would either follow the event based model or the callback based model. For an example, a synchronous method that does intensive work (say the DoWork()) can be made asynchronous by using the following patterns
1) Implementing the IAsyncResult pattern. in this implementation, 2 methods are exposed for the DoWork() synchronous method, the BeginDoWork() and the EndDoWork() method. The user will call the BeingDoWork() passing in the required parameters and a callback of the delegate type AsyncCallback(IAsyncResult). The BeginDoWork() will spawn a new thread a return control back to the user. Once work is completed in the spawned method, as a last step, it will call the inform the AsyncResult implementation, which in turns will call the EndDoWork() (which is the callback that was passed in to the BeginDoWork()).
2) Implementing the event pattern. Her…

MEF (Managed Extensibility Framework), .NET 4, Dependency Injection and Plug-in Development

Almost after .Net 4 was released I remember reading about MEF (Managed Extensibility Framework), this was a framework for developers to compose their application with required dependencies. At first this looks like the Unity Container used for dependency injection, but MEF is much more than a dependency container but there is nothing stopping you from using MEF as a dependency injector.I remember around 5 years back when I was in a project that created a framework that allows developers to plug-in there modules as WinForm screens. The developer would create a set of screens with the intended functionalities and the drop this component in the bin folder of the framework and then will move on to do some painful configurations for the framework to pick up the module. Dropping the component into the bin folder and doing a bit of configuration is all that s needed for the framework to pick up display the screens. Typically, the configurations would also contain metadata about the screen.Al…