Mono 1.0 released!!!

Everybody (me included) is totally excited by the Beta 1 launch, yet I think the Mono 1.0 release is an equally important landmark (provided it has the right quality level), my personal reasons for thinking so:

  1. Having been programming for a couple of years in Java, one of the first things that attracted me to .NET was the portable design of the CLR, for the longest time it's been a pity there was only one commercial implementation
  2. Many talented developers keep away from .NET because of its Windows (and Microsoft) dependance, now all that talented people can use C# and ASP.NET without those worries
  3. A lot of naysayers kept saying that Microsoft would kill Mono just because it's the evil empire. For all of you: I told you, you were wrong.

Alas, in spite of my excitement with Mono, I'm afraid I will have very little time to play with it: I've got my hands totally full with Whidbey and Yukon...

 

4 Comments



  • "A lot of naysayers kept saying that Microsoft would kill Mono just because it's the evil empire. For all of you: I told you, you were wrong".



    Why would Mono be killed, knowing they have been evangelizing .NET in non-Windows platforms?

  • I know, I know, it's non-sense, yet it's the kind of "arguments" you get from anti-MS people.

  • MS exists to make money, as do all commercial businesses. Mono will allow a developer to use a Linux desktop to write a .NET program that will run on Apple and Linux. That means $0 for MS. That negates the purpose of having the .NET languages/runtime.

    And the ability to run a .NET program on Linux means less reason to buy XP or Win2k3.

    There are lots of reasons why MS would want to kill Mono. The parts of Mono they can attack are known to the Mono crew and there are contingency plans in plan if such a thing were to happen.

    I think that Mono will only help MS, but it's not like MS (and every other large business over 2 years old) has never made stupid business decision before. Hopefully they'll do the right thing on this one.



    [Disclaimer: I've made all but about $350 of my income via MS-related products/projects]

  • Your quotes don't really address the relevant issues, though. Changing C# is not the issue. Forcing Mono to remove other, non-ECMA items from Mono is entirely possible and the Mono team has, like I said, already mentioned that they would either remove the functionality or try to rework those areas in order to avoid infringing MS patents.

Comments have been disabled for this content.