Linked by Thom Holwerda on Sat 26th Nov 2005 17:02 UTC, submitted by Megatux
Gnome "I followed the debate about a successor for the C/C++ combination as the primary language for developing the GNOME core desktop platform very closely last month. There has been discussion about a number of options. What I would like to do on this page is give an overview how a probably less well-known language might be a viable compromise as a C/C++ successor. This language is called Eiffel and exists for over a decade. Eiffel takes the principle of Object-Oriented programming to its extremes and, as a consequence, is a very easy to learn language."
Thread beginning with comment 64988
To read all comments associated with this story, please click here.
Forget about it
by Lumbergh on Sat 26th Nov 2005 18:41 UTC
Member since:

Following the debate until now, I think there are a number of requirements which need to be fullfilled when we choose a C/C++ successor:

Just write the bindings and use it if you wish, but stop talking about "we" when there will never be consensus on such an issue.

In the somewhat ideal world "we" would have a universal runtime so everybody could just use whatever or something like XPCOM (don't know much about it), but there hasn't been much talk about that in a while and since the Gnome 3.0 idea is going nowhere fast (Havoc Pennington made a post about 3.0 a while back), it's pretty much futile to discuss huge architectural issues without also discussing a Gnome fork.

Edited 2005-11-26 18:41

Reply Score: 4

RE: Forget about it
by ma_d on Sat 26th Nov 2005 21:39 in reply to "Forget about it"
ma_d Member since:

I think the idea is for Gnome Foundation to support one other language for bindings...
The trouble with your average language binding is that they usually lose something from the original library. For example, I was playing with pygame a while back (a binding for python to SDL). It turns out it's not really full bindings, it's more like the minimal functionality you need to quickly throw together small, low complexity, 2d games. Which they are pretty honest about.
The second trouble is that they always release later than the actual library (that doesn't have to happen if the same people who are working on the library are slapping someone and saying "hey, write a binding for what I just changed."

And the biggest reason to pick one (although this isn't a problem for eiffel, since it apparently compiles to c) is that languages like python and java both incur a runtime; and many users don't have that kind of RAM just to run some tiny extra program. And developers know this; so they end up writing in c or whichever high level language is more popular on the platform (Python right now for Gnome).

That doesn't mean bindings won't happen for odd languages. But it does mean better documentation for people who develop in one of the supported languages. Some of Gnome's documentation is terrible, but the GTK documentation, for example, is wonderful.

Reply Parent Score: 1

RE[2]: Forget about it
by Lumbergh on Sat 26th Nov 2005 21:52 in reply to "RE: Forget about it"
Lumbergh Member since:

Yeah, bindings suck because they are always second class citizens, but Gnome is so stagnated in politics that nothing ever happens to address the obvious shortcomings in Gnome as a development platform that are recognized by Gnome developers.

The best intermediate term thing I could see happening is that all GUI functionality for Gnome is moved out of Gnome and into Gtk+ (which is supposed to happen), and then start working on some kind of component system like Kparts with Dbus on the backend.

Reply Parent Score: 2