I've been trying to explain this to someone on CIX, and this effort attracted praise from a mate of mine. So, in the vague awareness that I've not posted much real content here for a while, here is that piece...
Background: the classic MacOS had what's called a "spatial" interface. If you put an icon in a particular place on your desktop, it stayed there, forever - or until you moved it. When you set a windows's size and position, the Mac remembered it, indefinitely. There was a one-to-one concordance between files on disk and icons on the screen; it was impossible to have two windows open showing the contents of the same folder, because that would mean 2 icons showing for each file in that folder. What this meant was that Mac users could organize stuff by simply putting it in a given position on the screen, on the desktop or in a folder, rather than buried in a hierarchy of folders. This is totally different from just about every other GUI ever, where the OS positions windows and icons and thus they move around randomly, and you can see a single file in an arbitrary number of places simultaneously.
Now read on...
Humans are pattern-manipulating machines and in certain domains our pattern handling works best given context.
For example: in 1994, when I was run over, I lay in my hospital bed and described to my landlord's girlfriend the location of just about every unread book among the dozens of random piles of random books dotted randomly around my bedroom. "Go for the stack to the 2nd left of the stereo, go down about 10 books, look for the one with the orange spine with black text 2 up from a silver metallic one..." And so on. This was easier than giving her a list of authors and titles. My memory works like that; most people's does. She brought in about 6 carrier bags full of books and over 90% were the right ones. IOW she got almost all of my unreads - say 90% of them - and very few reads.
Now, the proper way for me to do it would have been to have sorted and categorised all my books alpabetically and by genre. Then I could have named the ones I wanted and she could have found them readily.
But real life isn't like that. We don't do things like this unless compelled. Most of us have cluttered desks and cluttered homes and just put things down and we find them again (if we do) based on where we remember putting them and what they were near. Patterns and context.
It is how the human mind and brain work.
Now, if you are designing a computer to do this task, you can either [1] attempt to compel your users to sort and categorize, [2] make the computer remember where everything is so that they can use their associative, content-addressed human brain, or [3] provide them with rich search tools.
Most computers do #1. These days, everyone's adding #3.
What the Mac did which was unique was provide #2. This is a deep and tricky area. It's hard to do and results in some weird side-effects.
E.g.
If you are going to store where a file appears and replicate this info, you must ensure that it only appears in one place at a time - so if you click the spinner in list view to show a folder's contents, if that folder's window was open, it disappears. This makes Mac novices go "huh? WTF?" But it is necessary behaviour. It is better to do that than to refuse to allow them to click the spinner. What the designers realised that they shouldn't do, though, was allow the files in that folder to appear in 2 places at once, because once you allow that, files cease to become entities and become abstractions - just pointers to files, references.
It's OK to allow references, but they should be explicit. Like aliases. The name was italicized and there was an arrow in the corner of the icon; both readers and graphical-grasping type people get a cue.
If you provide your users with this sort of system, it makes it much more useful for the sort of person who just strews stuff around to find their files.
It's not mandatory. You could set all your folders and your desktop to automatically sort by any criterion you wished. The OS still remembered where windows were, though.
It's an extra feature, a useful extra thing that makes organising and finding your stuff easier, if you choose to use it. If you don't so choose, if you are by nature one of the sort of people who alphabetises their record collection or something (and such people scare me, personally), then set the Mac to sort everything and ignore the window placement. It's no burden.
It's an extra facility, but it's a very clever, elegant one, something that's hard to do right but very easy to miss the point of.
If you've never had it, you don't miss it. If you have had it and used it, it's great, invaluable, priceless.
But it has weird side-effects, like disappearing windows and a filer that can't show both a tree and subfolders in listings. These drawbacks are actually minor and you can work around them; it's worth it for the things they enable.
But if you don't understand the big picture and just want to fix the weird side-effects and add in "back" and "next" buttons and stuff, you collapse the whole wonderful house of cards and are left with a rather sad heap instead.
Apple could have Carbonised the Classic Finder and left it in place and working, and added on top a NeXT-style Browser. It would be like the folder view and Explorer tree views of Windows. 2 views, 2 choices, and people who use one seldom use the other. Different ways of working. Different strokes for different folks. It might have been hard to get the Classic Finder to do big scalable photorealistic icons but that would have been a small price to pay functionally, though a huge one stylistically.
But it didn't. What it did was try to makeover the non-spatial NeXT desktop and make it look like the Mac one: disks and files on the desktop, folders containing icons that you could open or nest or reuse for different views like the Windows one.
The result is a sad mishmash. It's not spatial, but it's also not an efficient tree-driven view or a browser-like one. Sometimes it remembers views; sometimes it doesn't. Sometimes it's NeXT-like, sometimes it's
superficially Mac-like, sometimes it's Windows-like. It's inconsistent.
That's not good. This is a really clever OS which does some great stuff by eliminating much legacy rubbish and starting over from a solid base, but at least one baby got tossed out with the bathwater.
October 19 2005, 00:15:26 UTC 6 years ago
A large percentage of the human race doesn't - and actually finds spacial approaches disconcerting. I suspect that someone at Apple actually finally did some user research on one of the basic axioms of the Finder...
October 19 2005, 00:33:06 UTC 6 years ago
That's the sort of spatial memory Liam's talking about here. We're not talking about the ability to visualize complicated spatial representations or hold graphs in your head. We're talking about putting something down, and having it be there when you look for it again.
October 19 2005, 00:58:42 UTC 6 years ago
I like lists. In either alphabetical order or acquired-date order. With rich search tools.
6 years ago
6 years ago
6 years ago
October 19 2005, 02:26:52 UTC 6 years ago
But as I remarked, one is not compelled to use the spatiality. Personally, I set my desktop and my document folders and the System folder and a few others to auto-arrange by type and prefer it that way.
That is not the issue, tho'. The issue is that there was this big thing that classic MacOS did that OS X doesn't, and since that thing was pretty much unique to the Mac and for many people was one of the things that made the Mac great, it's a damned shame that it's gone.
Crippling the UI for all because a minority don't benefit from an optional feature is a pretty crap reason.
October 19 2005, 10:22:50 UTC 6 years ago
6 years ago
October 19 2005, 05:53:08 UTC 6 years ago
October 19 2005, 06:48:44 UTC 6 years ago
October 19 2005, 07:33:55 UTC 6 years ago
6 years ago
October 19 2005, 13:18:25 UTC 6 years ago
October 19 2005, 08:33:20 UTC 6 years ago
October 19 2005, 07:14:41 UTC 6 years ago
That's what I thought until I met Fiona... Honestly, it's not human.
October 19 2005, 13:19:42 UTC 6 years ago
October 19 2005, 13:21:06 UTC 6 years ago
October 19 2005, 15:14:01 UTC 6 years ago
October 19 2005, 15:19:17 UTC 6 years ago
October 19 2005, 16:36:08 UTC 6 years ago
In this instance, I thought you were
It must be said that that particular pic does not show off your splendidly Adonisian physiognomy to its best advantage.
October 19 2005, 08:49:18 UTC 6 years ago
It's the right and proper thing to do!
Likewise, having your files in alphabetical order, or alphabetical by type order, is also the right thing to do!
October 19 2005, 13:27:01 UTC 6 years ago
October 19 2005, 13:47:56 UTC 6 years ago
October 19 2005, 10:15:39 UTC 6 years ago
I've never liked Macs. Every time I go near one I'm reminded of Marvin's "I can't believe you live in something so small" comment. Easy for novices to do simple things with maybe, but they run out of steam all too rapidly. I've been doing some web site testing lately and was running around 30 simultaneous open web windows - groups of 6 matching tabs in a different window for each of the four servers, then a bunch of other windows for my admin and edit functions. I also had to test on a Mac, with both Safari and IE. I could barely manage two windows simultaneously and the lack of clear feedback as to which browser or site I was switching between meant that I was forever mistaking Safari for a hoped-for "fix" on the accursed IE. The Mac clearly wanted me to have the nicest day possible for the single window I was using at that moment and kept throwing it at me full screen and hiding as much furniture as it could.
I particularly dislike Macs for the keyboard and mouse. Not enough keys. No buttons. I'm a geek. I can learn to use _anything_ if it delivers something useful. But my primary interface is my fingers and the input device and I need bandwidth here.
October 19 2005, 10:40:51 UTC 6 years ago
October 19 2005, 13:33:14 UTC 6 years ago
But OS X multitasks like a dream. It has the same sort of assortment of browsers as Windows - IE, Opera, Firefox, Mozilla are all in common, plus Safari and Omniweb and Camino and others. It has multihead support as good as Windows if not better and supports gargantuan screen resolutions.
I can't see the basis for your objections. No browser name in the titlebar? It's right at the top left of the screen, constantly.
The one thing I'll criticise OS X's window handling on is that mouse events are not passed to background windows. To activate a control, you have to click on the window to bring it to the front, then click on it again to operate the button or whatever. And I'm not sure that even this is 100% consistent across all apps.
But your critiques sound to me like they are based on unfamiliarity and problems that no longer exist.
Sure, MacOS 6 on a 512x384 screen was a bit cramped, but even there, it was actually usable.
October 19 2005, 13:59:25 UTC 6 years ago
On the pro side, the mouse angle is something OS X does right. It's perfectly operable with a single-button mouse, but if you plug in a multibutton wheel mouse, it instantly and seamlessly supports right-clicking and the wheel and the buttons become very useful. I don't like to use OS X with a single-button mouse myself.
On the browser window side, I think you may actually be echoing my point, that OS X is poor at remembering how you size & place windows.
October 19 2005, 10:17:53 UTC 6 years ago
Um... I've never come across a GUI that does this. Windows will sort icons automatically if you set it to do that -- otherwise they stick in place. (Being windows it will forget sometimes. Gnome remembers where you put them, as does KDE.
and you can see a single file in an arbitrary number of places simultaneously.
Indeed -- which is very useful.
What the designers realised that they shouldn't do, though, was allow the files in that folder to appear in 2 places at once, because once you allow that, files cease to become entities and become abstractions - just pointers to files, references.
But abstractions is exactly what they SHOULD be. I know where all my files are on my linux machine. I also know where I have made abstract shortcut links to speed my work and I know which are the shortcuts and which are the files. My windows directory on my home machine is /mnt/dos/ but it is also /home/richard/dosdisk (as a quickly accessible link from my home directory). This makes things easy.
This is the C/Unix philosophy, if you prevent people from doing stupid things by mistake you will also prevent them from doing clever things on purpose. My files are rigorously organised but I also have redundant shortcuts to enable quick access from place to place.
But real life isn't like that. We don't do things like this unless compelled. Most of us have cluttered desks and cluttered homes and just put things down and we find them again (if we do) based on where we remember putting them and what they were near. Patterns and context.
Alas this doesn't work for me. If I need to find things then I have to categorise. My CDs are alphabetised -- I can find them in a moment and if I have lent one I know it is gone. My books are loosely themed -- I cannot find them without an exhaustive check of bookshelves and even then I cannot really say. I put things down and then I don't know where they are unless I impose a filing system on them.
October 19 2005, 13:47:14 UTC 6 years ago
GNOME since v2.6 or v2.8 is adding this functionality, but the last time I checked, it remembered window positions but not that of the icons within them. KDE I don't personally know well enough to judge. So yes, they're getting there, but they're starting from 15y or so behind.
On the Mac, it was *pervasive.* Insert a floppy, position its window. Eject that floppy. Put the same disk into another Mac. The same window reappears in the same position (screen resolution allowing). TTBOMK, no other GUI can do this.
Object positioning is part of the file's metadata, is *always* preserved and so can be used as an identifying part of the file, just like its name or icon. I don't think KDE or GNOME write extra data into your filesystems to store positions, do they? 'Cos this isn't something built into ext2 or ext3 or any PC filesystem, AFAIK.
As for the broader question of abstractions, the point here, I think, is that it's harder for people to learn and to manage abstractions than simple 1:1 mappings. My mother, coming to computers in her 50s, has great difficulty with the notion of scrolling a window; the idea of this small restricted view onto a larger document, controlled by scrollbars, is not an easy one to assimilate. Now, I fear my mum will never be au fait with computers and she and I have given up hope on this one, but it demonstrates how things that seem very obvious when you're familiar with them are quite hard work for unfamiliar users to grasp.
On classic MacOS, the icon *is* the file. Move the icon, move the file. Move it to another disk, you copy it. If you want two of them on one disk, duplicate it first. It behaves like an entity in the real world, yes, via a layer of indirection, but like a /thing./ On most other GUIs, an icon is just a pointer to a file, and you have to learn this. You see a /view/ but views are mutable and you must learn to maintain a secondary, mental model of ther underlying filesystem. You're manipulating the real entity via a remote control. A simile: instead of picking up and moving things on your desk, you're working one of those arcade machines where you steer a little grabbing claw around, and your only view is through a TV camera. It's introducing a 2nd level of unnecessary indirection - computer files are not toxic waste or human innards or something else you might not want to handle directly.
I think this is why many Unix types - and quite a few old Windows hands - prefer to do their file manipulation from the command line. That way, you're not using this /tool/ that comes between you and the filesystem, you're manipulating the /real files/ underneath. The GUI becomes an barrier between the user and the filesystem.