Re: Time to heat up the new module discussion

[Alvaro Lopez Ortega <alvaro 0x50 org>]

Rodrigo Moya wrote:

>>>> It is a very different situation. While the power manager support
>>>> provides new functionality, GTK# would only provide duplicate
>>>> functionality for another development framework that overlaps
>>>> with GNOME.
>>>
>>> Perhaps I am misunderstanding, but this argument doesn't make any
>>> sense to me.
>>>
>>> Gtk# isn't an application, so by itself it's not useful and
>>> doesn't really duplicate anything.  It does provide a native API
>>> to Gtk#, but traditionally language bindings have been considered
>>> a strength of GNOME.  Gtk# calls into Gtk+, so it's not like we
>>> have two competing implementations of the toolkit here. I don't
>>> see the duplicate functionality here.
>>
>>   My mistake, I didn't explain it correctly. What I meant was that
>>   the group of Gtk# plus Mono overlaps with a big chunk of the
>>   desktop. My understanding is that GNOME is a development
>>   framework and Mono is another one completely unrelated. Both of
>>   them have quite big class libraries: XML parsers, string
>>   management, asynchronous I/O, etc.
>>
>>   Of course it is possible to use both of them for writing a single
>>   cool application, although it doesn't seem to be technically
>>   correct because of all the duplicate code: there would way too
>>   many unneeded possible failure points and wasted resources.
>>
> you are right, but what is so different with Mono that this wasn't
> raised when Python was included?

  Nothing is different. That's exactly why we shouldn't make the same
  mistake twice.

  I have nothing against Mono. Actually, you know that I'd think the
  same if it was Java, Perl, or whatever other high level language
  caring another bast class library and/or execution environment.

  Let's keep GNOME neutral and fast.. and then it will be up to each
  distro or operating system to add their own bits each (written in
  Python, Mono, Java, ..).

  We ought to reach the complete consensus before accepting the
  dependency on a framework that is probably bigger than the GNOME
  framework itself.

-- 
Greetings, alo.
http://www.alobbs.com