User: Password:
|
|
Subscribe / Log in / New account

The GNOME project at 15

The GNOME project at 15

Posted Aug 17, 2012 5:44 UTC (Fri) by jmspeex (subscriber, #51639)
In reply to: The GNOME project at 15 by hp
Parent article: The GNOME project at 15

I understand that developers aren't *intentionally* pissing people off and it's just a side effect of something else. Also, I understand that making code evolve isn't easy, but rewrites tend to be even worse -- even if it looks simpler because "hey now I can understand all the code". UI or not, I can't think of any project (though there may be a handful) that really benefited from a rewrite. The only viable way I can see is when you have the resources to keep maintaining the old version until the rewrite is not only released, but achieves feature parity with the (still evolving) old version. This is what Microsoft did with NT and I'm sure it wasn't cheap.

In the end, I think the problem isn't even just for users, but for developers as well. From 1999 to ~2005, I wrote and maintained an application that had a gnome front-end. All I can say is that it was a rather painful experience. The API itself was OK (except for being C rather than C++, but I could deal with that) and it didn't take too long to get something working. The real problems came with maintaining the code with ever-changing APIs. Part of that was the gnome2 transition, which not only changed how some widgets behaved (it's OK for a major release), but also completely removed some widgets (GnomeMDI for example, which was supposed to be "the right way"). Even after the transition, APIs would keep coming and going. Oh, we're no longer supposed to use the gnome canvas, there's something new instead. Need graphs? Use GtkPlot, no use Guppi, oh wait we rewrote it and Guppi2 is much better, no but Guppi3 will be... You would never know which API you could trust to not end up being deprecated in 6 months. I stopped being involved around in that project around 2005, at which point the other main developer was working on a Qt frontend. (I still work on FOSS, but fortunately I haven't have to work with GUIs since then)


(Log in to post comments)

The GNOME project at 15

Posted Aug 17, 2012 6:54 UTC (Fri) by hp (subscriber, #5220) [Link]

That sort of code and API sanity (avoid giant rewrites, keep the API stable) is far, far better these days than back then.

In OSS one can only do so much. The libgnomeui/GnomeMDI stuff took a long time to reach consensus. So for example, in January 2001 I was apparently telling people not to use it:
https://mail.gnome.org/archives/gnome-devel-list/2001-Jan...
But, someone else would have told you to use it at that time.
It just depended on who you asked. There wasn't a dictator to decide.

There's more consensus/process/cultural-norm now than there used to be.
For example, a list of "official" API: http://developer.gnome.org/platform-overview/stable/

I was surprised by it just now, but libgnomeui appears to still be on my Fedora 17 system. So the ABI remains to this day.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds