From the Editors: Don't expect Microsoft to let Mono dictate



Email    print   
November 1, 2008 —  (Page 1 of 2)
The true test of a specification’s openness is whether the company that sponsored the specification accepts third-party additions or changes. Microsoft submitted its Common Language Infrastructure to Ecma, a vendor consortium, on the basis that it was an open, non-proprietary specification. The Mono project’s desire to contribute back to the specification will test Microsoft’s earnestness. We don’t predict that Microsoft will pass the test, but rather will squelch Mono’s changes.

From Day 1, of course, Microsoft has been in the driver’s seat regarding the CLI and everything related to .NET. That is unlikely to change.

In its efforts to replicate .NET 2.0, Mono thought up some interesting additions to the specification. That’s good. An open specification should be dynamic and encourage broad participation. It shouldn’t just be a pro-forma rubber stamp for one company’s proprietary technology.

While Mono is free to submit its ideas to Ecma, Microsoft remains incredibly powerful when it comes to CLI. The Ecma CLI working group must decide whether the additions are worthwhile, and Microsoft serves effectively as a gatekeeper. It can use the documented processes with Ecma to slow down any additions that it doesn’t want. Even if, by some fluke, Ecma does approve some of Mono’s changes to the CLI, Microsoft can simply delay implementing them in its own code, or ignore them completely.

It took the Mono team several years to develop Mono 2.0. The pace of the open-source project’s work, and its relatively small installed base, is too underwhelming to threaten Microsoft’s designs over .NET. Microsoft is also cycling its energy toward the creation of .NET libraries such as LINQ, WCF and WPF, which Mono will be attempting to replicate in upcoming releases.

Note that the .NET Framework has remained largely unaltered since the release of .NET 2.0, which means that Microsoft and Mono are using the same playbook. Despite Ecma, Mono has to scramble to stay on the same page. Because Mono has to ensure that it not only conforms to Ecma specifications, but also passes Microsoft’s test suites, it is all but guaranteed that Mono—and anyone else seeking to create a CLI implementation—must follow Microsoft’s lead.



Related Search Term(s): Ecma, Microsoft, Mono, Python

Pages 1 2 


Share this link: http://sdt.bz/33024
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
From the Editors: Microsoft should rescue Mono
Helping Mono would be a good move for Microsoft; a look at the companies that have come and gone in the SD Times 100 Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb