.net - PowerShell Runspace vs DLR -
Now with the available .NET 4.0 beta, and thus the broad availability of .NET dynamic language runtime, I think that Types of topics are going to be "hot"
I'm confused about the conceptual difference between DLR and PowerShell. I think if I want to provide scripting capabilities in my .net app, So I can enable scripting in DLR (and thus IRPathan or IronRB) , Or whatever Iron * languages available for DLR), or a PowerShell host Runspace.
What are the pros and cons of each method? Why can I choose another? As a dynamic language, and a first-class .NET language on it, why does PowerShell not also target DLR?
You can consider "DLR v1.0" in DLR in .NET 4.0. This includes improvements to call site caching mechanisms, cross-language interop featuers, and existing LINQ expression trees. These are all features that are very useful for hosting languages, but are not hosting a single language.
And this is a missing piece in DLR 1.0 - a shared hosting story for all languages but we start on as a hosting API, which we send on CodePlexXLL / DLR and IronPathon projects and O / IronBube is also given on gitb. Unfortunately we did not think we could drive these APIs to the quality of the ship for the net quality so that we do not include them. Especially we want to get more feedback from other languages such as parvars and even VB and C # so that we can ensure that we have the right API.
Therefore, there is more or less the story of hosting this in every language, in which Iron Pethone and Iron Roubin are currently available. But we would love to see that they will be integrated in the future so that your users can choose which language to use. But there is nothing in the box to target the powerhield right now.
Comments
Post a Comment