Originally written 21/07/2008. Images created 24/08/2008.
I recently came across something rather interesting on Ars Technica – a kind of old article, entitled “About the Finder…” (a pun based on the second menu item of the Apple menu in Mac OS 9 and earlier). In it, John Siracusa makes the case for the Spatial File Manager, and also somewhat condemns what I call the Browser File Manager (although it’s more commonly known as the navigational file manager.)
Now, Mr. Siracusa is an awesome writer, and he makes some excellent points in the article, but I have, in particular, problems with his arguments on Page 4 against the Browser File Manager. It seems all they amount to is “I’m Not Used To It, Therefore It Sucks”.
In the article, he states that the spatial file manager enables us to remember the “location” of the file, while the browser file manager makes us learn “strings” and “addresses”, forcing people to memorize text, instead of visual cues. The problem with those claims is, in reality, they are completely false. Indeed, the Browser and the Spatial employ the same methods – they simply have different ways of going about it.
Browsing and Visual Paths
When I want to find one of my sketches using Windows Explorer, I double-click My Documents, double-click My Pictures, double-click the Art folder, and double-click Sketches. Now, I know that I store my photos in a folder called Camera in the My Pictures folder. If I want to then check out the photos I took on the 25th of August 2006, I click Back, Back and then open the Camera folder and open the folder labeled “2006-08-25”.
In my mind, I know that the folder called My Documents contains another folder called My Pictures, and in that folder are two others, called “Art” and “Camera”. Therefore, I know that if I want to get to the Camera folder from the Art folder, I must first “put away” the Art folder back into the My Pictures folder (i.e click “Back”) and then “take out” the Camera folder, placing the My Pictures folder down for the moment so I can place my full attention on the Camera folder.
This is no different from real life; indeed, the only thing that’s changed is that it’s all so much faster. This is the point John was trying to make with the Spatial File Manager; however, the analogy works just as well for the Browser File Manager.
Strings and File Paths
Even when I do type paths, I don’t think of them as strings. The path \\blah\shared\test\ means that the computer named “blah” contains a folder named “shared”, which contains a folder named “test”. C:\Program Files\MarkKB means the C drive contains a folder named “Program Files” which, in turn, contains a folder named “MarkKB”.
OK, obviously, I don’t actually think that when I’m typing it in, or browsing it in Explorer; rather it all happens automatically – muscle memory kicks in, and I don’t really have to “think” much about the journey, but instead can focus on the destination.
Paths and Landmarks
The reason this works is because its the same way we remember routes to and from places: walking to school, driving to work, taking the bus – we rely on landmarks to get from point A to point B. Landmarks can be anything – T-junctions, gas stations, billboards, crossings, old folk homes, they all contribute to our muscle memory. In the example I used at the beginning, I used My Pictures as the common “landmark” to get from Art to Camera.
Indeed, when you really get down to it, a file path is nothing more than a shorthand compilation of landmarks: C:\Users\markkb\Documents\test.doc is no more different than writing Home\Tree\Shops\Gas Station\Roundabout\School. That a file path would reflect a path in real life (complete with shortcuts! ^^) comes as no surprise – after all, computers are designed to reflect the reality they were created in.
Because, y’know, otherwise they wouldn’t work at all. And that’d really suck.