Linked by Eugenia Loli-Queru on Wed 21st Jan 2004 07:56 UTC
Unix was originally all about not being... Multics. If Mono is to follow a similar nomenclature (just for the kicks), we have to talk about Mono's upcoming 'monopolization' and 'monarchy' in the next generation of the Unix programming land. Your see, if everything goes well, in 2 to 3 years most new Gnome user/desktop applications will be written --hopefully-- in Mono and C#. Update: Miguel deIcaza replies.
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
A few points on this article......
First, Unix was not about not being Multics. It was about simplicity. It seems that spirit has been lost today.
And the comparison to Mono / .NET is bad, because Mono is about recreating .NET on Unix.
I can't understand why a C# app would be a better GNOME app than a simple C program. Loading several MBytes of libraries only to launch a Music player seems _very_ inefficient. But that's not really my point. The real point is: .NET is a platform. GNOME is aplatform. Eugenia, what you suggest in the article is the exact same thing that everyone whined about when Microsoft tried to extend Java with proprietary Windows technologies. Mixing .NET code and GNOME code won't neccessarily make better (integrated) apps. So, Sun DID NOT make a strategic mistake by not releasing GNOME bindings for Java. Why the hell should they? The Java platform is defined and does not include GNOME.
Because Mono is developed under a free license we see more GTK# apps appear than Java apps using GTK / GNOME.
There is absolutely no advantage in writing GNOME apps in C# except for C# being the simpler, better language compared to C.