Posted by: Anonymous Coward
on May 20, 2007 08:23 PM
> Gnome and KDE do not do hardware detection. They are desktop environments. If Kubuntu fails where Ubuntu works, it has nothing to do with Gnome vs. KDE.
This is at least partly untrue. Gnome has these underlying components that are part of the desktop base and do helper work for the environment to get together. I suspect kde has them too (probably some part of konqueror).
For example, Gnome volume manager in my experience has handled mounting and unmounting of removeable drives for complete newbies a lot better than konqueror (which crashed or locked up unmounts for usb disks) during the days of pre-Mandrake 9.x (before ubuntu came around) and we were doing some migration/training work for the Uni. Of course, I shouldn't expect those bugs to be present now, but there's that tiny little feeling in me that goes "if you don't want to mess with your USB's filesystem, unmount it either with gnome or the command-line". I guess what I'm trying to say is that whatever did his network detection may have been some underlying component of gnome (gnome-hal? gnome-oranges? gnome-apples?) that didn't work in kde.
IIRC, Kubuntu usually has the same kernel and base config as Ubuntu, only a different DE, so as a general rule, you can't blame the base for hardware detection discrepancies between the two. Maybe there's some underlying gnome-hal config or something that does it better than kde does. I wouldn't know, of course, since I'm a gnome person. Of course, the distro packagers could have just forgotten to include some daemon or something to do the autodetection for him, but if it's part of the DE, or they simply removed the gnome stuff and replaced with kde stuff (which i suspect), then it goes to show how integrated the whole thing is from the gnome standpoint.
So I guess it shows from the two examples that gnome devs really prioritize on getting a desktop first and features later.