Slashdot Mirror
Mono Blocked from MS Conference
Anonymous Coward writes to tell us that Microsoft has apparently blocked the Mono 'Birds-of-a-Feather' meeting from being held at their Professional Developers Conference for the second year in a row. Miguel de Icaza discusses the circumstances in his blog. From the blog: 'It is their conference, and they have every right to control what they will allow to be shown there, but they actively have misrepresented things.' Not terribly surprising but infuriating nonetheless.
Here you hear once more that developers who buy into .NET are not interested in developing or targeting other platforms other than Windows. Those who would want to have Linux then rather use PHP, Perl, etc. That is so crazy and ignorant that it doesn't make any sense! Or maybe, the people expressing those opinions are not "Real Software Engineers" -- or good business people for that matter.
.NET 2003 quite regularly. In fact, now that I have discovered the beauty of VMWare, it will be that much more comfortable to create projects in Visual Studio that are resting on a VMWare shared folder and use them instantly in the Linux host.
.NET 2003 with the intention to deploy and run in Windows boxes whose only .NET Framework runtime is the Mono for Windows SDK.
.NET developer that only wants to use .NET in Windows would be as silly as a PC user back in 1987 who only wanted to use IBM hardware.
.NET will be much bigger -- and better for everyone -- than Microsoft .NET alone.
.NET developer at the PDC or elsewhere that would not grin once he/she sees their application running on Linux or Mac OS X?
It is NOT an all or nothing proposition. You can develop in Visual Studio and very well target Linux, Mac OS X and anything else that runs Mono. As much as I use the totally cool MonoDevelop (a.k.a Bad Ass IDE of the future), I still use Visual Studio
But make no mistake, that is just one of those rich kids whim of mine. I have, for the past two years, used a Windows box that has mapped drives to my Samba enabled Linux boxes to achieved the same effect.
One must also keep in mind the great utility of Mono's Windows incarnation. Thanks to my add-in (sorry for the shameless plug) you can use Visual Studio and test in Mono without having a Linux or Mac OS box anywhere in sight. In some cases, I very purposefully create Mono applications using handy dandy Visual Studio
In the early 1980's IBM put out the specifications for the PC and regardless of what were their intentions back then, the world of IT has become what it is today because of all of the innovations that we later had by contributors like Compaq, Dell, HP, Apple, Toshiba and many others.
Today, being a
I say we have an extremely similar situation with the original submission from Microsoft to the ECMA of the C# language and the CLI specification. Now, in 2005, you have a great group of contributors that include Novell, Microsoft, IBM, HP and many others.
But perhaps the most striking difference from my IBM PC analogy is the role of the individual contributor. You see, I want to suggest that Open Source
No really, from a business perspective, you would have to be brain damaged to create an application or system of any sort and not hope that it can run in as many platforms (meaning customers that are willing to pay) as possible!
So you mean to tell me that there is some
For GOD sake, GET A CLUE!!!!
You hit the nail on the head. Mono is the only choice for a serious C# application. Unfortunately, the rest of the industry figured this out years ago and wrote all their code in java, which runs on all the platforms you mentioned and has nothing to do with microsoft. Why you wouldn't use an existing and mature cross platform language that is non-microsoft is beyond me.
mp3's are only for those with bad memories
It's obvious that Mono will NEVER be able to run every .NET application. As soon as Microsoft starts seeing Mono as a thread, something will happen.
BTW, where's the big wave of .NET applications?
If you can read this, thank an english teacher.
Its somewhat worse than that, Miguel has not only wasted his time, but he's suckered a large number of others developers in to expending massive effort on Mono. It is interesting and all, but it was as nearly as I can tell a complete waste of time, that could have been better spent on Java or standards not completely dominated by Microsoft. Now if there were interesting .NET web sites all over the Internet I wanted to use and had to have Mono to use on any non Windows platform then yes it would serve its purpose, I just don't think I've encountered such a web site. Are there any?
Not sure I grok why Miguel has such icon status in the open source world, he doesn't seem to have very good judgment.
@de_machina
...because Mono exists, I tell them: "Yeah right, and Windows is cross-platform because WINE exists"
Swing may be slow and crappy, java is definately not. The compromise in speed that you make in a large Java application compared to a large C++ program is negligable for most application development, and of course development in a modern OO language is much easier. Plus the tools for java such as IntelliJ and Eclipse are still a year or two ahead of microsofts intellistudio and about 5 or 6 years ahead of open source development tools.
.NET platform.
Java on desktop linux will die unless a good open implementation becomes popular like harmony/GCJ etc. Java is of course firmly entrenched in many banks and large development companies because its the only modern development platform suitable for large scale cost efficient development that isn't tied to Microsoft. It's also become increasingly popular to write large multiplayer online game backends in Java.
To make out that being a modern OO language is a disadvantage is laughable. It's a bit like saying "I'm still going to use my horse'n'cart because cars are just fad and soon we'll all be flying planes." Sure, the java platforms isn't suitable for people who haven't learnt modern development practices of for hacking togethor small or temporary scripts, but that's not it's core market.
I wouldn't declare Java dead yet, given the only viable alternatively currently is the