There is no longer any need to even pay lip-service to them…I’d even call it weakness of business model at this point. This is a bit of an anti-MS point, but why should OSS waste ANY time acknowlaging MS “innovation” at this point in the game. Third, and most important, Mono takes away from many other good, solid, growing, established OSS projects to chase after a MS “holy grail”. If Mono can’t provide that, pack up and go home now. That in turn allows you to “free” your self of MS OS at your leisure, if you choose to, and with minimal pain to your apps.
That has been the real success of PHP, MySQL, and apache! The fact that they are OSS, but also play nice with the windows world…mostly that within their “sphere” things are more or less consistant across OSes. While the core parts will work, again, it will always work “second-best”, even when it techinically exceeds the MS specs! The main thing I would ask here is this: Is Mono available for windows computers, with native mono compiler and CLR VM? Because unless the Mono apps can run ON WINDOWS, INSTEAD of the MS components, everybody will have to write 2 of everything…or just 1 for windows. Second, They will ALWAYS be at MS’ mercy. Look at Borland’s experience with C++ windows compilers as an example…they’ve had lots of trouble “being second” and at MS’ mercy. It will always be second-fiddle to the MS version. If they want MS C# programmers to use their product.Ĭ# sounds like a great language…VB meets Java, but the whole MS aspect is highly dangerous.įirst, the perception will ALWAYS be that Mono is the “copier” of C#. But compiling, linking and generating executable files should be done with one program Maybe I just lack the patience to fiddle with it. Novell’s IPX/SPX protoco could have been the standard Internet protocol but they wanted to keep control of it. Novell is a joke of a company they haven’t produce a marketable product since Netware 4.11 (early 90s). If you want portability, then Java is a better solution. However, Mono lacks the commitment of a multi-national like MS or Sun. Something that could be used across any platform. I am currently studying C# at college when I go to job-hunting saying this is what I studied at college employers laugh. If I was actually serious about C#, I would look into extactly the patent numbers. So, while Novell/Ximan develop mono they are leaving developers open to Copyright lawsuits from MS, who use these features. The problem with C# is that MS owns a number of patents which cover features used in implementing C#.