Mono Progress In the Past Year
Eugenia writes "OSNews posted an article accounting the applications created in GTK# the past 8 months, since the release of Mono 1.0. While many of them are still in their infancy, it's clear that the platform had a healthy progress, with 'super-hits' like Tomboy, F-spot, MonoDevelop, Muine & Blam! and other, less known gems, like SportsTracker, PolarViewer, MooTag, GFax, GIB, Sonance and Bluefunk. The 2.0 version of Mono is expected around May, but the developers advised distros and users to upgrade to Mono 1.1.4 despite being a beta."
How is this not like life?
Ford Explorer -- does that also access the internet?
Hyundai Accent -- is it about the korean language?
Honda Accord -- music perhaps?
People make names which they feel are the best for something. They rely on something's ability to be good at it to spread the love, so to speak. If it's good, people will remember it. If it's not good, it goes away and it's no issue. Do you really like how people went to ultrageneric names and domain speculation on the Internet? Pets.com? Mail.com? News.com?
Take a look at things which people remember. What about Napster implies filesharing? What about Suprnova? What about Google implies searching?
Naming is a magic game. Just because you don't like how others play it, does not mean they are playing it wrong. This whole "incorrect naming" meme is stupid and pointless. Start thinking critically about what you're saying before you repeat it everywhere.
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
There is nothing to "snatch": these are applications implemented in a non-Microsoft toolkit using an open language standard.
The catch is that C# and CLR are not open standards - they are just ECMA standards. Apparently it was a brilliant move by MSFT because now people will automatically believe CLR is somehow "open". In fact, a while ago Novell was asking MSFT for a clear declaration that Mono does not infringe MSFT IP. Guess what, we never heard what happened with that.
I don't see how writing Gnome applications in C# benefits Microsoft any more than writing Gnome applications in C++ or Python.
It provides a hose that MSFT can step on to end the distribution of the appications. The more critical the app is for Desktop Linux, the better for MSFT. Hopefully the apps that are written in C# will stay small and architecturally open enough to be easily rewritten in another language should that happen. We should never become too dependent on Mono, or Java, or any other proprietary technology.
Save your wrists today - switch to Dvorak
What are these good bits of which you speak? Or are we (yet again) confusing Java, the language, and Java, the platform? An argument can be made that the C# language learned and improved upon the Java language's experience. On the other hand, comparing the two platforms (i.e. runtimes and libraries) is a whole different bag. Granted, C# and .Net are possibly the best technologies to use if you are developing Windows applications.
But, to assert that these are the best options in any other environment is simply ludicrous.
Mono is in no way as mature, stable, feature rich (you name it) as the Java platform.
Pray tell where is my Mono equivalent of Jakarta, Java3D, Maven, HotSpotVM, Tapestry, Eclipse, Netbeans, IntelliJ, yadatada?
When you find them, then come back and tell me C# has "all the good bits."
Mono may have the potential to become what Java is today, but its not there yet.
I read