Outdated terminology
It occurred to me the other day that there's an incredibly common piece of jargon in software which doesn't make any real sense in the modern world; and this jargon word is not safely hidden behind the scenes where it only bothers programmers, but instead it forms an important part of the user interface of a great many programs. And I've never seen it remarked upon before, which is why I only just noticed it myself after a decade and a half of using GUIs.
That word is ‘exit’.
In the old days of single-
But none of this has been the case since the advent of the windowed GUI. Your word processor at no point defines the limits of your interaction with the computer; it's just one of many applications each of which is contained within its own window. You don't need to ‘exit’ it in order to do something else, because you're not trapped in it: you can quite happily do something else while the word processor is still running, and indeed you probably did. When you've finished word-
I suppose you could argue that you want the program to exit, to leave your screen and wander off to wherever software goes when it isn't running; but it doesn't seem to me that that's really been the intended metaphor at any point. Also it's unnecessarily inaccurate, and somewhat patronising: it smacks rather of telling small children that their deceased pet has ‘gone away’.
I don't imagine there's any getting away from it now; the word has become such standard terminology that users would probably be disoriented to find alternatives like ‘Vanish’ at the bottom of their File menu. But it struck me as interesting that this curious linguistic vestige of single-
no subject
no subject
(Of course that touches on another UI design rant, which is the casual and endemic inconsistency in deciding what should be the subject of command verb: with Exit, I'm exiting the program, but with Quit the program is quitting, at least if you choose to read it in that sense.)
no subject
no subject
no subject
no subject
"exit" still makes some sense in command-line interfaces, of course, since there often is a suspended shell to which the easiest way to return is to terminate the foreground CLI application.
no subject
opera says exit, sylpheed says exit. I don't appear to have anything else clicky open, except xdvi which doesn't have a special button for closing it.
no subject
*starts exploring menus*
OpenOffice Writer has 'exit'. That's about the only one I can find on this machine (Debian Linux, predominantly running GNOME applications).
no subject
no subject
Pursued by a bear?
no subject
no subject
no subject
no subject
Given the quality of most modern commercial software, I have the image of it all slinking off to some seedy disreputable bar somewhere...
no subject
no subject
no subject
no subject
Did you get my email this morning, incidentally? I wasn't sure what the best address to use was.
no subject
I did indeed get your email, though Hotmail helpfully labelled you as junk so I had to rescue you. The Bug Fairy now sits proudly on my desktop, thankee kindly for that! :) I may draw something based on her tonight...
"Bug fairy"
no subject
no subject
Or perhaps "Piss off and Die when *I* say, not just when you feel like it"?
I thank you.
no subject
no subject
no subject
no subject
It's annoying.
no subject
no subject
no subject
I have some other applications which have both "Close" and "Quit" options. One example is the Rhythmbox music player - which only has one main window, but if you close that window you might want the music to keep playing. Quit stops the music, Close doesn't. (There's a little notification icon left if you want to control the music playback.)
Unfortunately, if you click on the standard "X" icon in the window title, Rhythmbox performs the quit operation instead of the close operation. Which is just annoying. Hmm. *goes to report a bug*
no subject
Oh, and pterm doesn't seem to have a way of terminating itself from the menu. :)
no subject