Slashdot Mirror
Linux's Difficulty with Names
JohnTyler writes "This article at XYZ Computing takes a look at Linux's strange naming practices. When compared to their Window's equivalents, the names of many Linux programs are difficult to recognize and even tougher to remember. This may seem like splitting hairs, but it is actually an important usability issue. Just think, if you had to do a bit of graphic design which would be easier to pick out of the menu, GIMP or Photoshop? Or if you wanted to play a song, Media Player or xine?" The article is a bit thin, but it raises an excellent point.
ls, rm, df, du, etc . . . did any of the engineers at Bell Labs type 10-fingered?
But then again, you click the "Start Button" to shut down in Windows :)
This message printed on 100% post-consumer recycled electrons.
This is really more of a software designer's issue than a strictly Linux one. As we speak, I am looking for my copy of Daemon Tools on my computer, but I can't find it because it's named in the start menu by the software's manufacturer, not the name of the program. This is the case for many windows apps and I view it as a similar problem.
I suppose Outlook Express is the ideal name for an email client...as is Outlook. Acrobat is the perfect .pdf viewer or creator. Excel instantly draws to mind spreadsheets [now, but 20 years ago?]. I could go on, but why bother.
The article is just more crap slinging between two apes vying for dominance.
"Photoshop" sounds like an application for buying photographs. The writer only knows it's a graphics editor because he has read or heard it somewhere. Contrary to a myth promoted by Microsoft and others, you simply can't use a computer without having to learn anything.
Also, FWIW, and unlike any version of Windows I've ever seen, the GNOME "start" menu breaks things down by category, so you can look in the "Graphics" or "Sound and Video" submenus if you have a general idea about what you're looking for. The last Windows I sat down in front of offered me an almost flat menu of two complete columns on a high-resolution screen, and since I rarely use Windows I didn't know what more than a handful of the applications were.
Worse, in those rare instances where things were put into sub-menus, you had to look under the vendor's name to find the product. So you not only had to know that "Photoshop" means "graphics editor", you also had to know that it's published by someone named "Adobe".
Idiot-level apologetics.
Sheesh, evil *and* a jerk. -- Jade
touch...
mv...
finger..
touch..
mount...
mv...
finger...
unmount...
sleep...
Seriously, I agree. I think that is why I like giving SUSE to my friends/family. Telling my elder family to click on "Image Editor" is much easier than telling them to click on "GIMP."
The Kai's Semi-Updated Website Thingy
Most of these applications are listed as in the K-menu in the box I'm using are listed by function first. For example: Web Browser (Firefox) and Advanced Text Editor (Kate). That eliminates pretty much all the confusion there, doesn't it?
"This article at XYZ Computing takes a look at Slashdot's strange naming practices. When compared to their Web 2.0's equivalents, the names of many Slashdot URLs are difficult to recognize and even tougher to say. This may seem like splitting hairs, but it is actually an important usability issue. Just think, if you had to do a bit of news which would be easier to tell your friend on the phone, digg.com slash technology or linux dot slash dot dot org slash, no not linux dot slash dot dot org, i said linux fullstop ess ell aye ess haych dee oh tee fullstop oh arr gee?
The article is a bit thin, but it raises an excellent point.
liqbase
Names don't matter, it is all about training and then familiarity.
What's more intuitive, "Matt", or "Coffee Boy"?
Oh, and what does Exel and Outlook do? Does Outlook Express do it any faster?
As a technical discussion, names as handles to objects or ideas don't matter (excluding downright misleading names, like a boy named Sue): it gets down to user training. To write that "Whatever the reason, desktop Linux's usability is hindered by its naming practices" is just silly: in a work enviornment, users will use what they are trained on. At home, Grandma is going to use whatever will let her get her polaroids out of her new camera.
And Windows isn't particularly easy to use; rather, everybody has had some exposure to it.
As for your examples... once you know what they stand for ("list","remove","disk free", etc.), those commands are a hell of a lot quicker to type (and less prone to error) than spelling the words out.
When introducing new users to the linux systems at work I always end up explaining that the programs are named by clueless geeks who *think* they are funny (gnu, less, etc.). Please just ignore the stupid names and enjoy the power of the tools.
go ahead, take naming advice from "XYZ Computing", ffs.
Although it could be debated as to which platform has confusing names, i.e. what is Excel, what is Visio, what is Access, what is Outlook, ad nauseam, I actualy have a contrarian view for you.
Why give applications boring vanilla names like photoshop, media player, etc.?
With the names that are given to many linux applications it could be argued that someone new to the platform would be lost, but I say they will be lost anyway and when they do learn about the applications that meet their needs the interesting names will leave an impression which will differentiate them from the applications on competing platforms that have common names.
I would also argue that vanilla naming creates its own confusion. How many people think Internet Explorer IS the internet?
I say we stick with the fun names.
burnin
Back in the 80's, we were on teletypes (tty) with greenbar and the fast modems where using 75-150 baud modems. While I coded in the 70,s it was on punchcards, but I do know that other system were using less than 75 baud modems. Basically, each letter came at a high cost both in paper and in bandwidth. So, the commands were kept small and simple.
Look, if it really bugs you, then create your own commands, perhaps with alias or symlinks. But to think that commands were done due to lack of typing is silly.
I prefer the "u" in honour as it seems to be missing these days.
The examples given are from different companies and design teams, so it's hard to generalize them. Overall, however, popular Windows software tends to be made by companies who put a lot of thought into the naming of their product, since it will help determine how popular that product is. Many linux programming teams either go too general or try getting clever with the name ("Which greek god relates to what this program is doing?").
The problem with getting too clever is that without a strong advertising push or word-of-mouth push (Firefox), people really don't know what your program does. The problem with going too generic is that the program isn't memorable.
There's a few programs that get it right by choosing a name that's both descriptive and clever (Photoshop, Winamp, OpenOffice, etc). Point is, either get a big ad budget or take some extra time choosing a name. Of course, if your target audience isn't the general public (read: ethereal), then it doesn't really matter since computer experts will recognize software based on how good it is.
You have enemies? Good. That means you've stood up for something, sometime in your life. --Winston Churchill
You're right that many people will probably regard this as splitting hairs, and this in itself is a pretty big issue. Names (from "top-level" names like application titles down to the names of lowly index variables) are critically important in usability, as is documentation.
Yet try as I might, with the notable exception of Python, I've never been able to pick up an open-source product of any complexity that I'm not familiar with, without buying an O'Reilly book or something of the like. Flame me if you will for "not trying hard enough," but it seems to me like having to try hard goes against the definition of usability in some ways. This makes for a pretty big hidden cost.
Open-source projects are the products of engineers working on something they feel is personally important, and it's perhaps unsurprising that communication with the end user (at least on the level of completeness and polish that larger companies need to demonstrate) is not given much priority. But the end users are what will drive the victory or loss of Linux on the desktop, and I think they are already voting with their mice.
And say what you want about Microsoft - but the level of effort they put into this front (from the easy-to-understand language in setup to the MSDN) is way ahead of what I've seen from the Linux world. I think they are the ones to be applauded in this case.
Now lets see all the Windows users look at processes running, and let them all go
"Ah! alg.exe csrss.exe ctfmon.exe dllhost.exe explorer.exe internat.exe kernel32.dll lsass.exe mdm.exe msmsgs.exe mstask.exe regsvc.exe rundll32.exe services.exe smss.exe spoolsv.exe svchost.exe system winlogon.exe winmgmt.exe wisptis.exe wmiexe.exe wmiprvse.exe wscntfy.exe wuauclt.exe are running - I know EXACTLY what all that is doing."
Linux processes/apps are named from convention and are all documented. The less said about the alternative (and comparing with) the better.
No it doesn't. Is it saying 'Linux' (?) should start giving things super-generic names? Well that's a great idea. Let's call things 'Media Player'. But who gets to decide which media player gets named the definitive 'Media Player'? And they may not realise that most obvious super generic names are already trademarked by someone.
I don't see anything wrong with Gnu (General?) Image Manipulation Program. Rather effective description if you ask me.
It's not like the windows world isn't full of stupid Win* names is it? Winamp? WTF? It's a pretty tenuous link that you're supposed to guess that 'Amp' means an MP3 player.
Malike Bamiyi wanted my assistance.
The KDE guys need to Kut the Krap with the names already.
sulli
RTFJ.
You've completely missed the point.
If you're a 4th century roman citizen, you are going to have a tough time with a tank. A modern American might have a tough time too, but they are more likely to have been exposed to cars and computers and whatnot and have a greater chance to pick it up quicker than the roman citizen. Both of them will still have to be trained.
That's your point, but that's NOT the point of the article!
Take that same roman citizen, and train them in the use of a BMW. Now ask them which one they will remember more easily after they are forced to walk around without either for 2 months. Chances are they'll remember more about driving a BMW.
The point is not so much useability as it is reusability. I consider myself a pretty intelligent computer user, but I have to constantly go back to manuals and look things up to remember commands and programs. GIMP doesn't immediately invoke any devices in my memory to recall that application on demand at a later date. Photoshop instantly makes me think of images. 5 seconds later I find out it's for photo editing. I can stick that in my long term memory and remember it for later much more easily. This is how the average user thinks.
Linux geeks are going to be spending 99% of their time memorizing programs and commands that they use every day and they have to realize not everyone is going to see the world the same way they do. Shortening the word copy to cp helps the advanced linux user save typing but for less advanced users it's easier to remember the word COPY because it makes sense to a wider range of people.
"All great wisdom is contained in .signature files"
Call it flamebait if you will, but for the average user Linux doesn't even exist. It doesn't matter if it is called Linux "Alterna-OS" or some other crap, they know what shipped on the computer and don't have the time or inclination to learn anything else. Sure, the geeks love it, but why would the average person like it? Does it do more than already-installed (windows/media player/office/etc) or does it just do the same thing? See, if all it does is the same thing then Linux has NO VALUE preposition whatsover to the average joe they will only switch when alternative software has more usefulness and is not merely a clone.
I ask you, why should you care about vi when you have notepad (which does the same job with less confusing commands)? Making Xine or Helix useable requires setup and configuration of codecs, whereas it just works under windows!
For Linux to gain ground it needs to add utility without adding futility. No one is going to accept that it more trouble to get the thing to work the same way, and they would barely consider it if the improvements are only marginal. As far as features, Windows is better to average joe. It reasonably works out of the box, and there is nothing to screw up in the configuration. When Linux works like that then it will compete with Windows, but if the software included with Linux surpassed it that would be the end for Redmond. There is no way a "normal" user is going to put up with the bullshit involved with setting a Linux box up, so these Linux people should shut up about their desktop until it works or even happens and stay on the servers.
All that being said, I love Linux as far as the performance... It turns "dated" machines into useable machines, and for those that are running on a budget it may still have a place. For servers, I don't think there is a better choice you can make. But again, the Linux people need to stop thinking they have a desktop offering -- they have a toolbox of many tools but they do not have a leatherman. Desktops need to be useable by the computer challenged to qualify as an offering, and anything too complex is just missing the mark. Do you think the normal person would know much about partitions, screen mode depth and resolution, or even the goofy device names for mice or screens? These things make the whole proposition unrealistic.
-Mind
But it makes sense if you think about it.
Maybe if you think about it drunk.
You can't take the sky from me...
But your attitude is EXACTLY what is holding Linux apps back from popular adoption.
.pdf viewer or creator. Excel instantly draws to mind spreadsheets [now, but 20 years ago?]. I could go on, but why bother.
I suppose Outlook Express is the ideal name for an email client...as is Outlook. Acrobat is the perfect
The name of an app is not meant to be Literal!! It's meant to make you want to own it! If you had a choice between two toilets, the Open GNUFeces gtkSepticPort, or a CrapThrasher 3000, is there any question which you would select? Calling a graphics program The GIMP (yeah, I know it's meant to be a snarky acronym; newsflash: after the age of 16, nobody cares.) is like naming your son Susan. In fact, I've introduced the GIMP to new users (all of whom look like they'd rather be anyplace in the world than in that room at the time) with a, "Hey, look, with a name like The GIMP, it's got to be good, right? Right??"
For serious 'flagship' Linux applications, allowing the "coding community" to name them is right in line with allowing the "marketing community" to write them. It screams "Hobbyist," which is fine, if that's all you want it to be. In the early '90's, when nobody knew any better, it was not unusual for an organization's HTML jockey to also be responsible for creating the site's look and writing its content. Then, the medium matured, rapidly. When I see the names for a lot of these (very, very fine and well-coded) linux apps, I get the urge to crank Nine Inch Nails, order a double-mocha-latte, and re-read SnowCrash...
Right out of HS in 1959, I attended the Barns School of Business to learn "computer programming", which was really just using jumper cords to connect holes in a patch board to a neutral bus board on the IBM 402 Tabulator. We used the 540 Gang Punch to enter data onto punch cards for sorting in the 402 Tabulator. The purpose of "programming" was to sort punch cards so the tabulator could tabulate them and sent the results to a printer. But, I looked too young and couldn't convince employers to hire me.
So, after bumbing around on a few jobs for a few years, I went to college. Nine years after my first "programming" training, in 1968, I took Fortran-64 programming in grad school. We used the KSR-133 tele typewriter which supposedly poked along at 10CPS, but if you tried touch typing at 10CPS you couldn't push the keys hard enough to make it punch a hole in the yellow spool of tape into which your program was punched. After spending a couple hours typing in my solution to the quadradic equation I'd put my reel of yellow tape in a brown envelope and the prof would mail it to the CDC6600 computer center in a town 120 miles away. A week later I'd get a printout showing the errors in my typing and the process would start all over. If the printout contained a printing of my program followed by the answer then I had completed the task. IIRC, we completed only 3 or 4 problems that semester. The next semester the physics dept had a contract with the local bank and their B200 computer. We still used the same KSr-133 but the turnaround was the next day because we could go to the bank after hours and see our programs being run. If the errors weren't too bad we could use their KSR-133 and do a "quick" correction on the spot.
I never used Fortran after that class, and it was only ten years later, in 1978, that I got back into programming using Apple II BASIC. In 1980 I resigned my teaching job and I've been programming every since. In 46 years I've seen "programming" go from patching a breadboard to using tools like Eclipse, KDevelop, MSVC++.NET on PERSONAL computers that are millions of times faster than the 402 Tabulator, or even the IBM 1400 series transistorized computer, which was just on the horizon as I graduated from Barnes. Now, researchers are beginning to get a handle on optical and quantum computing with 10's to 100 GB of RAM and all solid state storage replacing mechanical HDs.
What a ride it has been!!!
Running with Linux for over 20 years!
I have been harping on this for years. For some reason software devs love to encode the names of their apps in some archaic symbology. I still do not understand this. While Excel and Premier do not give you an automatic clue as to what they are, at least they "sound" user friendly. I there is an honest interest into getting linux into more homes, this has got to stop. Same with the terrible documentation that surrounds many of these same packages. We have got to stop writing this stuff with the geek brain in mind, but others as well. Asking a non-tech user what libconf is, is just like asking them what a dll is. It just happens that Windows shields the user as much as possible from this. And before you all go flame me, remember that geeks like us buy much less of this compared to average Joe home user.
My
Corrected list
Linux entries are read off directly from my GNOME menu
==============
Web Browser
Windows: IE
Linux: Firefox Web Browser
Graphics Editing
Windows: Photoshop, Illustrator
Linux: GNU Image Manipulation Program, Inkscape Vector Illustrator
Movie Playback
Windows: Windows Media Player
Linux: Totem Movie Player
DVD Playback:
Windows: WinDVD, Windows Media Player
Linux: DVD Player, Totem Movie Player
Simple Text Editing
Windows: Notepad, Wordpad, TextPad
Linux: Text Editor
Instant Messaging
Windows: AOL Instant Messenger
Linux: Instant Messenger
Music Playback:
Windows: Windows Media Player, Itunes, WinAmp
Linux: Music Player
CD Ripping:
Windows: Itunes, Windows Media Player
Linux: Soundjuicer CD Ripper
CD Burning
Windows: Roxio Easy CD Creator, Nero
Linux: CD/DVD Creator
"Fighting terrorists with millitary might is like killing a mosquitor on your Dad's forehead with a rifle."
It has a lot to do with the fact that open source geeks can't afford trademark lawyers. A name like "gwksprt" may be horrible, but at least you're unlikely to be sued over it.
Let's do the comparison one more time using the names in my Ubuntu Breezy menus vs. the EXE names on Windows. Fair is fair, right?
Web Browser
Windows: iexpore, Opera, Mozilla, Firefox
Linux: Opera Web Browser, Mozilla Web Browser, Firefox Web Browser
Graphics Editing
Windows: photoshop (a place to buy photos?), illustrator
Linux: GIMP Image Editor
Movie Playback
Windows: wmp
Linux: Totem Movie Player, MPlayer, Xine, VLC Media Player
DVD Playback:
Windows: WinDVD (what titles can I win?), wmp
Linux: Totem Movie Player, Xine, VLC Media Player
Simple Text Editing
Windows: Notepad, Wordpad, TextPad
Linux: Text Editor
Instant Messaging
Windows: AIM
Linux: Gaim Internet Messenger
Music Playback:
Windows: wmp, Itunes (you tunes we all tunes to Itunes), WinAmp (I don't want Windows louder)
Linux: Beep Media Player, Rhythmbox Music Player
CD Ripping:
Windows: Itunes, wmp
Linux: Sound Juicer CD Ripper
CD Burning
Windows: Roxio, Nero
Linux: Gnome Toaster, Serpentine Audio CD Creator, Nero
It's pretty clear that Windows needs some consistency work before it will reach the level of polish and ease of use found in today's modern Linux distros. Anybody can write a story that manipulates the details in their favor.
A great many people think they are thinking when they are merely rearranging their prejudices. -- William James
Wood shop: a place where one works with wood.
Metal shop: a place where one works with metal.
Auto shop: a place where one works on cars.
Following that logic, where does one work with photos....
PhotoShop.
Secondly, I am sure you are right when you say we don't need the "brainless among the users". After all, no one wants to see Linux on the Desktop make it. We certainly don't want to see Microsoft taken down a notch or two. God forbid that someone who is a CEO/CFO/etc and knows just enough to use Windows uses Linux and decides it would be good for the 50000 workers in their company use it as well.
Thirdly, you are right, I am sure the people trying to improve the usablity of OSS are doing nothing for the open source community. Improved usablity is worthless. And, people actually using OSS do nothing for it either. Check it yourself. It is almost a law of nature.
Now, for what you convienently glossed over. Of those 20 programs in your KDE/Graphics menu, how many do you actually use? How many are actually easy to use? How many are big steaming piles of code crap? Of the programs installed on your box, how many are in permant beta? How many have not had a new release in months or years? How many have no programmers because all the sexy code has been written and no one wants to do the polish, upkeep, and maintenance?
There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
Was this back when nickels had pictures of bumblebees on them?
Where does the school board find them and why do they keep sending them to ME?
First of all, USABILITY MATTERS. This is no longer 1986, or 1994 for that matter. We know now that the usability of a system is a key to its successful deployment.
AMEN. I would go a step further and say that most technological revolutions are effectuated more so by usability breakthroughs than pure technology. The rise of the Internet was precipitated by the web browser. The widespread availibility of a graphical interface drove the adoption of personal computers. MP3's weren't even on the RIAA's radar before Napster made finding and downloading them easy.
Usability and accessibility are FAR more important that most geeks realize, probably because most of them want to use their knowledge of technology as a social lever, rather than as a boon to others.