Linked by Eugenia Loli-Queru on Wed 4th Feb 2004 05:34 UTC
According to statistics, Java continues to have the crown of the most used VM-based platform in the industry. However, Microsoft's C# and .NET gain ground every day. While C# might or might not overcome Java in the following years, the fact remains that more and more programmers want the choice of C# among their developer tools. So, where does this situation leave Apple?
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Hell, Mono probably already compiles on MacOS X with GTK.
I think Apple should focus on promoting Objective C and Cocoa, perhaps lending a hand to GNUStep's efforts.
MacOS X shows than NeXTs UI layer and class library are as good as ever, with a built-in IDE that is really pretty damn good.
Their adoption of Konqueror, instead of licensing the IE rendering engine (which surely must have been an option), shows that a vendors overwhelming marketshare in a given area does not predispose Apple to adopting that vendors product.
Supporting .NET is not the same as supporting Java at all. Java essentially provides the entire environment, from GUI rendering code to the VM to the language specification, and it is all available publically.
You have to license the Java trademarks and pass conformance testing if you want to market your modifications to the technology as 'Java', but this is a comparitively passive involvement by Sun.
With .NET only the language specification and a minimal class library is available publically.
Entering into licensing agreements for Windows Forms etc. when this is being phased out in Longhorn for what is sure to be an entirely incompatible API along with MS proprietary extensions like WinFS, tied to their patented XML schemas, and requiring DirectX etc. for GUI widget performance, just make .NET a quagmire that i'm sure Apple would rather not wade into.
If I was Apple I would simply wait until Mono matures, or if they see significant pressure from customers, contribute resource toward improving Mono.
A Microsoft-directed, Apple-only implementation would only put Apple at a disadvantage, no matter which way the .NET cookie crumbles.