Five GNOME/Linux Desktop Issues
GNOME, one of the two main linux desktop environments and platforms has become a very popular choice adopted by most major distributions as their desktop of choice, mostly due to its simplicity and minimalist design. While it does several things ‘right’, by generally providing a straightforward experience and ‘hiding’ advanced configuration options in its gconf system, its development has been unfocused and lacking in some areas where it needs additional work.
More specifically, the desktop is lacking very basic features one could find even on the original Macintosh or Windows 1.0. I’m going to list some of those critical omissions that should be a priority for any modern desktop and that GNOME seems to have missed:
- Regional Settings. I’m really clueless as to why GNOME does not include a proper Regional Settings configuration panel by default. Sure, power users, programmers and *nixheads can sort out the enviroment variables, but this should be there anyway.
- Audio Configuration. ALSA has been the standard for years, yet GNOME is missing a proper audio configuration panel. Audio is more than setting the event sounds and choosing a backend. The advent of PulseAudio has made things much worse, especially on systems where there are more than one soundcards available. Soundcard selection and configuration should be a couple of clicks away. And this includes multi-card systems and numerous backends.
- Convoluted Settings. Why do we really need two panels for ‘Keyboard’ and ‘Keyboard shortcuts’? Why isn’t there a proper, functional ‘Service’ management panel? Why is gnome-control-center polluted with utilities such as ‘Network Tools’ and ‘System Monitor’? (hint: those are not configuration panels, but utilities). Why is ‘Default Printer’ a separate panel from ‘Printnig’ (and for those still in the 20th century, where on earth is Faxing configuration?)
- Searching, Indexing: Chaos. On Ubuntu clicking on Places -> ‘Search for files’ shows the old GNOME ‘Search for files’ utility. Clicking the lens on the top right or going to Applications -> Accessories (?!) -> Tracker Search tool starts tracker. Pressing Ctrl-F when a Nautilus window has focus shows yet another dialogue. This is totally unacceptable.
- Configuration: No CLI Requirement. There should be a concerted effort by all linux vendors, across all desktop environments to constitute a simple text based standard for configuration files with self-documenting facilities and coupled with a standard API for accessing, creating and modifying such files. This, in turn, could (possibly) allow for automatic generation of GUI applets capable of configuring every single aspect of the system in case a custom UI for a certain function is not available. Such a system would present a simpler, more pleasant experience to both users and developers. No GUI application, utility or system function should require the use of the terminal, although it should be possible to use a plain text editor to edit configuration files if that’s preferred. Since linux is a multi-desktop environment operating system, this should not be gconf, but something else; perhaps an XML-based standard.
I’ll be revisiting the topic over time in follow-up posts in order to add more usability annoyances of the modern linux desktop. Until then, I’d like to hear your comments.
Please do not ‘inform’ me of KDE’s strengths. I’m very well aware of them and I’ll provide a respective critique of its features as soon as the 4-series reaches a point of maturity worth spending some time for (I’m guessing 4.2 at the earliest, maybe a bit later).
It’s been really exhausting porting stuff to OS X
Justin Frankel lists a few reasons why Apple’s developer resources suck. While OS X has some of the most modern, most powerful APIs around, much of their functionality is undocumented, forcing developers to spend countless hours reading header files or even reverse engineering while getting to know how to use them.
Sure, AJAX, when viewed through the prism of the still world of HTML and CSS, can be beautifully dynamic. But, let’s face it, Google Earth — despite its resource-laden design and slow response on slower systems — is a much more natural, a friendlier way to view geographic data. With Microsoft trying hard to reclaim the (tech) lead on mapping (see Virtual Earth, WorldWide Telescope), it’s up to Google to stop the surge.
Enter the Google Earth API and browser plugin — software that opens up Google Earth for use within browsers and accessible by web developers. Sadly, it’s only available for Windows right now — I bet this will change soon.
WidSets. What a disappointment.
A reader of this blog sent me an email a couple of weeks ago, asking me to consider porting my Hellenic Reverse Directory Lookup widget (HRDL) for Apple’s Dashboard in Mac OS X to the Widsets service provided by Nokia. Over the past year or so I’ve been emailed another two or three times by readers asking me to ‘port’ the widget to several ‘platforms’ including Windows Vista ‘Gadgets’, Yahoo!/Konfabulator widgets etc. The reason I am writing this post in English is because I’d like to express my impression of the Widsets platform along with my explanation as to why I’m not going to bother with porting the HRDL widget to it.
»
Those using Firefox 3.0 may have noticed that by default when someone scales the content of a page, the images are resized too, a behaviour long-pioneered by Opera. Those using Firefox 3.0 on linux will be sorry to find out that upscaled images are not resampled using anything but what seems to be nearest neighbour (I haven’t checked the code): they are ugly, pixelated and definitely not pleasant to the eye.
This is well documented on the Mozilla Bugzilla repository and sadly it may be the case that it’s not fixed until Firefox 3.0 final is out. Which is a shame, as many people with higher resolution displays, especially high-resolution laptop displays that sometimes reach approximately 150dpi actually depend on the scaling functionality to be able to read stuff properly. Ironically GTK+ offers pretty decent image scaling functionality and hopefully it’s not that hard to make use of it in Firefox in the near future. Here’s an illustration of the problem. The picture on the left shows the original (unscaled) content of the ΜΠΛΟΟΓΚΛ hellenic blog search engine. The one in the middle shows the scaled version, as shown in Firefox 3.0 Beta 5 that shipped with Ubuntu 8.04. The one on the right shows a resampled version of the image using the (pretty computationally expensive) lanczos algorithm, which although not probable as a solution it’s quite close to the (realistically possible) bilinear resampling for upscaled images of this size.

You can follow the progress on this issue on the Mozilla Bug tracking page here.
10 Days to Hardy and GNOME’s ugliness.
Following on from my earlier post on the upcoming Ubuntu 8.04 ‘LTS’ release, I fear that my prediction, albeit harsh, was pretty accurate: Ubuntu 8.04 LTS should have never been branded as a Long Term Support (LTS) release. Despite the obvious shortcomings of having β-quality software (Firefox 3.0, GVFS) and new frameworks that — statistically — are going to break things for some people (Pulseaudio is one example; gvfs another) there are tons of bugs that I would classify as ‘Medium to High’ priority and that the Ubuntu devs could not possibly fix in time, don’t know about or probably don’t consider that important anyway. Despite all this, 10 days before release, Ubuntu Hardy is a ‘joy’ to use, if you can see beyond the LTS branding, treat it like a bleeding edge linux distribution and cope with the bugs and general instability that more or less define it; compiz, nautilus, the gvfs back ends, firefox — are all great; when they don’t crash.
Sadly, they do crash. More than I’d like. While I respect the decisions of the Ubuntu devs, I believe it is absolutely clear at this stage that a release as ‘bleeding edge’ as Hardy should have never been tagged with LTS. Still, I’m pretty confident that the steady stream of bugfix ‘updates’ will keep on coming (I’m counting more than 150-200MB daily) and hopefully by June Hardy will be a solid, usable release for everyone.
»
C4[1] Videos, have been available on Viddler for about a month. For Mac Developers this is probably of some interest. [via daringfireball.net]
The following image says it all really:

These past few days there’s been a flurry of WebKit posts over at Surfin’ Safari about its ACID3 performance. I guess when dealing with bugs, and given the fact that Microsoft typically needs around 5 years before simple CSS1 bugs are fixed (as an aside the first and only version of Internet Explorer to date that passes ACID2 is 8 Beta 1, released a couple of weeks ago), I was surprised to see how fast the WebKit developers worked towards passing the ACID3 test. Between 20:22 and 03:51 another three ACID3 bugs were fixed, taking the score to 99/100. I guess by tomorrow WebKit will officially be ACID3 compliant. Woohoo!
By comparison, Firefox 3.0 Beta 4 that I’m using to write this post in Ubuntu Hardy Heron Beta1 scores a somewhat respectable 68/100, although I don’t think they’ll pass ACID3 before the final version is out.



