I think this guy (and I suppose Linux UI designers) doth protest too much. All we are asking for is the same level of innovation (however it is to delivered) on the UI level as we have had for Apache, PostgreSQL, CUPS, GCC and Linux itself. It is not our right, but we have become spoilt by all the goodies OSS delivered. So we should be allowed to demand. Like children.

The article talks of printing in Windows, Linux and OS X. A quick look at how OS X does it: All printing uses PDF as the output/intermediate format. Ghostscript + Gimp provide conversion (say to HP formats). Underlying print systems is CUPS. Built-in Samba is used for connecting to and printing to Windows printers. You never see all this (except if you really want to, then poke around in /etc/). The UIs on top control everything. You even get a progress meter (if you want) when printing to a Windows printer!

It is not so much a case of effort I think as it is one of planning and thinking carefully about what the objective is. There appears to have been a rush to emulate, which has resulted in the spray-on effect.

On Apr 02, 2004, at 07:53, Kiggundu Mukasa wrote:

Just as we were jumping in the fray, a nice and long article came out.

http://daringfireball.net/2004/04/spray_on_usability

Eric S. Raymond — the renowned Linux/Open Source evangelist/essayist — couldn’t figure out how to connect to a shared printer. So he wrote an essay describing the problem (the UI for printer configuration on his Linux system is horrible) and proposing a solution (open source developers should do a better job with UI design). Raymond wrote:

The configuration problem is simple. I have a desktop machine named ‘snark’. It is connected, via the house Ethernet, to my wife Cathy’s machine, which is named ‘minx’. Minx has a LaserJet 6MP attached to it via parallel port. Both machines are running Fedora Core 1, and Cathy can print locally from minx. I can ssh minx from snark, so the network is known good.

This should be easy, right? *hollow laughter* Famous last words…

(Side note: parallel port? What year is it in the Raymond household?)

Raymond’s description and criticism of the usability problems he encountered trying to achieve this are accurate and apt. The gist of it is that what seemed like the obvious way to go about the task was in fact completely wrong, and worse, there was no indication from the system that he wasn’t on the right track.........................




.............................................. Raymond is quite complimentary to Mac software in these articles — he holds it up as an example for Linux developers to emulate. But he fails to acknowledge that most Mac software — such as the System Prefs panel you use to connect to a shared printer — is closed source, and produced by full-time professional engineers.


He also fails to acknowledge another uncomfortable truth: Unix nerds who care about usability are switching to Mac OS X in droves. In fact, most of them have already switched. This trend isn’t necessarily a market share bonanza for Apple — all the “Unix nerds who care about usability” in the world amount to only a fraction of a percent of the general population. But it’s a trend that bodes poorly for usable desktop Linux software. Most of the talented developers still using desktop Linux are either cheapskates or free-software political zealots.

This isn’t to say desktop Linux isn’t growing in use. It is, and will continue to. But it’s growing at the bottom end of the market — cheap $400 computers from Wal-Mart. That’s a market where software usability is not a key feature.

Raymond’s stance toward Windows, however, is childish. E.g., he writes:

If the designers were half-smart about UI issues (like, say, Windows programers [sic]) they’d probe the local network neighborhood and omit the impossible entries. If they were really smart (like, say, Mac programmers) they’d leave the impossible choices in but gray them out, signifying that if your system were configured a bit differently you really could print on a Windows machine, assuming you were unfortunate enough to own one.

I question how “unfortunate” one would be, at least in this situation, given that it’s easy to configure a shared printer with Windows XP. In fact, even dear old A.T. might actually have a chance to make this work, if she were given the head start Raymond himself had at the beginning of his adventure (i.e., with the network already set up, and the printer already connected to and shared from the other PC).


**************** ***************************** Kiggundu Mukasa # Computer Network Consultancy### KYM-NET LTD. # Intranets & Internet Solutions# Plot 80 Kanjokya Street P.O. Box 24284 Kampala, Uganda Tel: +256 77 972255 +256 71 221141 Fax: +256 31 262122 *****************************************************************
-----------------------------
Paul A. Bagyenda
Digital Solutions
P.O.Box 23833
58 Bukoto Str.
Kampala, UGANDA

Tel: +256-31-262117
Mob: +256-77-507743
Email: [EMAIL PROTECTED]
Web: http://www.dsmagic.com
-----------------------------



---------------------------------------------
This service is hosted on the Infocom network
http://www.infocom.co.ug

Reply via email to