Home opinion-and-analysis Open Sauce Where, oh where, is the ECMA-compliant Mono source code?

Author's Opinion

The views in this column are those of the author and do not necessarily reflect the views of iTWire.

Have your say and comment below.

Last week, Miguel de Icaza, a vice-president at Novell, announced the release of version 2.8 of Mono, a project he set up to create an open source clone of Microsoft's .NET development environment.


De Icaza is extremely punctual in announcing these Mono releases. However, there is one release which he hasn't spoken about for more than a year - and which, I think, he would like everyone to forget about.

The release that I'm referring to is something De Icaza promised on July 6 last year when Microsoft issued a clarification about the licensing of some portions of .NET - C# and the common language infrastructure, allowing developers to use both under the terms of its community promise.

The promise extends to two sets of .NET specifications, 334 and 335, submitted to ECMA, a standards body that has been in existence for nearly 50 years.

De Icaza, who said he was "overflowing with joy" at the clarification, made a confession at the time: what he and the other Mono developers had cooked up thus far contained much more than was detailed in the ECMA specifications.

There have been fears among free and open source software community members that Mono could prove to be a patent trap and this statement from De Icaza confirmed that people were right to entertain such fears - after all if he had boldly gone beyond the ECMA specs, he could well have incorporated code that violated patents belonging to Microsoft.

De Icaza made the following pledge: "In the next few months we will be working towards splitting the jumbo Mono source code that includes ECMA + A lot more into two separate source code distributions. One will be ECMA, the other will contain our implementation of ASP.NET, ADO.NET, Winforms and others."

The man is yet to deliver on that promise. I haven't seen or heard of anybody who has reminded him of the same promise either.

WEBINAR 26/27th May

Thinking of deploying Business Intelligence (BI)? So are your competitors.

And the most important, fundamental, tool for delivering your BI information to your users? Dashboards.

THIS IS ONE NOT TO MISS SO REGISTER NOW

DON'T MISS OUT - REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect

 

 

 

 

Join the iTWire Community and be part of the latest news, invites to exclusive events, whitepapers and educational materials and oppertunities.
Why do I want to receive this daily update?
  • The latest features from iTWire
  • Free whitepaper downloads
  • Industry opportunities