Jef Raskin On The Mac

der Kopf writes "Jeff Raskin, one of the creators of the Macintosh and inventor of the click-and-drag interface, states in an interview for the British newspaper The Guardian that "the Mac is now a mess. A third party manual (Pogue's The Missing Manual) is nearly 1,000 pages, and far from complete. Apple now does development by accretion, and there is only a little difference between using a Mac and a Windows machine."" While I think Raskin has some good points, I think there's a far cry between the Mac & XP.

Comments

Not jaded at all

[AKAImBatman]

And in this corner, we have Macus Nastolgious; a species of computer user who misses the way Macintoshes were before The Great Migration to a modern and flexible operating system. Be very cautious around this beast as it will use any information, no matter how irrelevant to the topic, to prove its supposed "point" about Mac OS being "superior" to Mac OS X. It is also very good at selective hearing, often ignoring words and phrases such as "modern", "virtual memory", "true multitasking", "protected memory", and "brushed metal".

If you are attacked by one of these creatures, your best course of action is to appease it with a lollipop and a Cherry iMac running Mac OS 9. Ignore the sobbing that may result, as it is only an opening for renewed attack.

In case anyone's interested, Wikipedia knows who Jef Raskin is.

Re:Not jaded at all

[William Tanksley]

Jef didn't like the old MacOS either, so your argument is beside the point. His problem with it was user interface, not technology. His complaint about the new interface is that it's more of the same, with a few inconsistencies thrown in just for good measure.

-Billy

Re:Not jaded at all

[AKAImBatman]

Instead of attacking the person, try to attack his points. Wow, look at that, you can't.

You lose sugarpuff:

A third party manual (Pogue's The Missing Manual) is nearly 1,000 pages, and far from complete.

As another poster so helpfully expanded on for me, Mac OS X has an entire Unix subsystem and feature set that are designed for power users and developers. Your average user knows nothing of these, nor do they need to. That doesn't stop people from documenting all those extra "cool" features in OS X.

Apple now does development by accretion, and there is only a little difference between using a Mac and a Windows machine.

An unsubstantiated statement. I suppose he felt that his statement about the manual should have given him the right to make this statement, except for that statement being based on flawed logic.

My original vision is outdated and irrelevant.

He recognizes that the original Mac interface is unsuitable. But then he goes on to say:

The principles of putting people first, and designing from the interface to the software and hardware, are as vital today as they were then.

Ok. But what does that mean? He gives no examples of proper interfaces, nor does he explain why OS X fails to achieve the "People first" status.

And the iMac G5? Was the original iMac a step on the correct path?

The unfoldable portable-shaped box on a stalk?

Ouch. You'd almost think he doesn't like the thing. But then he says:

It is a practical and space-saving design.

So which is it?

The truth of the matter is that he didn't actually make a single significant point in the entire article. He made several claims to the effect of Mac OS X being "a poor user interface", but never once gave an opinion as to why or how to fix it. Granted, that may be the fault of the editor, but then we need a better article. There were NO points made in this one.

Re:Not jaded at all

[john82]

More to the point, it seems that Raskin has had some chip on his shoulder since Jobs kicked him off the Mac team years ago. Raskin also uses this as another opportunity to hock his book. This is not even the first time this year. Witness an earlier occasion with Berkeley Groks in March of this year.

Re:Not jaded at all

[johnnyb]

Trust me, authors use every opportunity possible to hock their books. Just look at my sig!

Re:Not jaded at all

[Jeremy Erwin]

But virtual memory, multitasking, and protected memory ultimately have quite a lot to do with the user interface. Virtual memory allows a user to run a great many programs at once, without having to worry too much about cleaning up-- no need to close the web browser before writing a letter; no need to worry about memory fragmentation.

Protected memory ensures that if a misbehaving program crashes, the entire system isn't brought to a screaming halt. It's annoying when one's word processor crashes while one is writing a letter. It's even more annoying when the entire system is brought down as well, necessitating a lengthy reboot cycle. A user of a protected memory system need not worry about running finicky programs in the background, or discovering that an application really doesn't like being run on Tuesdays or months ending with "r"-- a program crash need not bring everything on the computer to a screeching halt.

As for multitasking-- the macs used to feature cooperative multitasking-- wherein each program would voluntarily give up control of the system. I suppose this might have been a boon for running a Real-Time Application, but many programs proved to be resource hogs. Ultimately, if one is running multiple programs at once, each with the same degree of urgency, it's better to let the operating system handle prioritizing time-slicing.

Now, some might still argue that puny humans are only capable of doing one thing at a time, and that it would be better to focus one's efforts on a single-tasking operating system-- but I believe most people are familiar with the practice of letting one's email client fetch mail in the background while responding to silly slashdot posts.

Re:Not jaded at all

[Golias]

Instead of attacking the person, try to attack his points.

When he has one, I'll give it a shot.

OS X is vastly more simple for a beginner to use than the old "System 7" Macintosh. He's coming at OS X the same way a Windows geek does, as somebody who is used to the way a different operating system does things, and therefore a slanted opinion about the way things "should" be done.

The dock, the new multi-tiered finder, and the "no button" mouse are all ultra-friendly on-ramps for a new user to get up and running on all the basic apps. Once the stuff "grandma" needs to learn to do e-mail and surf are mastered, digging deeper into the OS is remarkably simple. After a year or so with her first iMac, my previously-computer-illiterate aunt is comfortably trouble-shooting her own network issues.

The old Mac OS was simple and elegant for the apps and environments which existed in 1989, but ten years later it was getting awfully long in the tooth, and some of the paradigms which seemed like simplicity itself did not adapt well to the way people are using computers today.

Pat yourself on the back for making something which was way ahead of the pack at the time, Raskin, but stop being a crybaby now that your work has been eclipsed and made redundant.

You don't hear this kind of whining about the web from people who used to write CD-ROM encyclopedias, but this article is pretty much the same sort of thing.

GUI design

[BWJones]

Raskin has been suggesting for years now that the MacOS has failed the interface test. My impression is that he would prefer an entirely different machine that may perhaps be radically different than what we have now. If this is so, Raskin should go out and create his OS of choice. At that point, I will evaluate it but for now, I will stick with OS X. Sorry Jeff, but you appear to be concerned with designing interfaces for folks that do not know how to use computers. I know how to use computers and have found very efficient workflows that allow tremendous amounts of work to be accomplished (except when posting to Slashdot of course) using current computer interface designs. The current way of doing business with GUI's is somewhat efficient for noobies, quite efficient for intermediate users, and the GUI combined with the CLI is very efficient for advanced users. By the way, the combined GUI and CLI is done quite nicely in OS X.

Also, Raskin's complaints about Windows and OS X being similar could come down to other explanations: 1) convergent evolution or 2) Microsoft blatantly ripped off Apple in look and feel and continues to do so. I am inclined to believe both options as there are simply efficient ways of interfacing with computers in a GUI paradigm. That said, how many times have we seen MacOS features show up in Windows some time later? I am by no means suggesting they are equivalent however. OS X is so much better than Windows in terms of function and interface, but Windows has made huge strides in the last few years, although I do find myself applying the "standard" Windows scheme on my XP machines.

Re:GUI design

[IAmTheDave]

Raskin has been suggesting for years now that the MacOS has failed the interface test. My impression is that he would prefer an entirely different machine that may perhaps be radically different than what we have now.

This is an interesting point - we have had, in essence, the same UI experience since Windows 3.x, GeoWindows, and the original Apple user interfaces - it's all, at this point - increased productivity features and eye candy.

Moving away from this UI-locked experience requires radically different thought. While not touting the technology-forward-seeing abilities of movie producers and directors, you'll notice that most "UI" in future computers stand more for "User Interaction" than "User Interface" - that is, interaction becomes more integrated with daily life. Computers track eye movements, "read" thoughts, anticipate needs, and almost always have overly-simplistic and well thought out data displays (my favorites are displays on panes of glass.)

Point is, as pretty as the Mac OSX interface is (and it is...) making it prettier and reevaluating the decades-old principals of PC user interfaces and user interactions are completely different topics.

Re:GUI design

[Duke Thomas]

Raskin has been suggesting for years now that the MacOS has failed the interface test. My impression is that he would prefer an entirely different machine that may perhaps be radically different than what we have now. If this is so, Raskin should go out and create his OS of choice.

He did, though it was a long time ago. See information on Raskin's Canon Cat. It would be interesting to see him make a more modern computer interface, but he seems content to just make vague complaints nowadays.

Re:GUI design

[Chief Typist]

Sorry Jeff, but you appear to be concerned with designing interfaces for folks that do not know how to use computers.

This is an important thing that I think Jef and many other UI researchers are missing. There aiming at an old target -- back in the 80's there were a lot of people who didn't know how to use a computer. Having a PC at home or school was rare.

These days, there are kids who have never known what it's like to live in a house without a computer. Or a school that has a computer lab. Like learning a language, it becomes second nature as you grow up. You get to the point where you don't even know that you know it.

As time passes, the proportion of the population that "gets it" becomes much larger than the part that needs a simpler UI.

Of course, there will always be people that need dead simple UI, and it's appropriate for many specialized interfaces (e.g. the iPod.) But it seems to me that research towards more complicated UIs (and how to manage the complexity) would be a better course -- that's where the "computing population" is headed.

-ch

Re:GUI design

[TuringTest]

That's bullshit. Try reading about Raskin's opinions on user interfaces before critizising him. A guy who invented the Mac interface deserves at least that.

My impression is that he would prefer an entirely different machine that may perhaps be radically different than what we have now. If this is so, Raskin should go out and create his OS of choice.

He is doing it. It's called The Humane Interface, and you can download it from sourceforge and give it a try.

Given that some strengths of this interface are the same which make the CLI a good tool for advanced users, you should at ponder about it for a while.

If you believe that the current GUIs is "quite efficient" for intermediate users then you have not seen many of then doing something even a little bit complex. This quote from the interview perfectly resumes the real situation:

" There has been immense progress, primarily in the richness of applications. But all this power is lost on many people, and impedes the utility of it for the rest, because of the unnecessary complexity of using computers. "

You have to bear in mind that the human brain is a processor with limited power, it's main bottleneck being it's small short-term memory. Also the Input/Output protocols are constrained by perceptive capabilities. A guy who promotes design ing software optimized for this restrictions is worthy of some respect, moreover given that he is able to provide some actual solutions.

Re:GUI design

[pavon]

Sorry Jeff, but you appear to be concerned with designing interfaces for folks that do not know how to use computers.

Having read his book, I don't think that that is the case at all. The main thrust of his dream OS is to get rid of a certain class of errors (modal errors) which cause problems, regardless of your skill level. Infact the more you become familiar with the system the worse they get. A perfect example of this is shortcut keys. I have to use a half dozen text editors in windows, (for various IDEs etc), each of which has keyboard shortcuts. After using an interface for a while you get used to it and the actions become reflexive. So I find myself constantly hitting the wrong shortcut key in the wrong program. Is find Ctrl-F, Ctrl-S, or Ctrl-E, F3, or Shift-F3? I reflexively hit Ctrl-F, to find myself with a forwarded email or error message. The Mac is better because more of the shortcuts are standardized and more applications actually follow them, but I still run into the error. These errors decrease my productivity slightly, but more importantly they make using the computer frustrating. It is impossible not to develop a reflex when you use an interface often, and when that reflex betrays me, and the computer does not do what I expected because someone swapped the gas and brake pedals out from under me, it makes me agrivated. So that is his primary vision - not necisarrily to make computers easier or more efficient but more pleasant. Concidering how much stress there is concerning computers even among people who know how to use them, I think that this is a laudable goal.

But in addition to that I also get the impression that he is overly obsessed with perfection in interface efficiency and elegence. Think of the kind of person who will spend days hand coding assembly, even when the same program written in python still has tons of CPU cycles to spare. His current prototype project to implement his OS seems bogged down in optimizing the low level atomic user interactions. Theortically, some of these changes will let me work faster, but in reality, my limiting factor when typeing is not how fast my fingers move, but how fast my brain words and rewords what I want to say. The same for 2D and 3D graphics.

His arguments in this article are also primarily esthetic - OS X is very complicated and no-one will every understand it all. It is the age old argument between an elegant, small well-designed system, and an amalgemation of existing parts which does the same tasks, but is 10 times more complex because it carries the baggage of compatibility.

I sympathize with his desires, but I don't know that complete elegance will ever win out over ugly practibility. Elegant systems are a joy to use for tasks that mesh with the flexibility built into the system, but once one needs to do something that doesn't quite fit the system, the grand design becomes an obsticle instead of a help, and those loosely bound, ugly amalgamations begin to look more appealing for the absolute freedom that they provide.

Re:GUI design

[nlper]

A guy who invented the Mac interface deserves at least that.

Are you freakin' nuts? What Raskin wanted to create in the original Macintosh project was, essentially, the Canon Cat. No mouse, no GUI, no 32-bit CPU. In short, an information appliance rather than a computer, and something no one would ever recognize as a Macintosh. He lost a power struggle with Jobs early on, when his Mac team was a half-dozen people, and left Apple.

Viz, www.folklore.org

I think history has pretty much spoken on the viability of his design choices, especially the relative success of the Cat vs the Mac's GUI. Ask yourself this, if those leap keys were such a breakthrough in the UI, why hasn't something analogous caught on in the last two decades?

Tyler

Boinc has a diffrent view

[stecoop]

The quest for CPU power has been largely defeated by bloated software in applications and operating systems. Some programs I wrote in Basic on an Apple II ran faster than when written in a modern language on a G4 Dual-processor Mac with hardware 1,000 times faster.

That is quite odd of him to say. I just checked on seti@home, climate prediction and predictor@home via boinc, I don't see any Apple IIs on top of any lists. Well maybe the distributed computings teams should hire Jef Raskin and his Amazing Basic programming abilities - right?

I think sometimes, you wake up for an interview and haven't had coffee yet and say things that are not quite what you intended - it happens to me all the time ya know...

Re:Boinc has a diffrent view

[benhocking]

Yeah, I'm not buying it either. Certainly we all know where he's coming from - the boot up time on an old Apple II was faster than the boot up time on a modern Mac or PC. However, I cannot imagine how a useful program can be faster on an Apple II than any modern language on any modern hardware. I suspect he's taken the boot-up analogy and way over extended it.

I remember having an old program that calculated bifurcation trees that used to take 24 hours to complete on my old Compucolor II (which as you all know, was made by that wildly successful company Intecolor). When we got an Apple II, I ported it over to Apple Basic (from Compucolor Basic, the graphic commands of which are horrifyingly delicious) and got about a 20-fold increase in speed. Now I only had to wait a couple hours. If I run that same program today on a modern computer (using a modern language and a modern compiler) it finishes too quickly to time without using a timing macro. (I haven't run it in 5 years or so, and even then it was too fast to accurately time - less than a couple seconds, as I recall.) Granted, I might be misremembering some details, and I might have improved the efficiency of the program myself. However, it was a fairly simple program, so I'm not sure how I could have written it that inefficiently.

Re:Boinc has a diffrent view

[russellh]

Remember hotjava? Sun's first introductino to java? we all made fun of it because hey, tic-tac-toe on expensive 1996 Sun hardware, at 1979 speeds. And it still looks like crap. Yet another new interface. What the hell have we done in the meantime? That's what Jef is talking about. Not scientific number crunching and transistor count.

Re:Boinc has a diffrent view

[Anonymous Coward]

Congratulations. You missed his point entirely. He's talking about the relative speed of operating systems, applications and processors, vs. the absolute growth in processor speed. It's quite obvious to any of us who've been around for a while, that, for example, this web-based text entry box is much slower than typing on a vic-20's console.

Is This Personal?

[cyngus]

People on other websites have pointed out that Jef may be a bit off the mark and is still taking things personally from back when he was on the original Macintosh design team. Reportedly he was against the mouse driven interface and other things we've grown quite used to. It seems to me that Jef is very much an interface purest, promoting the most highly efficient and cleanest interface possible. Unfortunately, this doesn't necessarily translate to the most user friendly experience. I've tried his humane computing environment and while I'm certain that my productivity would jump once I got into the proper thinking mode, I don't really have time to learn the mental model for proper interaction with it. At the end of the day his opinions on interface design tend to me far more academic and far less pragmatic. What he says may be *right*, but impractical for mainstream computing.

That _is_ a nice sharpener

[laird]

That is a nice blade sharpener.

I think that he's right that MacOS X is too complex to be a simple appliance. But I think that general purpose computers are by definition complex, because they can be used for *anything*, and his vision holds more true for specialized devices. For example, the iPod is elegant and transparent to use.

That being said, I'm sure that usability could always be improved. But I don't agree that there's not much difference between XP and MacOS X -- while they're similar at a very high level (mouse/windows/icons over multi-tasking OS, etc.), MacOS X is better in almost every detail. But it's best not to get into a religious war here. I can only guess that Jeff has such a radical vision for how computers could be that from his perspective XP and MacOS X aren't too different.

Hmm, kinda like Nader! :-)

Re:Anti-MS jabs

[jmays]

Are you new here?

Re:The difference is

[bigman2003]

Actually, the Mac will let you use two buttons too. I bought my wife a wireless mouse, with two buttons, and she now enjoys the thrills of 'right-clicking'. And it really does work too! Just about every time I use her computer, I right-click (because that is what I would normally do) and the menu I would expect to come up...comes up.

On the other hand- as a person who used Macintoshes from 1985, until about 1999, when I switched to Windows...I find the Mac OS X to be completely confusing, and more difficult to use than either OS 9, or Windows XP.

I don't think is is a bad OS- but it suffers from the same problem that people complain about in Windows. There are just so damn many features now, that it is difficult to figure out where stuff is.

I'm sure that if I had been using the Mac for the last 5 years, everything would be fine. But right now, I would guess that the barrier to entry for a new user is very similar for either Mac OS X, or Windows XP.

Ripping off goes both ways

[59Bassman]

Remember, Windows has had the command line from the beginning. Apple only ripped it off recently!

/end feeble attempt at humor on a Monday morning

Apple today is NeXT

[green pizza]

When Apple bought NeXT (and Steve Jobs) in 1997, the joke was "NeXT was paid to take over Apple". Indeed, Apple today is just a consumer/prosumer version of NeXT.

The original Macintosh and the original Macintosh OS had input from Raskin, but also from a whole score of designers working to make a GUI-based computer for "the rest of us". (http://www.folklore.org). Over time, Apple added more and more features to Mac OS until it became the Mac OS 9 horrible mess.

Mac OS X **IS NOT** the "Classic" Mac OS by any stretch of the imgination, the GUI and system design are 90% NeXT. Even most of the codebase is derrived from OpenStep 4.x. (And updated, obviously, also borrowing from newer versions of Mach and BSD). If you run across something about Mac OS X that seems un-mac-like or just plain weird (and isn't a true bug), it's probably an intentional NeXTism.

Raskin didn't like the NeXT in 1988, there's no reason why he'd like Mac OS X in 2004.

I fear that Raskin has made himself irrelevant

[Dragonfly]

I admire his work on the original Macintosh and recognize that he was instrumental in creating the modern GUI as we know it.

However, by failing to recognize the changes in HCI introducted by the pervasive, multi-modal, non-linear interface known as the world wide web, along with the slow but steady increase in users' basic knowledge, his comments have become more and more out of touch with reality.

It is worth noting as a postscript that his theory for a Humane Interface was strikingly similar to vi: interact with the computer by memorizing an array of keystroke commands.

not an issue

[bobalu]

I bought a PowerBook about a year ago (my first Mac) and have found that this really isn't much of an issue. Every once in awhile I have to hit the Control key to bring up a pop-up menu but not much. It took about 40 seconds to get over it the first time, since then I haven't been pining for a 2nd button.

You can always use it with a two-button mouse if you want.

The difference

[Hatta]

While I think Raskin has some good points, I think there's a far cry between the Mac & XP.

Agreed, OS X has a usable shell.

Re:The whole one-button mouse thing has to go...

[matthew.thompson]

MacOS does cater for this oput of the box.

It's the Apple Macintosh that doesn't. There is a difference between the operating system and the hardware - the combination provides an easy to use solution but does not restrict the user.

If you find a two or more button mouse that you like you are more than welcome to plug it into your Mac - and the buttons, scroll wheels and the like will work. Out of the box. Without extra software. In most applications.

All this because hte OS has been designed to cater for both modes of operation.

Seems like people want a mess...

[Anonymous Coward]

With the success of OSX and XP, it really seems like people want a mess. So KDE and Gnome are doing the right thing ;-)

Jef Raskin's involvement with the Macintosh

[allanc]

Jef Raskin is always introduced as "one of the creators of the Macintosh" when in fact the only lasting contribution he made was the name. He wanted to make a machine that was basically a brain-damaged Apple II--something that would only be able to run the applications built into its ROM, couldn't be expanded, and basically limited the hell out of its own usefulness.

He was strongly against giving it a GUI at all, that was Steve Jobs' influence.

The closest widely-marketed computer to Jef Raskin's vision of How Computing Should Be was the Commodore Plus/4.

--AC

Re:Jef Raskin's involvement with the Macintosh

[squiggleslash]

The closest widely-marketed computer to Jef Raskin's vision of How Computing Should Be was the Commodore Plus/4.

From what I've read, the closest would probably be those Royale PDAs. He was proposing a simple to use machine that run a small, fixed, set of applications.

Where did you read he was against a GUI? He was against a mouse, but everything I've read has implied the interface would, nonetheless, be graphical:

Jef did not want to incorporate what became the two most definitive aspects of Macintosh technology - the Motorola 68000 microprocessor and the mouse pointing device. Jef preferred the 6809, a cheaper but weaker processor which only had 16 bits of address space and would have been obsolete in just a year or two, since it couldn't address more than 64Kbytes. He was dead set against the mouse as well, preferring dedicated meta-keys called "leap keys" to do the pointing. He became increasingly alienated from the team, eventually leaving entirely in the summer of 1981, when we were still just getting started, and the final product utilitized very few of the ideas in the Book of Macintosh. In fact, if the name of the project had changed after Steve took over in January 1981, and it almost did (see Bicycle) , there wouldn't be much reason to correlate it with his ideas at all.

Remember, at the time of development, mice were unheard of. A graphic user interface wouldn't have implied a mouse, and many people - presumably including Raskin himself - would have considered it a complication, an extra device that would have required user learning.

Die, mice, die!

[nonmaskable]

Um before anyone follows Jef's vision of the future of human-computing interfaces, you might want to consider that he was opposed to the use of a mouse on the Macintosh.

If he hadn't been replaced by Jobs as the team lead, the Macintosh would have no mouse, using keyboard function keys instead.

Mac OS X "Manual"

[green pizza]

It's easy to write a concise Mac OS "Classic" manual when there's no command-line interface, nor are there any Unix underpinnings.

A default install of Mac OS X contains a full Unix environment. (You can opt to not install the "BSD Subsystem", which just doesn't install terminal.app and several Unix userland applications).

I've seen emacs books that are 400+ pages and I've seen a 700 page sendmail manual. There are entire volumes of perl manuals. One could easily write a 10,000 page Mac OS X "Manual".

Maybe Apple should team up with ORA to write a 100 page getting started / user manual, like NeXT did in 1988. The Mac OS X interface is actually pretty simple, and an average user can only initially see about 20 control panels, about 15 applications, and about 15 utility applications. As long as you ignore the command-line world and don't write chapters on file sharing fundamentals or netbooting, I'll bet a 100 page manual would be quite sufficent.

Re:Mac OS X "Manual"

[CODiNE]

Actually Macs DO come with a Manual... there's at least two of them... maybe 20 pages or so, I don't have one around here. The Mac OS X manual was enough to get grandma more comfortable with using iPhoto and Mail. They are printed on nice paper in full color with huge screenshots on every page. Very nice noobie-talk guiding a user through basic stuff. The other manual is specific to the model you bought... shows how to add memory and an airport card, things like that.

Raskin's Bitterness

[bstarrfield]

Jef Raskin has good reason to have been bitter about the way the Macintosh has turned out. His description of the Mac's history ( http://mxmora.best.vwh.net/JefRaskin.html) provides a good introduction.

However, UI's have had to change as computing technologies have become more complicated. When the Mac was introduced, the Internet was still in its developmental stage; computer graphics were limited; and hardware devices were essentially permanently connected to the computer (no plug-and-play type technologies). The world changed, and the interface had to change with it.

It would be great to follow Raskin's advice and reevaluate the Mac GUI - however, it's apparent that Apple is constantly trying to do this. The X GUI has had changes (remember the purple window-shade type button in the X beta's?), and will no doubt continue to change. Right now we're looking at a (I'd say) fairly succesfuly merger of Mac OS 9 and NeXT UIs. But things can always get better.

I respect Raskin tremendously, but I would take his opinions with a grain of salt. His comments should be appreciated and considered, but I certainly don't believe that Apple has abandoned its quest for usability.

Re:What i like about XP

[Anonymous Coward]

Who gives a fuck about your feelings about XP???

Re:What i like about XP

[tomcio.s]

i expected an appropriately configed G3 to do the same with OS X
Did you read the install notes on the box, or the website or during the installation process??? No.. Right that's your problem. All the info and minimum requirements are posted there.

I'm also burnt out on the brushed metal look, the costly updates and dodgy performance unless your willing to fork out big $$$
Explain to me how $999 iBook is expensive? or $799 eMac? If you don't like the look of the hardware. Well, tough. I guess you can buy anything in the gray ai32 world.

I can buy an old PC and know it will be slow - but it will work - and with everything plugged in
I won't even begin to digest this erronous statement. I will say one thing tho - minimum requirements. I have been burned by this before on the ai32 platform. Or have you ever tried using a scanner that had a proprietary pci card? I didn't think so.

Re:What is it with one-button mice?

[balaam's ass]

You said it.

As a Mac user, I'm annoyed that I have to "Option-Click", "Control-Click" and "Command-Click" --- i.e. make motions which require two hands, when a simple 3-button mouse would let me do all of these quickly and easily. How are these key-click combinations "more user-friendly" than single clicks on a multi-button mouse?

And I like your response to those who say "You can always buy a multi-button mouse". Yea. I have a Logitech USB scrollwheel mouse that I use, but why did I have to buy one??? Why didn't I just GET one that came with my Mac?

NPR interview

[cmodcmodcmod]

This NPR interview (audio) is much more interesting / in-depth:
http://www.npr.org/templates/story/story.php?story Id=1606665

Different crowd

[Anonymous Coward]

You're absolutely right - there's quite a divide between the OS 9 and OS X crowds. For instance, before OS X, I'd rather have chopped off my hands than own a mac. I made fun of mac people as dimwitted idiots who didn't really want to use a computer, or artsy-touchy-feely types I'd rather not hang around with. Not too mature, but I did.

Now, I own a powerbook. ;)

Re:The whole one-button mouse thing has to go...

[Muddles]

Other posters that posted comments like "Just plug a two button mouse in and go" are right, but they missed the point. The 2,3,4 or more button mouse is a crutch for poor interface design. (Like everything else this isn't always the case) Basically, most things that are on a right-click context sensitive menu really don't need to be there, and many developers pile things into a context sensitive menus that while sensitve to the context, are little used, and should be elsewhere. The fact of the matter is a Mac is nothing like a PC to use documents exist as floating windows outside of the application window, the file menu is always on the top, and most controls exist in floating windows alongside your document. Use a Mac without the second button for any lenght of time, and you'll realise that the crtl-click is a much cleaner way of doing things. You will also notice that on a mac the ctrl-click usually gives you far less options, again, it's by design (in safari I can view source, save the page or print it, that's it 3 options). On the otherhand, the scroll wheel is what I miss the mist when I don't have my mouse plugged into my Powerbook.. then again, the arrow keys are about 2 inches from my track-pad, so I use those.

Mac OS X hardware

[green pizza]

Mac OS X requires more horsepower than XP. There's more overhead with Mach, the Unix underpinnings, the Cocoa classes, and the Quartz PDF graphics engine. It's a tradeoff between the original (but old) NeXT code and modern clean design.

That said, I've found Mac OS X 10.3.x to run fine on a 500 MHz G3 with 384 MB of RAM and Rage 128 graphics. 10.3 will work "OK" on 350 MHz with 256 MB (basiclly the slowest slot-load iMac or slowest blue & white G3 tower). 10.2 and older are far slower, and performance on a first-generation tray-load iMac or a beige G3 is slower yet.

Rule of thumb:
With 256+ MB RAM,
OS X on Beige or Black hardware: SLOW
OS X on Colorful (slot-load) hardware: OK
OS X on Silver hardware: AWESOME

A default install of WinXP SP1a is quite sluggish on my Dell: PII/350, 192MB, RagePro. Disabling the appearance manager service (giving it the WinNT4/Win2K look) makes it quite a bit faster.

those who can do, those who cannot...

[d0n quix0te]

Design a Canon Cat. Jef's time to make an impact with his interface ideas came and went. His idea for the original Mac was implemented whole sale with the Canon Cat. It had everything Jef wanted including his stupid "LEAP" keys and an invisible interface.

The result an utter failure, Canon dropped the product in 6 months. Jef claimed that he did not get the support he wanted and had to make compromises on his vision. Bullshit, this man had his time to impress us with his interface expertise and product design skills. It was an utter failure.

Remember, Jef was a professor by training... his ideas are at best academic. If Jef had his way, the Mac would have been a glorified typewriter. It took the the genius of Bill Atkinson, Bruce Horn, Steve Jobs among many others to give us the Macintosh. These guys are the true fathers of the Mac.

Jef has a case of sour grapes, being kicked out of the Mac team by Steve Jobs, and then having his beloved Cat being canned by Canon at Steve's insistence. Jobs, insisted the Canon drop the Cat, if they were to invest in NeXT. Canon invested close to $100M in NeXT!

What we are left with is an academic who time has passed by.

As has been pointed out EVERYWHERE

[falcon5768]

He is not the father, or one of the co-creators or anything... he left the project in 1981, before they even had begun major development BECAUSE his view of the Macintosh wasnt the rest of the teams view.

Likewise if HIS view of the macintosh had made it, it would be on our kitchen table, not run any of the mahor programs it does, not have a mouse, and in all honest probably not even exist today.

One thing wrong in OS X

[sjonke]

OS X is great, but it certainly isn't perfect. For one thing it is still (and was in OS <=9, so no joy for Jeff) difficult to tell when an application is running and which application is top most. The user may be looking at some window but it may not be a window of the currently topmost application and so the behavior is not what they expect. It all started way back when with the advent of "Multifinder". Oh to wish for the good ol' days of one-app-at-a-time Single Finder.... ;)

I can't count the number of times I have had to explain, for example, that first you have to click in the AppleWorks document window and then the so-and-so menu will appear, because they had closed the last window in some other application and they are looking at an AppleWorks document, but AppleWorks is not the top application. The slightly grayed out title bar isn't much of a hint. Maybe background applications' entire windows should be grayed out/dimmed and more so (the content not just the title bar) to distinguish them from the frontmost app. Or translucent, although I find translucency to be wildly busy looking so I prefer the idea of graying out the entire window.

on the other hand...

[zogger]

... it was quite pleasant to day after day, year after year get on the computer and not care much about getting owned, or the latest windows bug du juor. Some folks never drank that MS kool aid to begin with, because they could see it was just lame. MS power users became that way from necessity a lot more than from desire, because their stuff was broken and prone to getting viruses and trojans all the time, let alone constant crashing. For every 100 times my friends had to deal with registry corruption, etc, I had 100 times of booting, getting to computing, and nothing much happening besides what I wanted to happen. It wasn't perfect, that's a gimmee, but you got to admit reality, it was way easier to use for joe average and a lot more secure. Why that would want to make someone cut of their hands is beyond me, unless you actually LIKED having broken and overly complex for no appaarent reason stuff just to give you some busywork to do with your spare time. Some folks like that for a hobby, obviously, others don't.

It's only relatively recently in the past few years, that a home consumer could get an offering from any OS vendor that was at least half assed stable and half assed secure and functional from raw noobs to advanced professional level users. Before that time, Macs had at least the security part correct, along with the GUI, and were 1/2 way to functionality across the board. that's a 2.5 rating out of 3. MS barely gets a 1.5 until recently, same with linux.. Now I would say that the top 3 OSes are tied at 2.5 still, but Mac got there a lot sooner. And if GUI isn't important, then why has it become an industry standard, across all vendors of the major OSes? Could it be because it's a good idea, that people appreciate the ease of use of GUI? I think so, so do all the folks who have developed and distributed such OSes. I'd say that's some fairly good proof.

There's a REASON that there is something beyond a CLI offered by EVERYONE now. And Apple knew this quite a long time ago and specialised in it, it wasn't an afterthought or a "me too" offering.

With that said, I switched fulltime to Linux once it hit a 2.5 rating on my personal home joe user scale, because it's freer, runs on cheaper hardware I can afford, and at least achieved parity with what I had before. I wouldn't have if it hadn't been developed to that point.

*snore*

[HarveyBirdman]

Q: And the iMac G5? Was the original iMac a step on the correct path?

A: The unfoldable portable-shaped box on a stalk? It is a practical and space-saving design. But the interface needs fixing.

Well, it's been 23 years since you left Apple, Jeff. Where's *your* fix?

One only cares about getting something done.

And a simple to use, no muss, no fuss, all in one computer fails on that front... how, exactly?

Apple has forgotten this key concept. The beautiful packaging is ho-hum and insignificant in the long run.

Insignificant to Jeff Raskin, that is.

You know, there's a reason people hide their gray boxen PCs under their desks, and a reason there exists an aftermarket case mod industry.

Ugh.

[solios]

More importantly, how many times have we seen Windows features show up in MacOS?

1. Meta-Tab : a Windows first. Swiped by Apple for OS 8.5.
2. Windows that minimize to a dock/taskbar, rather than windowshade in place : a Windows first, and the Windows-like behaviour I hate the most about OS X. 9 Windowshades, goddammit. It's a third party hack on Windows and OS X.*
3. Preview-in-filebrowser : A feature that had been standard with Explorer and missing on the Mac until OS X.

There's others, but it's been awhile since I've been a regular Windows user, so I'd be hard pressed to recall others.

Raskin had almost nothing to do with the Mac as it's known now, or as it's been known for years- his own computer design concepts called for a command line interface, not a GUI. He gets a lot of credit for the Mac but the fact is that he left Apple long before it was ever released. MacOS System 1 was shaped much more by Andy Hertzfeld, Steve Jobs and Burell Smith than it was by Raskin.

As for Windows useability.... ugh. Apple's ripped some features, but they're mostly good ones. Minus that whole "losing the windowshading" thing, which I'm still pissed about. If you want Windowshading without third party hacks, your only option these days is an X11 window manager. :|

Of course, that could lead me to ranting about the state of X11 "desktops" and how much of a letdown it is to see the big DMs turning into shit Win32 clones with bad implementations of all of the worst features of OS X jammed on top- and I've already strayed too far into troll territory, so I'll just stfu. :P

* You would think that with the zero-pixel borders around sides and bottom of non-Brushed Metal windows in OS X that they would have included windowshading or at least allowed applications to implement it on a per-app basis... but since ALL windows minimize to the dock, it's easy to make one hell of a mess out of it really, really fast in the process of working with Dreamweaver, Illustrator, Photoshop and Fireworks... not the cleanest solution in the world, thank you.