A roadblock but also a non-event
Posted Jun 24, 2005 18:32 UTC (Fri) by whitemice
In reply to: A roadblock but also a non-event
Parent article: Microsoft Puts Roadblock in Front of Open-Sourcing Avalon and Indigo (eWeek)
>It was only a matter of time before Microsoft started roadblocking the
>Mono project's compatibility goals in a significant way, but to me this
>is a non-event.
Agreee, this is a non-event.
>First, .Net itself has become a non-event for Windows and the greater IT >community.
I certainly don't agree with this; a great deal of client side .NET coding is taking place.
>Added to which those people who are doing the most interesting coding
>with Mono appear to be doing Gtk# coding,
>which is entirely distinct from the issue of compatibility with a
>Do Gtk# coders, who constitute the bulk of the Mono community, really
>care about supporting further Microsoft standards?
To a point, core stuff, access to web services and what not. But this pretty much already works. C#/.NET is a great environment. Anyone who says it is "useless" should come see the running code. It is *FAR* less messy than Java (with its Jakata, Xerces, Xalan and what-not with version mania and insane class paths - sometimes when I'm in Java-land I think, "My Gawd, this is worse than Perl") and offers a very solid core of services (you don't need to add anything to work with XML, SOAP, etc...).
But some of the MIcrosoft specific stuff? Nah, I can do without it. I'm going to code to Gtk# on the client so it can run on LINUX, WIN2000, WINXP, etc... which even Avalon and whatever will never do. (Will they back-port to 2000? Even if they do, it will be a hack and poorly supported). And GTK is a *VERY* nice toolkit to work with. I hadn't done any client-side programming in 5+ years having been in the web-server-zone and I was able to knock together nice GUI apps within a day.
to post comments)