Actually the post points out something interesting - we are in the midst of a transformation from a pictorial communication system to an ideographic language where the connection between symbol and signified becomes arbitrary. Nothing wrong with that "arbitrariness", but the visual language continues to evolve - maybe we'll see a paper clip icon even in "Avengers"-like interfaces for this reason.
(edit: fixed typos)
To give an example, the word "microphone" has only been used to represent modern microphones since 1929. The term referred to the mouthpiece for a telephone between 1929 and ~1878, and from ~1878 until 1683, it described ear trumpets.[1]
[1] http://www.etymonline.com/index.php?allowed_in_frame=0&s...
Historically they were called directories, which I would love to see a return to from the wrong and infantilizing "folders".
1: filesystem > directories > files 2: Desktop > Folders > Documents
They're both models for (basically) the same thing. The technical incorrectness of folder doesn't interfere with usage in real scenarios, unless you expect Average Joe to be structuring data as opposed to, say, collecting media. Granted, if Average Joe had mild OCD and thought of everything he did as indexes and references to some abstract node then directories clearly makes more sense, but that would be a separate system divorced from the desktop abstraction.
Edit: Being young of course none of this is really hammered in by convention– maybe that's why I don't mind the two abstractions coexisting. Even if the terminology originated in a Windows era, it doesn't bother me in the least that Mac (and others) use it as well (for the reasons stated above).
Why yes, yes I do. Desktop environments are all attempted answers to the question "why is a computer like a writing desk?" The question is absurd in its own right, but carries additional absurdity baggage such as calling all files "documents". A movie is not a document. A computer program in binary form is not a document.
All of my machines boot into bare-ass window managers -- typically either awesome or WindowMaker. It's simple, cruft-free, and leaves more room for the programs I want to run. Aside from the shell I find an activity-based model for launching programs -- such as found in iOS, Android, OLPC, and even Windows 3.1 for pete's sake -- to be infinitely preferable to the document-centric desktop model, which assumes that the user can't fathom a computer without the machine pretending that it is some older, non-computing, manually-operated piece of office equipment.
Even if the terminology originated in a Windows era -- it didn't. It started with the 1984 Macintosh. Funny that, even Apple is moving toward an activity-based model for iOS.
The desktop model's heyday may be passing right in front of us, but more likely than not the consequences are going to lead towards even higher level abstractions. For fertility, and for clarity (so that engineers can talk to engineers, and everyone else doesn't get mistaken for a really stupid engineer).
Because Poe raved on both?
Probably too late. I work with nice guys, progammers in their late 20s, mid-30s, who have only ever known those as 'folders'.
By convention at work if it's on a unix-y OS it's a directory, if Windows it's a folder. It's just easier that way.
Besides, if you're a programmer on Windows, even if you're really young and started with .NET, I'm pretty sure the API and the MSDN docs still consistently use "directory" throughout.
See, eg:
http://msdn.microsoft.com/en-us/library/system.io.directory....
And yes, the floppy disk. Whenever I want to feel old I ask one of them if they know what that icon is, and whether they ever seen one. Best answer: "Yes ... I think I saw one at my grandmother's house ..."
Then I tell them it would fit barely half an mp3 and tell them how many you'd need for the same storage as this 2GB Micro-SD the size of my fingernail :D I love living in the future!
Until someone trumps the performance of condensor microphones in the studio, this form will remain a current and accepted form for speech input.
That's easy. When you copy something you place it onto the clipboard, when you past it you are pulling a copy off the clipboard.
So "copy and paste" or "copy and glue". How does pasting go with copying? I copy something to the clipboard (...whatever) and then copy it from the clipboard to my document. How is that like gluing something? It really makes no sense.
And then I remember cutting. "Cut and paste" makes more sense. You might cut something out of a magazine and glue it onto a collage. Okay.
But the point is that none of this matters. "Paste" is a new word that means to copy something from your "clipboard" to the current location. It's not a metaphor anymore, it's a thing in its own right. A new definition for an old word.
What's the point in inventing a new term for something, when this one makes sense and is widely understood?
> I don't see any reason that we couldn't be storing our files in abstract squares rather than folders in the sky.
...because they're called folders, and we know how to use them? If I said, "Here, have a square," is your first instinct really to think oh! that must be for putting stuff in/on? Sure, you can abstract them to just a symbol but it's unnecessary. It's not like the system cares what you call it or how you choose to display it.
> The world's most advanced phones include an icon that looks like a phone handset that you haven't touched in 20 years, unless you've used a pay phone recently.
I have in fact, but that's not the point. Again, we know the shape. There aren't many things it could be besides a phone. You could show someone a glossy brick I guess, but what good would that do? The best alternative I can think of would be something like a speaker or microphone, but where's the argument that that would actually be better?
> At some time in the past the magnifying glass became the "search everywhere" icon, but for some reason binoculars are for searching within a document.
I'm just now realizing that he must be thinking of a specific piece of software. I gathered he was on Windows, now I see he worked at MS. Is this Office? This one I agree with, but it sounds like a quirky error made by some engineer or perhaps phony UX consultant. Same goes for the clipboard– hell if I know why MS would use that icon for paste, but in no other software that I can think of is that normal.
> Envelopes
Same thing as folders. So our terminology expanded to cover abstract digital entities, but that doesn't make it a hinderance to our intuition. Folders, packages, envelopes... maybe they're too nostalgic for the bold futurist, but generally it's about as practical as you can get.
> Wrenches and Gears Who hasn't used a screwdriver? Or never seen a wrench? Even the people who don't own one probably know what it is. I'm indifferent to the gears/tools thing. It still makes sense, but I'm open to new ideas– preferably a little more clever than a circuitboard.
> Microphones For speech recognition, would an ear be better? I think most people would get the microphone bit simply from watching cartoons, talkshows, album covers etc... but I admit this will likely be more foreign in the future, and is already disconnected from people in developing countries without that much media exposure (although they apparently have an iPhone/Pad/Pod).
> Photography It's kitsch. It still makes sense because the alternative to a square with a border is a square without a border. But for all of us who still use medium/large format cameras from time to time or for work, we can simply pretend. Lenses are a-OK.
> Televisions Actually, for the large number of people who gave up cable for hulu and netflix but still want to catch the news– yes! I do have rabbit ears! Maybe it's a little too retro for most video icons, but again– it till makes sense, it just may be better suited to apps that show live broadcasts.
> Carbon Copies and Blueprints Eh, so the term's (carbon copy) a bit outdated. But then again, when was the last time I "pasted" a document together? Yeah, Drawing I. As for blueprints... it makes sense for XCode right? And CAD. We may not use blueprints so often anymore, but it's less ambiguous than "construction documents," which might as well be "layouts". Which might as well be squares with a shape on them. Etc...
Basically, this would be a far more interesting post if the author would go further into making actual suggestions. Some of it makes sense because it's intuitive, some of it makes sense because we're used to it. If you want to correct the latter, you've got to show something what's better.
Edit: ouch, that's an ugly post. Not sure if I can format it in any way.
Also, I'm looking forward to seeing what people suggest in the discussion here. It's an interesting topic for sure (and I'm sure there will be plenty of people to disagree with me).