Username or EmailPassword
> First Microsoft tried to embrace and extend
> Java directly, by adding their own extensions
> to their own implementation of Java that tied it
> to Windows. Sun sued them for that.
It was proven in a court of law that Microsoft intentionally introduced incompatibilities into their version of Java in an attempt to undermine Java. That's why Sun sued them. It was part of the whole laundry list of anti-trust claims against Microsoft from multiple other companies..
> But MS did submit the CLI and C# to ECMA
> for standardization. Door open for someone to
> take it and run with it.
The problem is that until Microsoft open sources the official .NET implementation, mono is always going to lag seriously behind .Net. And also, keep in mind that only the CLI and C# are standardized. Most of the .Net APIs are not. There are many features in .Net 3.5 for example, that, mono doesn't support, and probably never will. Porting .Net applications to mono often requires a significant amount of changes. And if you don't have the source code for the app, porting may also be impossible.
Mono is an interesting effort, sure. But right now, it comes NO where near the cross-platform capabilities of Java. And until Microsoft open sources the official .Net implementation, I doubt that it will ever compete with Java when it comes to truly cross-platform applications. Edited 2009-01-13 05:39 UTC