Linked by Thom Holwerda on Mon 7th Sep 2009 22:38 UTC, submitted by EvilWells
Debian and its clones Developer Frans Pop, author of debtree, posted an article showing the evolution in size of the GNOME desktop environment in recent Debian releases. The picture he paints isn't particularly pretty: the default GNOME install has increased drastically in size over the years.
Permalink for comment 382693
To read all comments associated with this story, please click here.
Comment by kaiwai
by kaiwai on Mon 7th Sep 2009 23:24 UTC
kaiwai
Member since:
2005-07-06

I do thinnk he does go over the top in some regards although the current situation is absolutely stupid. There is gvfs which is supposed to replace gnome-vfs. By 2.28, there should be no reason why gnome-vfs is included anymore. FAM has been replaced with gamin, why then hasn't GNOME standardised on one piece of technology instead of offering numerous variations? The spiderweb of dependencies has been known for ages, there has been a plan to simplify it but no one is willing to put the hard word on the maintainers by saying, "no, if you don't upgrade your application, your application will be booted from the GNOME desktop".

I mean, Christ almighty, Bonobono (plus CORBA and numerous other components) has been deprecated for how long and Evolution *STILL* uses it?! webkit has become the de-facto standard open source rendering engine and yet GNOME is still hobbling around with gtkhtml and ghecko? All of this should have been sorted out by now - 2.28 should have heralded the shedding of all this crap.

Don't get me started on HAL; bless the cotton socks of the programmer who originally came up with something to address the original aim of trying to get Linux to 'just work' to improve the desktop experience but things should have moved well beyond HAL by now to a system where detection is based on the hardware notifying the kernel of its presence which then sends a signal via DBUS to a a hardware 'management' dispatcher which decides based on a set of rules how to handle a given device. HAL right now is still using the retarded CPU hogging, unscalable polling that even a person with computer 101 knowledge can see as being retarded.

There are problems and they're not being address; you need leadership from the top down where a target can be set, a roadmap laid down and for contributing programmers to know, "ok, this is the target we're aim to get to" instead of a project wandering around the wilderness trying to work out what is supposed to be moving towards in terms of a target.

Edited 2009-09-07 23:28 UTC

Reply Score: 9