Feeds

Microsoft: keep your sticky mitts off our language runtime

DLR stays closed, IronPython to accept donations

High performance access to file storage

It's official: Microsoft will not accept any external code contributions to its planned Dynamic Language Runtime (DLR), which will run Microsoft's new scripting languages for the web and Silverlight content on .NET

Microsoft will, though, continue to accept source-code contributions to its slowly emerging implementation of Ruby for .NET, IronRuby. Contributions are helping to build IronRuby and shepherd the language towards the first-full release.

The Register has learned, meanwhile, that Microsoft will start accepting external contributions to its other great scripting language project, putting Python on .NET - IronPython - in the "near future". The promise by Microsoft IronRuby lead John Lam comes nearly a year after the topic was first raised.

The reason Microsoft decided to leave the DLR closed, despite taking contributions to the languages that will run inside it, is to protect itself from unwanted licenses and IP claims.

The DLR will enable dynamic-language applications and media designed for the web or Silverlight to be built and delivered in IronRuby and IronPython inside Microsoft's .NET Framework. The DLR will provide a shared a sandboxed security model and browser integration. This will allow developers to use these languages inside the same programming environment and runtime as Microsoft other languages.

Early versions of the DLR, announced in May 2007, have been available under Microsoft's Public License (MS-PL), which the company says is "BSD-like".

While the DLR has not exactly been open so far, the official policy emerged following an internal debate over what code Microsoft can accept.

Last week, Jimmy Schementi, DLR program manager, told a TechEd session on Microsoft and open source: "The languages were very confused about should we accept contributions or not... now we have that line defined, everything else is fair game."

He added: "In the future if there's part of the DLR we want to make open source that will probably allow contributions."

Microsoft is keeping the DLR closed because it will go into the next version of the .NET Framework, expected around the same time as Visual Studio 10. Microsoft had committed to release DLR 1.0 by the end of 2008.

Closing off the DLR will potentially prevent unwanted and unaccounted IP from creeping into the code. This could have posed two distinct problems for Microsoft.

The company could have left itself, and customers, open to IP claims from disgruntled code authors.

Also, Microsoft does not want code that's distributed under copyleft licenses, such as GPL, creeping in. This could compromise its ability to redistribute - and thereby monetize - Windows-based products that ship with any tainted DLR code. A copyleft license would compel Microsoft to ship the product source code and contribute changes back to the community. This is not a typical business model for Microsoft.

As it currently stands, IronRuby does not ship in the box with Visual Studio. Instead, users must download the language once they have Visual Studio and require it. "The experience for end users is that IronRuby will be a trivial / transparent download when they use a feature that will optionally require IronRuby," Lam said in an email.®

High performance access to file storage

More from The Register

next story
Android engineer: We DIDN'T copy Apple OR follow Samsung's orders
Veep testifies for Samsung during Apple patent trial
Windows 8.1, which you probably haven't upgraded to yet, ALREADY OBSOLETE
Pre-Update versions of new Windows version will no longer support patches
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
Windows XP still has 27 per cent market share on its deathbed
Windows 7 making some gains on XP Death Day
Internet-of-stuff startup dumps NoSQL for ... SQL?
NoSQL taste great at first but lacks proper nutrients, says startup cloud whiz
US taxman blows Win XP deadline, must now spend millions on custom support
Gov't IT likened to 'a Model T with a lot of things on top of it'
Batten down the hatches, Ubuntu 14.04 LTS due in TWO DAYS
Admins dab straining server brows in advance of Trusty Tahr's long-term support landing
prev story

Whitepapers

Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
HP ArcSight ESM solution helps Finansbank
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.