Skip to main content

Ralsina.Me — Roberto Alsina's website

KDE 3.1 vs. GNOME 2.2: How GNOME became LAME

2003-03-01 00:41

Pre­pare for a flame­fest of mod­er­ate pro­por­tion­s, cour­tesy of Lin­ux­World.

If Nick Pe­tre­ley had writ­ten this ar­ti­cle, say, two years ago, it would have gen­er­at­ed enough heat to pop all the corn in Mex­i­co, though.

Spe­cial iron­ic de­mer­its for the use of a forced acro­nym as mech­a­nism for crit­i­cis­m.

Navindra Umanee / 2006-04-03 04:19:

What worries me the most is the stuff I've read about GConf on Slashdot from GNOME users. They seem to have experienced some serious issues with it.



Since GConf is being pushed for adoption by KDE by the maintainer (and who knows Red Hat might go ahead and do it to their fork regardless), I'd hate to think what that would mean for KDE.

Roberto Alsina / 2006-04-03 04:20:

Oh, I am confident that KDE wouldn't have much of a problem, or, if it did, it would be detected on beta and dropped.



The problem with the GNOME config system I think is more related to this:



http://developer.gnome.org/doc/whitepapers/SystemConfig/user-desktop.html



Since their cnfig system wasn't too documented when they started using it, maybe the switch to GConf triggered weird usage. KDE has had a very uniform API for config access since a looooong time ago, so that shouldn't be a problem.

an anonymous coward / 2006-04-03 04:36:

All the corn in Mexico? That doesn't say too much, with americans subsidizing their farmers like crazy, mexican corn farmers are switching to other activities :P

Contents © 2000-2024 Roberto Alsina