Slashdot Mirror


X vs. XP.com Site Launched

Dan Pouliot writes "I've been compiling a shootout of X vs. XP for some time, but I've finally given it it's own domain xvsxp.com. Sure, I prefer Macs, but I've tried to have this site be as objective (and thorough) a shootout as possible."

42 of 176 comments (clear)

  1. some good, some bad, etc... by sundip01 · · Score: 2, Insightful

    There's quite a bit in here, not necessarily all new observations but a pretty solid collection of opinions that I think would seem to reflect the bulk of users on both platforms....

    These comparisons are nice but for a significant number of ppl it mainly comes down to what they are comfortable with. If people don't know any better than they really aren't missing much of anything....

  2. Pricing Perspective: by Anonymous Coward · · Score: 5, Insightful

    Should be re-organized more fairly to compare offerings. The "Full" (as opposed to upgrade) figure should be emphasized in larger text, and Microsoft's Full pricing should precede its Upgrade pricing, since that's what compares with Apple's offering. "Family 5 pack" should be renamed "Five Licenses", and there should be a figure that shows how expensive it is to buy a box and 4 additional licenses from Microsoft. If Microsoft does not sell just licenses, then the price / box should be multiplied by 5.

    OS X starts seeming much more cost-effective.

    1. Re:Pricing Perspective: by afantee · · Score: 3, Informative

      >> You have to buy 4 additional macs to use "five licenses".

      No, you are wrong, idiot. I have 3 Macs running OS X at home and the family pack @ $199 is still a good deal even if it's just for 2 machines.

      >> OS X now seems quite expensive.

      You are talking shit. At amazon.com, Mac OS X sells for $96.99, much cheaper than Red Hat 8 Pro for $116.99 and Win XP Pro for $199, and comes with more and better software than the other two put together.

    2. Re:Pricing Perspective: by TheInternet · · Score: 2, Funny

      How many times are you planning on posting this? Does it look less contrived each time or something?

      - Scott

      --
      Scott Stevenson
      Tree House Ideas
    3. Re:Pricing Perspective: by guuyuk · · Score: 2, Informative

      You have one Macintosh, you buy a single license copy instead of the 5 license family pack. It's called volume licensing.

      Apple also offers other licensing options (10, 25, 50, 100, 250, etc) for people that maintain larger installations. They're just not offered in the retail section.

      But then again, I don't expect to be able to walk into a Best Buy and purchase a 50 client license pack for Windows 2000/XP (although I can do that for various Linux distros since the installation license does not even mention how many machines you can install...).

      --
      We're sorry, the phone number you have reached is imaginary. Please rotate your phone 90 degrees and try your call again
  3. Cat got my balls by orangesquid · · Score: 4, Insightful

    Damn... I thought this was X(11) vs. XP, not (OS)X vs. XP.

    I wanna see a good X vs. X vs. XP shootout. Everybody always talks about the right tool for the job; I want to see a good analysis and adaptable scoring system that shows which is really the best for which jobs.

    But, for this particular thing, my vote's for (OS)X.

    --
    --TheOrangeSquid Is it any wonder things seem so awry? We swim in a sea of confusion and don't have to think to survive
  4. We've got a long way to go! by jgardn · · Score: 5, Insightful

    I read through most of the site, and I found it pretty balanced and objective.

    When you compare Linux to Windows XP, it seems that we are not too far from having all the features we need to be wildly successful.

    But when you compare Linux to OS X, it is obvious that we are so far from the goal. Even Windows XP looks like a joke compared to the things that OS X does.

    I'm glad he put together all the little tidbits of the user interface and user experience. I think the Gnome and KDE developers are paying a lot of attention as well.

    --
    The radical sect of Islam would either see you dead or "reverted" to Islam.
    1. Re:We've got a long way to go! by hobbit · · Score: 2, Interesting

      I hope that one of the dying unix firms will see this and make a last ditch effort to save themselves by producing a new desktop.

      They'd have to compete with Apple, which would be difficult, because Apple were a dying "high design" firm who made a last-ditch effort to save themselves by putting something decent under the hood (OS X's excellence does not come from high design alone).

      --
      "Wise men talk because they have something to say; fools, because they have to say something" - Plato
  5. cat scratch fever by XnetZERO · · Score: 2, Interesting

    FYI - With Mac OS 10.3, X11 will be standard equipment...

    1. Re:cat scratch fever by Ponty · · Score: 2, Funny

      The Unix/X way of approaching interfaces? You mean the "spin the big wheel and see which way to use this time," right?

  6. Organisation, Issues by MBCook · · Score: 5, Interesting
    Overall, this site is quite nice. It does seem rather objective to me. My biggest peeve about this site is that it needs "next" and "previous" links at the bottom of each page.

    As for actual content, there are a few things that I disagree with. This person said that they are a Mac fan, so I'm not too suprised at these things. Here is what I see wrong/disagree with:

    • Numlock/number pad - This is listed in the last section as something odd. He complains that you can only use the number keys when numlock is on. His site shows that this was explained to him, but I don't think he quite "gets" it. First of all, you can have the computer start up with numlock on (I do). That said, this is a hardware issue that he's juding on, which he doesn't seem to see it that way. It's tradition (like where the capslock key is, or that there even IS a scroll lock key).
    • He talks about that, but doesn't chide the Mac for having a one button mouse. This is also a hardware issue, but it's rediculous. I have a friend who has used Macs for nearly 20 years and JUST GOT A PC RECENTLY. They didn't know what the 2nd button was for, and it took me a little time to get them to get the idea. But once they got it, they LOVED it. It's SO much more convinent than holding option and clicking. That is there to cover up for the lack of a second button. Everyone I know who uses Macs alot (real computer people, not just people who only use AOL or something like that) have bought 2+ button mice for their Macs, because they are simply superior in usuability.
    • Windows is chided for having a menubar for every application. I think this is a good thing. I find it convinent. When using OS X if I want to access a menu in a application that isn't in focus, I have to switch to that application by clicking on a window it owns, then using the menu bar. In Windows, I can just click IMMEDIATLY on the mendu that I want. That article a while ago that talked about "cruft" explained why Mac did things that way. The windows way is superior (IMHO), but he doens't agree with me. Fine. The option-click thing above is also cruft.
    • Application vs Window. I don't remember if this was mentioned, but this has always annoyed me about Macs. In windows, if I close Word or some other program by clicking on the "close" button on the top right of the window, it closes. On a Mac, the window closes but the application stays open. This wouldn't be a problem for notepad or somesuch, but for large programs like Word, Photoshop, and other things, this can eat ALOT of memeory. This too, is cruft.

    Do I have a preference? I've always liked Macs, but I use PCs because they cost less (I can build a PC for much cheaper than the lowest-end-mac costs). From Win95 on, the IBM/PC has had a superior OS over OS 7/8/9. OS X changes things. It's a great OS. Would I rather have OS X or XP? I'm not quite sure. I'd probably chose OS X, all else being equal. It's done so well. I also don't like alot of the stuff XP does. If the choice was between 2k and X, I'm not sure. I would probably go with X again, but only because of the Unix core; wihtout that it'd be 2k. I use 2k and love it. It's a very good interface.

    Of course, this is just another one of those KDE vs. Gnome (KDE for me), PC vs. Mac (PC for me), DVD-R vs. DVD+R (whichever one someone wants to give me ;), Linux vs. BSD (Linux for me) type things. It has no answer.

    --
    Comment forecast: Bits of genius surrounded by a sea of mediocrity.
    1. Re:Organisation, Issues by ElGanzoLoco · · Score: 5, Funny

      I have a friend who has used Macs for nearly 20 years and JUST GOT A PC RECENTLY. They didn't know what the 2nd button was for

      Where was he for the last twenty years? I mean, if he was in a mac-only country where nobody ever has to use a PC, please, tell me so I can start moving there right away.

      --
      Hello! I'm a disaster waiting to happen!
    2. Re:Organisation, Issues by TwoStep · · Score: 4, Insightful

      The menu bar for each window was discussed by Tog.

      Basically, having the menu bar at the top of the screen makes it infinitely tall, becuase you can flick the mouse to the top of the screen and click a menu. It makes a *very* noticable increase in accuracy and speed, especially for expert users.

      The application vs. window issue is something that you get used to pretty quickly. If you use a mac for more than a day or so it seems pretty natural. With a modern OS with modern virtual memory, it doesn't really matter if you leave it open anyway. It actually can be a pretty nice feature, especially on a system like OS X where some apps still take quite a while to start up.

      Twostep

      --
      There are 10 different types of people in this world... those who understand binary, and those who don't.
    3. Re:Organisation, Issues by Dragonfly · · Score: 5, Insightful

      Application vs Window. I don't remember if this was mentioned, but this has always annoyed me about Macs. In windows, if I close Word or some other program by clicking on the "close" button on the top right of the window, it closes. On a Mac, the window closes but the application stays open. This wouldn't be a problem for notepad or somesuch, but for large programs like Word, Photoshop, and other things, this can eat ALOT of memeory. This too, is cruft.

      Allow me to disagree. First, leaving applications open on OS X doesn't use a lot of memory. For instance, I've had MS Excel running for 6 hours now, using it off and on, and it's using 0.4% of the CPU and 1.8% of memory right now with no open windows. Photoshop behaves similarly.

      Second, why should closing an application's only open document quit the application? What if you want to open another document, or just leave the app open to save yourself the trouble of re-launching it? By confusing Close with Quit MS created yet another confusing UI metaphor, combining two different actions.

    4. Re:Organisation, Issues by drsmithy · · Score: 4, Insightful
      It makes a *very* noticable increase in accuracy and speed, especially for expert users.

      "Expert" users rarely make heavy use of menues - they use the keyboard.

      The application vs. window issue is something that you get used to pretty quickly. If you use a mac for more than a day or so it seems pretty natural.

      I've been using Macs on and off for about 8 years now and as a main machine for the last 2. I still find this behaviour annoying - although not as annoying as the lack of a quick & easy way to switch between arbitrary windows when they are obscured from view.

    5. Re:Organisation, Issues by drsmithy · · Score: 2, Insightful
      Second, why should closing an application's only open document quit the application? What if you want to open another document, or just leave the app open to save yourself the trouble of re-launching it? By confusing Close with Quit MS created yet another confusing UI metaphor, combining two different actions.

      On the other hand, why would closing all an application's windows *not* quit it ? It's just another example of how the Mac is application-centric and not document-centric. In a document-centric UI, there should be no real distincion between documents and applications - opening a file should just give you a window with that file in it and no separate "application" icon or menu floating around somewhere. Leaving the application open is, by and large, a historical hangover from when launching applications was quite slow and the performance benefit for leaving them loaded was significant. Leaving the application open may still have benefits, but there really shouldn't be anything in the UI to create a distinction between an application and a document. It also leads to nasty situations where the user isn't aware an app is running and just keeps on trying to launch it (this happens when the developer doesn't have their application do something sensible - like open a blank document - when the user attempts to launch it while it is already running).

    6. Re:Organisation, Issues by Twirlip+of+the+Mists · · Score: 4, Insightful

      On the subject of the two-button mouse: the Aqua human interface guidelines specifiy that a contextual menu should not be used for any feature that is not also accessible through another UI control. Assuming for sake of argument that all software everwhere follows the Aqua HIG, you never have to control-click on a Mac. Ever.

      On the subject of the menu bar: google for Fitts's Law.

      On the subject of quitting an application by closing its window: some Mac applications have this behavior, some don't. The virtual memory implementation in OS X works in such a way that having extra idle apps open has essentially no effect. One you hit your physical memory limit, those applications get paged out to disk and no longer occupy physical RAM until they're activated again.

      Of course, this is just another one of those KDE vs. Gnome... things. It has no answer.

      I think the purpose of this web site is to demonstrate that this is not merely a question of preference, but rather that which is the better OS can be quantified, and a conclusion reached thereby. All that's left is to argue about the methodology.

      --

      I write in my journal
    7. Re:Organisation, Issues by phillymjs · · Score: 2, Informative

      On the subject of quitting an application by closing its window: some Mac applications have this behavior, some don't.

      IME, the Mac apps that quit on close are utilities that people can be assumed to be finished working with when they close the primary window-- Calculator, Disk Utility, Key Caps, etc. Like, when I'm using Calculator, I switch away from it if I need to refer to something else. When I'm done with it, I close it. I think this fits the desktop metaphor well because switching away from the calculator is analagous to leaving it on the table in front of you, and closing it is like putting it back into a drawer when you're done with it.

      Plus most of them are so small in size that they can be relaunched just as quickly as switching to them and spawning a new window if they were still active.

      ~Philly

    8. Re:Organisation, Issues by mikedaisey · · Score: 3, Insightful

      "Everyone I know who uses Macs alot (real computer people, not just people who only use AOL or something like that) have bought 2+ button mice for their Macs, because they are simply superior in usuability."

      One of the reasons Macs rock is that application designers are forced to design for a one-button mouse--not hiding vital features up in contextual menus that only show up when your mouse is in a certain part of the screen. That's one of the biggest unsung reasons Macs will stay defaulting to one mouse--it makes better design.

      And as you point out, it's a whole $10 to get a different mouse, depending on your preference--it can be more, but it doesn't have to be. So I can't see this as a serious "problem" with the platform.

    9. Re:Organisation, Issues by afantee · · Score: 2, Informative

      >> but there really shouldn't be anything in the UI to create a distinction between an application and a document.

      Why not? An applications can run without any document window, it might be doing some house keeping at background.

      Most of the times when the user closes a document window, he or she doesn't intend to stop the application. When people open and close lots of document windows, it's very annoying that they have to remember avoiding closing the last window and killing the application by accident.

      Plus, due to the excellent virtual memory system in OS X, there is really no need at all to frequently close documents or quit applications - you can hide all the documents of the front application or all the other applications by a single key stroke, and the background apps consumes very little CPU or RAM.

    10. Re:Organisation, Issues by EricHsu · · Score: 3, Insightful
      ... although not as annoying as the lack of a quick & easy way to switch between arbitrary windows when they are obscured from view.

      Cmd-` is a big step forward in this. (It switches between an app's windows.) I still find Cmd-Tab unusable.

      I use Windows XP, X11 and Mac OS X, now. My biggest complaint with Macs is not the one-button mouse thing (for god's sake, get a $10 usb 2-button mouse and be happy, or better yet a Kensington Orbit trackball); it's not the one-menu-to-rule-them-all-thing (I don't care).

      It's the lack of good keyboard bindings for menu navigation. even the "Keyboard Navigation" mode doesn't really do it. I've been doing okay with Youpi Key (the best freeware ever). But I miss the glory days of Now Menus or was it Action Menus... I forget now, whichever one automatically added arrow and key control to all menus.

      But when all is said and whinged... I use OS X for everything I can. - Eric

    11. Re:Organisation, Issues by u2mr2os2 · · Score: 2, Informative
      Re: One button Mice
      Let's just agree that different people prefer different things. It's not like the Mac doesn't support multi-button mice and scroll wheels. And if you're going to argue that Apple not including one causes an extra cost to get one, then I'd say that probably quite a good deal of PC users go buy another mouse from the typically crappy one that came with your typically cheap PC, causing an identical extra cost.

      Re: Menubars
      True, the Mac menubar system was probably greatly influenced by the small screens we all used a long time ago, but it still very true that it has a great advantage from Fitts Law. I don't buy the idea that not having to click on a background window to select a menu item for it is an advantage. That only works when the menu item is not covered by another window and when the application does not implement that stupid metaphor MS introduced of a background app ignoring the first click as a command and just using it to bring the window to the front. This metaphor is only stupid because they only implement it in some of their apps and not system wide, so you get inconsistent behavior, which is far worse than consistently using either method.

      The other thing is the damn MDI (multiple document interface). Within an application using this mode, you get a one-menu system, which is like a Mac, and it invalidates the multi-menu-is-better argument unless you throw out MDI apps. The problem with MDI is that the windows are trapped within the host app, so most apps like this are used with the document maximized within the app (also since the MDI window management functions are lame). Now combine this with DDE or "smart" apps that open documents I click on as a new MDI window in an existing instance of the already open app, and I see the document open, but then unless I look, I don't know if its a new application window that I can just close or if its a new window within the existing app. Many is the time I've closed the app, thinking it was a new app window for the document, but it was really just a new window in the existing app, and I just closed the handful of other documents it had open. True, I'll not lose data, but I'll lose several places where I was. So now I have to have the habit of closing the MDI document window first, then see if there are any more - if none, then I can close the app window. This doesn't even start to talk about the fact that an MDI app cannot have document windows mixed with those of another app. In fact, MDI causes the app to have a filled background behind its child windows that obscures things behind it. This kind of thing is what makes the Windows way completely app-centric and totally unfriendly to a doc-centric way of thinking. And this even within the supposedly "integrated" office apps!

      Re: App not closing when last doc window closes
      I agree that it takes getting used to on a Mac the app not closing when the last doc window closes. A PC user would really like to have an app close button on the menubar, but this is again just a holdover from app-centric thinking. A PC user thinks that they are thinking "I'm done with Acrobat Reader - close Acrobat Reader", but they are really thinking "I'm done with this document". It's just that it's actually easier (ironically via Fitt's Law) to close the app rather than the document because the app close button is in the top right corner of the screen (not always if the window is not maximized, but many people do have their apps maximized), or if the app is not maximized, it is visually the primary "x" button, so you are drawn to click it first, which is made even easier since they tend to be right next to each other. This gets back to my previous point of MDIs - I wind up closing the app and every other possibly unrelated document that app had open. This is hardly acceptable UI behavior.

      What has been the complaint about older Mac OS versions, is that there was no immediate visibility of apps that were open with no documents unless they were the foreground app. The app list was a drop down list, so you couldn't see the others until you dropped it down, and since there is only one menu bar, then you don't have other menubars in the background to give you a clue (but then if you had minimized a Windows window, you would not see a menubar either). Windows had a similar problem prior to Win95 with minimized apps because they went to the "desktop" behind other windows. But now Mac OS X gives visibility to the open apps via the dock so that even if they have no open windows, you know they are open. So let's not beat up OS X for a shortcoming of OS 9 and prior had, which seens to be all that many ex-Mac users seem to remember because they don't think that things may have changed with OS X. Many only remember and criticize the cooperative multitasking of OS 9 and prior while forgetting that Win 3.x used exactly that, and Win9x still used it when 3.x programs were running (did you know that Win95 could have two 32 bit programs running but be cooperatively multitasking because they were thunking down into 16 bit code a lot of the "32 bit" code just called down to 16 bit code?).

      Re: Having those unclosed windowless apps open in the backround does not affect performance
      I mostly disagree with this. It is true that in general, this makes opening a document for one of the open apps load quicker, but as you have enough apps open to commit all your physical memory, then opening other apps will be slower because the system will have to page out the idle background apps to make room for the new foreground app. If the OS were to implement a policy of paging out apps that have been idle for a while, then you would not have to wait for a pageout to make room when opening a new app, but you would have to wait for the idle app to be paged back in when you opened a document for that idle app. However, this would be faster than reloading the app from scratch due to not needing to initialize the app.

    12. Re:Organisation, Issues by drsmithy · · Score: 2, Insightful
      Why not?

      Because the application is irrelevant and should be completely transaparent. The user doesn't (and shouldn't have to) care what application is being used to open their documents. All they care about is the data in those documents, and the UI should reflect that.

      An applications can run without any document window, it might be doing some house keeping at background.

      What possible "processing" could an interactive application be doing in the background isn't related to a open document (or analogical equivalent) ?

      In simpler terms, if you have closed all methods of interacting with an app, thus indicating you no longer want to interact with it, what possible processing could it need to be doing (excluding normal startup and shutdown procedures) ?

      Most of the times when the user closes a document window, he or she doesn't intend to stop the application.

      As previously mentioned, the user shouldn't have to think about the application at all. The whole concept is simply unintuitive.

      When people open and close lots of document windows, it's very annoying that they have to remember avoiding closing the last window and killing the application by accident.

      With a decent implementation, this shouldn't be an issue. Particularly in these days of dirt cheap RAM.

      Plus, due to the excellent virtual memory system in OS X, [...]

      I haven't tried to abuse the VM in OS X for a while, but last time I did (ca. 10.1.x), it was far from "excellent".

      [...] you can hide all the documents of the front application or all the other applications by a single key stroke, and the background apps consumes very little CPU or RAM.

      The Mac in front of me has 512MB of RAM and an uptime of less than a day. Thus far OS X has create 3 "swapfiles" of 80MB apiece for paging reasons. All that is running is X11, MSN Messenger, Mail, Safari, Terminal, Word and Excel. That's a _lot_ of memory usage.

    13. Re:Organisation, Issues by FredFnord · · Score: 3, Insightful

      >"Expert" users rarely make heavy use of menues - they use the keyboard.

      This is absolutely true, as long as you define 'expert' users as people who rarely make heavy use of menus, but instead use the keyboard.

      Or perhaps you mean to say that I'm not an expert user... after all, I've only been using computers for 20 years, and Macs for 14. And heck, I only started programming professionally 11 years ago, got my BS in Computer Science 6 years ago, and have only been professionally programming Macs full time for four years.

      (I use command keys for quitting, saving, closing windows, opening new windows, occasionally for switching between programs. Almost everything else I use the menu bar, or contextual menus, for.)

      Or, just possibly, what you really meant by the term "Expert" in your sentence was "users who still yearn for CLI"?

      -fred

      --
      Sign #11 of Slashdot overdose: You see the phrase 'moderate Republican' and you wonder if that would be a +1 or a -1.
    14. Re:Organisation, Issues by sc00p18 · · Score: 4, Insightful

      By confusing Close with Quit MS created yet another confusing UI metaphor, combining two different actions.

      dude, that's ABSOLUTELY correct, I NEVER understood the close/quit thing until I got a mac. Then I realized that Microsoft just screwed it up when they were transferring it over from the mac interface.

    15. Re:Organisation, Issues by NeuroKoan · · Score: 2, Interesting

      Liteswitch helped make cmd-tab very useful for me.

      --

      "However," replied the universe, "The fact has not created in me A sense of obligation."
    16. Re:Organisation, Issues by davesag · · Score: 3, Insightful
      Because the application is irrelevant and should be completely transaparent. The user doesn't (and shouldn't have to) care what application is being used to open their documents.

      I don't know about you but I would hate it if the many various text files I work with somehow chose their own app to run in. I regularly open tomcat log files in BBEdit for example. I open PDF files in preview mostly but sometime want to open them in smacrobat. I open most graphics in preview but every so often want to open them in photoshop. sometimes I want to open html files in bbedit, sometimes in safari, sometimes in omniweb. Same docs, entirely different applications.

      --
      I used to have a better sig than this, but I got tired of it
    17. Re:Organisation, Issues by afantee · · Score: 4, Informative

      >> What possible "processing" could an interactive application be doing in the background isn't related to a open document (or analogical equivalent) ?

      Why couldn't you MS trained monkeys see things from a slightly different angle? A file manager like Finder might have a background thread for content indexing or repairing the file system, even if there is no browsing windows.

      >> As previously mentioned, the user shouldn't have to think about the application at all. The whole concept is simply unintuitive.

      That's just your simplistic world view. People do think about applications, and frequently choose different tools for the same document.

      >> The Mac in front of me has 512MB of RAM and an uptime of less than a day. Thus far OS X has create 3 "swapfiles" of 80MB apiece for paging reasons. All that is running is X11, MSN Messenger, Mail, Safari, Terminal, Word and Excel. That's a _lot_ of memory usage.

      And my 400 MHz iMac with 512MB RAM runs 24/7 for weeks or months as a software AirPort base station for web browsing and for kidds playing games and my wife doing research (statistic analysis, Excel, Word, PowerPoint, etc). My 700 iBook is used for programming Unix / Java / C++ (X11, tcsh, bash, Ruby, Perl, JBuilder, Eclipse, NetBeans, Project Builder, Interface Builder, etc), web design and graphics (FireWorks, Flash, DreamWeaver), database (MySQL, PostgreSQL), web browsing (Safari, Camino, OmniWeb, IE), networking and web serving (FTP, Apache, SMB, AFP, Firewall, NetInfo, AirPort wireless, iDisk, iChat, iSync, Network Utility), Word, Excel, PowerPoint, QuickTime, iMovie, iPhoto, iTunes, iMovie, Mail, Address Book, OmniDictionary, World Book, and more. Typically, there are 70 to 80 processes running, and I generally don't quit applications, so they run continuously for days or weeks, and everything remains responsive virtually all the time.

    18. Re:Organisation, Issues by Anonymous Coward · · Score: 2, Insightful

      This whole document-centric theory is complete bullshit. The user, no matter how dumb or non-expert, very much does care what application is being used to manipulate their document. The average person probably has 3-4 applications that could open common file types (windows has at least three distinct applications by default that could view and html, gifs, jpgs, and text documents, for example) and the application they are actually using makes a huge friggin' difference. This sounds like some sort of budget HCI academic theory that has no value at all in the real world.

      Without even going into how severely this theoretical 'document-orientation' deviates from the actual day-to-day necessities of using real computers to do real jobs, the windows way of doing things is very annoying in the limited way it does implement your ideal.

      I have an OS X machine and a win2k machine on my desk right now. First of all, Windows is completely inconsistent about the relationship between application, taskbar entry, and document. The most annoying example of this (which I face daily) is with Word and Excel (so I'm not talking about fly-by-night shareware here. In Word, every document is its own little floaty bit that sits on the taskbar and takes up space. When you click the upper-right (visually deceptively) Fitt's-law-adhering-to 'close' X, the doc closes, and only the doc. When the last one closes, the start-up time to open a new document is insane, so I have to keep a document open and in my taskbar all the time, but that's neither here nor there. In Excel, you get a little task bar entry and a document window for each of your workbooks, but you also get a little bonus entry for the application. In Excel, though, if you click that same X, the whole application shuts down and closes all workbooks. What the shit? It's maddening.

      So the whole document-centricity of windows is very confusing. Beyond that, document-centricity is the most brain-dead idea I've ever heard. The application should be completely transparent? Why? That's retarded. The application matters a lot. All they care about is the data in those documents? No, they care about *doing* stuff to and with that data, or creating it, or inputting it. The application is a tool that provides all of these capabilities. I would argue that most non-expert users think of their computers in more application-centric ways than document anyway. Think about how many moms say, 'i'm going to go online'. They don't 'compose emails' or 'download webpages', they click the AOL icon, and 'go online'. They are first using a tool, secondly, they are producing or interacting with the product of said tool. I guess it doesn't matter if you look at that XLS file in Access or Excel.

      with a decent implementation

      Well, name an OS that has a decent implementation. It's a real issue on every platform I've used (in addition to my previously mentioned PC and mac on my desk, the Mac is ssh'd into a freebsd box)

      In simpler terms, if you have closed all methods of interacting with an app, thus indicating you no longer want to interact with it, what possible processing could it need to be doing (excluding normal startup and shutdown procedures)?

      Hmmm...be available to compose emails at a hotkey press, receive instant messages, play music, help with OS navigation (like OS X's brilliant launchbar add-on), be available as a drag-and-drop target...

      Also, you argue that given dirt-cheap ram, the relaunch penalty of the app should be very small (basically cause the OS is keeping the application loaded and pointlessly hiding functionality from you). Then, you argue that OS X's doc hiding is bad because it wastes mem and the VM isn't good enough?!?!? Put in the same dirt-cheap ram.

    19. Re:Organisation, Issues by Dominic_Mazzoni · · Score: 3, Insightful

      "Expert" users rarely make heavy use of menues - they use the keyboard.

      Bullshit. Sure, I have all of the keyboard shortcuts for my favorite development IDE and web browser memorized, so I can do a lot of work without using the mouse. But being an expert user, I also make use of dozens of other programs that I'm half-familiar with, but don't use often enough to have all of the shortcuts memorized. So I use the mouse a lot. The Mac's single menu bar really is easier to use in this case.

  7. Not entirely.... by bigBlackSabbath · · Score: 3, Insightful

    The numlock is a software thing. The mac ignores the state of numlock. I imagine the numlock is only there for people using Virtual PC or Linux/NetBSD.

    And the reason the menu bar is at the top is easy - that way you can close and open documents without having to restart the application again. Mozilla on Windows means if I close the browser, I have to restart it. The alternative is the convoluted window inside a window technique Microsoft uses everywhere, such as in Word. The menu bar doesn't need to be repeated for every open document.

    Now, if the application is not really document oriented (not all applications are) or if it has features that don't require interaction with the document, that's what a dock menu is for. I don't know if you're familiar with dock menus, but nice authors make frequent commands accessible from a menu attached to the application's icon in the dock.

    Mail lets you check mail straight from the dock, Project Builder let's me make a new component or project from the dock, iTunes not only shows me what's playing, but it lets me pause, stop skip, or go back from the dock. Granted, those are all Apple applications, but Watson lets me check the weather, stocks, news, versiontracker, etc. all from the dock menu. Chimera - correction, Camino (kick ass browser!) lets me call up bookmarks from the dock.

    Not all applications are taking advantage of them, but, the support for it is there, and good programmers will use it those situations for a non-document based applications major functions.

    So, since dock menus reasonably address your need to have the menu bar always present and in the process removes the unnecessary repetition of menubars, I'd argue the single menubar approach is superior.

    Besides, with overlapping windows, most of your menubars will be obscured (at least somewhat) anyway, thereby forcing you to click on it to reveal the rest. The dock is always in the foreground, so dock menus are always accessible.

  8. A couple of comments by cbuskirk · · Score: 3, Interesting

    First I will steal a comment from a Macslash poster and say that each of the different categories should be weighted differently. The ease with which the average user can network two computers should carry more weight than out of the box chat capabilities.
    Second I am so absurdly tired of anyone who mentions anything to do with one button mice. If you are reading slashdot you are probably a computer geek. As a computer geek you more than likely know lots of stories about that idiot that can't use their computer. That is why there are one button mice! Most people are the idiot that can't use a computer. I don't think I have ever used an out of the box mouse from any PC manufacturer simply because I spend enough time using the computer that I really appreciate a mouse that is comfortable. Maybe Apple could be a little smarter and have a check box on the Apple Store site that allows a user to select their choice of mice.

    1. Re:A couple of comments by Anonymous Coward · · Score: 4, Interesting

      First off, I am *not* an average PC user.

      Since 1978, my fingers have been tickling keyboards of various shapes and sizes, QWERTY to Dvorak.

      I've used Macs off and on sinec 1985, Apples since a few years before.

      I have eight PCs in my home, (2) FreeBSD boxes, (1) Linux box, (1) Toshiba Laptop (Win2k), (1) Sun UltraSparc 10, (1) TiBook, (1) iMac, (1) Dual G4 Power Mac.

      As of today, my *NIX boxes are all headless .. sans one ..., no mouse, no keyboard (serial console access) and all access is via either my iMac or PowerMac ... with Apple's included one-button-mouse.

      Even navigating X-Windows, the 1 button mouse is NO BIG DEAL. In fact, it's so intuitive that I catch myself alt+clicking and windows+clicking when I'm at work on my Win2k Desktop there.

      The one-button mouse is more ergonomic, comfortable, and efficient that all this hullabaloo about multiple button mice is older then last week's dishwaster (and needs to be thrown out with it just as well.)

      And for the record, before the workstations were headless, they were connected with a standard AT-101 keyboard + Logitech 5 button trackball.

      Now all my servers are quitely running from my garage, and no matter where I'm at, whether it be the Living Room (iMac), Office (PowerMac), or back patio (TiBook) I have ready access to anything.

      Maybe when you've been typing and using a mouse for 20 years and have carpal tunnel in both of your wrists you'll appreciate the value of ergonomics some day.

  9. Some errors by drsmithy · · Score: 3, Interesting
    "Login":

    This is because Windows has been historically extremely vulnerable to viruses that take over the boot sequence and steal your login.

    This is not true at all. Windows is no more vulnerable to viruses that take over the boot sequence to any other OS and login and/or password hijacking programs have never been common on Windows. The Ctrl+Alt+Del for login has been in NT from the start (ca. 1993) and is simply part of the secure login facilities that NT was *designed* with.

    "General Interface"

    XP routinely fails to notify the user if the system is busy. It doesn't give ANY feedback when launching Internet Explorer.

    I've not seen a system for some time where IE startup wasn't so fast that feedback is required - but that's not the point. XP does give feedback - when the system is processing in the background, the cursor changes from an arrow to an arrow+hourglass icon. This includes (or should) the time while programs are loading and not displaying anything to screen. Unfortunately I don't have an XP box handy to test this with right now, but it certainly happens with Win2k and was also present in Win95.

    Something else that isn't commented on is how often applications block (the beachball), particularly the Finder. It happens *way* too much and on tasks that really should be quick or multithreaded.

    Whenever a window accidentally gets moved completely off the screen, the Size and Move keyboard commands can be invoked, and the window can be moved back onto the screen via the keyboard

    I can't see how a window could be "accidentally" moved completely off screen. I can see how it could be done programmatically by the application, or deliberately by the user - but not "accidentally".

    Dragging and dropping content from one app to another involves dragging the app down to the Task bar onto the button that corresponds to the window you want to drag into (even though the cursor switches to the Cant-Do-That icon), then finally drag the item back up the screen to the location you want to drop it. Not impossible, but not too practical either.

    Cumbersome it may be, but it is infinitely better than the complete lack of equivalent functionality in OS X.

    Corners are better used: the Start Menu is always placed in a corner, which makes it a very easy target.

    This is only true if the taskbar hasn't been made larger than the default. If it is, the Start button moves out of the corner (what it should do is expand to fill the entire space).

    Dragging test between windows is something that it is up to the application to implement on both OSes. Notepad is not a good example to use because it isn't really an app, it's just a text-control widget wrapped in a window.

    "Drag & Drop"

    More than one PC user has mentioned that they prefer cut and paste. And on Windows XP I prefer cut and paste too, not because cut and paste is an inherently superior method, but rather because XP's poor support for drag and drop has trained me avoid it altogether. But on Mac OS X?which has more thorough support for drag and drop?I use each method interchangeably depending on what best suits the current situation.

    I prefer to use Cut & Paste for file management as well, and I'd prefer it in OS X to drag & drop. Unfortunately, the Cut & Paste functionality in OS X for this purpose is inadequate.

    "Navigating the file system".

    IMHO OS X loses out here completely because it doesn't feature the classic directory tree + file list style of GUI file management which I find to be the easiest and most efficient to use (when partnered with good keyboard shortcuts).

    "Dock vs Taskbar"

    One of the Dock's most impressive features is it's advanced real time application feedback.

    Visually impressive it may be - however, functionally it's fairly pointless. Apart from the *massive* overhead involved (a busy minimised terminal window will drag the entire GUI to a crawl) the utility is fairly limited - for preview icons to be useful, they have to be huge, chewing up yet more valuable screen real estate in a GUI feature that already wastes more than it should.

    "Keyboard application switching".

    He forgot that Cmd+` will cycle between the windows of the foreground app. Also, a big weakness in OS X's keyboard switching IMHO is an inability to quickly & easily move to an arbitrary window (particularly without having all the app's other windows obscure the rest of the screen).

    "Keyboard Shortcuts".

    Some of the keyboard shortcuts are just flat out wrong. The standard shortcut for "new file" on Windows is Ctrl+N. Win+E is a shortcut for launching explorer. Although he rightfully picks up that there is *still* no shortcut key for creating a new folder in Explorer. The shortcut for "opening a file" in Explorer is Enter. Using Alt+F,O is the long way to do it. He also does not say anything about a shortcut that is seriously lacking in OS X - one to quickly go straight to the Desktop. This area is a big win for Windows IMHO, since it's possible to do anything from the keyboard in Windows quickly and easily with no extra configuration necessary.

    It's also troubling that XP relies on the Windows key for system shortcuts, since not all keyboards have a Windows key (my IBM ThinkPad lacks a Windows key).

    No ! This is exactly what it *should* do. All the keyboard shortcuts should be Win+ or have a programmable modifier key. Using the control key for shortcuts was a Really Bad Idea.

    "Networking".

    The network browser in OS X is really bad - although not as bad as the nightmare that was Chooser. You can't access anything on a remote machine without mounting it's share, searching for or connecting to specific machines is clumsy and opening up the "Connect to Server" dialog BLOCKS THE WHOLE FINDER.

    Connecting to remote machines in Windows is vastly superior. You can navigate directly to machines, the shares they have and manipulate things in those shares - even launch programs - all without having to map or mount the share.

    "Power User".

    I'm not quite sure why "screen capture" is in this section - I don't think I've ever wanted to take a screen capture in my life, let alone cared about how flexible the builtin tools to do it are.

    "Booting from alternate drives". This is a hardware issue and has _nothing_ to do with Windows or OS X. Just as there are PCs that require fidding in the BIOS to boot from anything except the first hard disk, there are also machine that let you hit a key on bootup to get a nice little menu of all the bootable devices the system knows about. It really doesn't belong in this comparison.

    "Misc"

    XP Home Edition doesn't support multi-processors.

    That's because the audience it's targetted at won't be running machines with multiple CPUs.

    You can only use your numeric keypad in XP when num lock is turned on, even with full size keyboards.

    This has already been commented on, but it bears repeating. This is *precisely* how the system should operate. Not only that, but most PCs default to having the Num Lock on at boot - and if that isn't enough, Windows will remember the state the Num Lock key was in the last time you logged out.

    Apart from these errors, which seem mostly to do with a lack of experience with Windows, lack of knowledge about it's history, and/or simple personal preferences, the site seems ok.

    1. Re:Some errors by afantee · · Score: 4, Informative

      >> IMHO OS X loses out here completely because it doesn't feature the classic directory tree + file list style of GUI file management which I find to be the easiest and most efficient to use (when partnered with good keyboard shortcuts).

      What the fuck are you talking about? The OS X Finder does have "the classic directory tree + file list" called list view, and is miles ahead of Windows Explorer in at least 6 ways:

      (1) Column View is the best feature for file browsing not available on any other OS.

      (2) Spring-loaded folder makes it possible to drag and drop files to any depth without opening lots of windows.

      (3) Finder toolbar is much more configurable than Windows Explorer.

      (4) Music, graphics and movies can be played or viewed right in the Finder preview pane without starting applications.

      (5) One-click search by content, size, type, date, extension, or visibility.

      (6) Automation with AppleScript.

      Oh, if that's not powerful enough, there is always the Unix terminal to play with: csh, tcsh, bash, Perl, Python, Ruby and lots other tools all preloaded. Windows is not even remotely close.

      >> Connecting to remote machines in Windows is vastly superior. You can navigate directly to machines, the shares they have and manipulate things in those shares - even launch programs - all without having to map or mount the share.

      Do you know anything about networking at all? Windows only understand Windows or SMB, while OS X can handle Windows as well as NFS, UFS, HFS+ and SMB. What do you mean by "without having to map or mount the share"? Surely you still have to login to a remote machine before accessing it. And OS X comes with Rendezvous ZeroConf so that devices (not just computers) can discover each other.

    2. Re:Some errors by Kplusplus · · Score: 2, Informative

      I barely made it through this post, but here it goes.

      File Management:
      You can recreate this file list + tree thing is easy. Set to list view then turn off all the columns. Icon View can be ordered as more than Name, it includes date modified, date created, size and kind. As a matter of fact all the 6 views in windows can be recreated by using the View Options control panel (Cmd-J). Also Column View supports spring lodaed folders so the easily movings things point is moot. Also copy and paste is supported for copying files as was covered in the section on drag and drop. It was mentioned as a blurb.

      File Systems
      NFS is transparent from any other fs. I had several user's accounts NFS mounted and none of them ever had a problem. Though i do agree that SMB and FTP is flaky, the rest is simply untrue.


      The rest I just couldn't care less about.

      --
      -"I'm one of those Mac people that will break a bottle on the bar and hold it to your throat for bad-mouthing my system"
  10. Actually... by FredFnord · · Score: 5, Informative

    ...I'm running my web server, mail server, FTP server, QuickTime Streaming Server, internet sharing, file sharing, and name server on MacOS X 10.2 on a beige G3. When I had my main machine out at a client's site, I used the beige G3 for all of my daily use for a couple of weeks. It worked fine.

    I will admit that I've upgraded the memory to 320 megs or so. But even on a 300 mhz G3, running with a Rage Pro chip, things work surprisingly smoothly and well. I wouldn't do all my development on that machine if I had a choice, but for day-to-day usage it's perfectly fine.

    -fred

    --
    Sign #11 of Slashdot overdose: You see the phrase 'moderate Republican' and you wonder if that would be a +1 or a -1.
  11. Dock feedback far from pointless by Anonymous Coward · · Score: 3, Interesting
    One of the Dock's most impressive features is it's advanced real time application feedback.

    Visually impressive it may be - however, functionally it's fairly pointless. Apart from the *massive* overhead involved (a busy minimised terminal window will drag the entire GUI to a crawl) the utility is fairly limited - for preview icons to be useful, they have to be huge, chewing up yet more valuable screen real estate in a GUI feature that already wastes more than it should.


    I could take you to task on many of your points, but this one is grossly inaccurate, and something has to be said.

    I don't know how you could use OS X for more than a week and still think dock feedback is mostly pointless. Let's take the prime example: Mail. Even if my Mail icon is tiny, it still tells me if I have unread messages by displaying that tiny red star on Mail's "stamp" icon. If I have magnification turned on, I can see how many unread messages have just come in. If you can't see how that is useful, then there's no reason to waste precious CPU cycles explaining it. :-)

    Besides Mail, there are dozens of other apps that provide Dock feedback (CPU Monitor comes to mind), save me keystrokes and reduce the app's interference with my workflow to a single glance rather than a click, a glance, and another click to go back to where I was. Print Center shows me when my print jobs are going, and when they're finished, or if they've encountered any errors. It even shows me how many pages still have to print! And I don't have to open a single window to get that information. There are dozens and dozens more examples where these came from. And none of these examples require the icons to be huge. You can get one level of usefulness with the dock minimized, and another level if you choose to magnify it, which can be done with a simple flick of the wrist.

    How can you possibly support that the dock feedback feature isn't useful with all that evidence?
    1. Re:Dock feedback far from pointless by drsmithy · · Score: 2, Interesting
      How can you possibly support that the dock feedback feature isn't useful with all that evidence?

      Sorry, I should have been more specific. I meant the type of eye-candy feedback I gave as an example (eg: minimised terminals updating, DVDs & Quicktimes playing minimised, synamically updating document thumbnails, etc) and not the simple things like the number of unread messages in the user's inbox which are quite useful and informative whilst having little impact on system performance. It might be better in 3 - 5 years, when Mac hardware has gotten fast enough (or OS X has been optimised enough) such that a single rapidly updating terminal in the Dock grinds the whole system to a halt - but right now these things need to be an option.

  12. Re:sorry, try again by gerardrj · · Score: 2, Informative

    Perhaps you should fire up Sherlock and head over to Ebay. I've seen several Beige G3s sell there for under $100 in the past weeks. $150 will get you a nice little box capable of running a file/web/mail server system or even playing some less demanding 3D games (with an ATI Radeon 7000 PCI installed of course).

    There's a retail site near me that sells used G3 boxes pretty cheap, like $200 for a 333Mhz mini tower.

    --
    Article X: The powers not delegated... by the Constitution...are reserved...to the people
  13. Re:OS X = X11 by pi+radians · · Score: 2, Insightful

    Don't forget that OS X can also run XP apps.

    --

    sin(6cos(r)+5A)
  14. Re:Multiple mouse buttons by Ponty · · Score: 3, Funny

    The Amiga was perfect and amazing in 1947. Shut up you evil heathen. You don't understand the future when you see it. I'm going to go and buy some crazy computer called an "Amiga" because it has a checkerboard sphere glued to the front. We will win forever!