On MovieTome: The 10 worst movies of 2009 so far!
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 3 of 3:
« Previous
The problem with Mono
I had a lot of hope for Mono. It seemed like a great idea. One thing that always annoyed me about Linux was that software packages I tried to install required some oddball language in order to run. All great languages, but I had to keep loading additional stuff, including the languages, just to get software to run properly. Mono looked like the golden ticket of a single layer to handle various languages. It even had Java (KVLM). But I always had the sneaky feeling that Microsoft would ruin the party by releasing a version of .NET that would make cross-platform capability impossible. And recently, they confirmed these fears with .NET 3.0. .NET 3.0 is basically 2.0 with added tiers. All the added tiers are proprietary, meaning Mono can not copy them. They are also very, very Windows specific which means that even if they weren't proprietary Mono would be unlikely to copy them. What a bummer.

http://www.netfx3.com/
Posted by: OhMyGosh   Posted on: 08/15/06 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Zdnet gone crazy or is it sun ??  hopefulcoder | 08/14/06
Novell Mono C# conversion to Java  mighetto | 08/15/06
The problem with Mono  OhMyGosh | 08/15/06

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

advertisement
advertisement

SmartPlanet

Click Here