Slashdot Mirror


A Better Finder?

Build6 writes "Ars Technica opens today with another one of their deeply-thought-out articles relating to MacOS X issues, pointing out another thing which the old MacOS had and the current one doesn't."

462 comments

  1. Evil bit support by Anonymous Coward · · Score: 3, Funny

    pointing out another thing which the old MacOS had and the current one doesn't.

    Evil bit support? Support for the One BSD to Rule them All (even though they are all dying)? The Foreman iGrill? Volkswagens? Red and blue lasers? Sharks?

    1. Re:Evil bit support by Build6 · · Score: 5, Informative

      I guess I shoulda made this more clear in my initial submission.

      I think the primary thing that the old MacOS had that the current one doesn't, is good handling of file metadata. I think most people who come from a Windows/x86 background don't really understand how magical it is to have a file system that, for example, can allow for different files of essentially the same "file type" yet be launched by different apps (file "creator" and file "type" tags exist).

      This was discussed in Ars Technica quite a while back, as well:

      http://arstechnica.com/reviews/01q3/metadata/met ad ata-1.html

      And, this "other thing" I'm talking about is a (properly) spatial finder.

    2. Re:Evil bit support by DeadSea · · Score: 4, Interesting
      When I first tried a Mac it frustrated me that I didn't have the type of control that I was used to on Windows. I couldn't make a certain program open a file by renaming it. The icon of a file would change when it was saved by a different program. Because I was used to working with text documents that could be opened by a variety of programs, this really confused me.

      Eventually I learned about the different meta-data types and how to edit them. If anything, I found that the Mac had several power user features too well hidden for me.

    3. Re:Evil bit support by sjonke · · Score: 2, Insightful

      I think most people who come from a Windows/x86 background don't really understand how magical it is to have a file system that, for example, can allow for different files of essentially the same "file type" yet be launched by different apps (file "creator" and file "type" tags exist)

      So magical, indeed, that it would, not infrequently get corrupted and lose track of what was what and you'd end up with documents of certain types looking like generic, unknown documents that in some cases couldn't be opened by anything except BBEdit. The especially cool thing is that then you got to use an equally magical "rebuild the desktop" startup key combination that, again not infrequently, didn't do any good. I had documents that stayed generic up until I switched to OS X. Then it was easy to fix the problem and get it to open with the right application using the Get Info window on the file in question.

      Moreover the argument was bogus to start with. In OS X you can set any file to be opened by any application regardless of what the default application is for that file type. I can set a particular .jpg to open in Preview even if the default is still GraphicConverter. I can also easily change the default application as well. This is essentially the same thing, except that it's reliable and easier to use.

      To add to the OS X crunchiness, I have graphic files (JPG, GIF, PS, etc) open in Gimp by using an AppleScript application/droplet as a conduit of sorts to Gimp under X11. I just set my script as the default app for those file types. Nifty.

      Yours miserably (like that arstechnica guy),

      Steve

      --
      --- What?
    4. Re:Evil bit support by Cyno · · Score: 1

      Well, with KDE right now I can right click on any file and tell it to open with any application on the system.

      I guess you can do this with Win2k, too, but I prefer KDE.

      For example I wrote a script to automaticly loopback mount my cdrom isos into a .loop.pid directory and open a konqueror window. As soon as I exit the window the loopback filesystem is unmounted. Then I right click and I have an option to burn the iso onto a CD. That was another script I wrote that automaticly burns an entire directory of ogg or mp3 files onto an audio CD as well.

      I think it might be more useful to have these type of scripts integrated into the system instead of writing more ways to automate the openning of an application or file.

      It might be nice to have that metadata but things like locate should be run at a nice level 19 and those types of extensions to a filesystems are not required to have a usable workstation. They might make it nicer for some people but for people like me they might also just get in the way.

      I've used OS9 and its not entirely bad, but I'd never want that running on my workstation.

    5. Re:Evil bit support by kalidasa · · Score: 1

      Well, with KDE right now I can right click on any file and tell it to open with any application on the system. I guess you can do this with Win2k, too, but I prefer KDE.

      And you can do it with OS X. Ctrl-Click > Open With > Application | Other ... . If you have bought yourself a scroll mouse (like my Macally mouse) you can use the right mouse button to Ctrl-click, just like Win2K/XP.

    6. Re:Evil bit support by rifter · · Score: 1

      You know, if your desktop database is corrupt in Classic Mac OS, you can simply delete it. Then when you "rebuild your desktop" you get a whole new database, no corrupt weirdness. That is one of the cool things I miss about the old Mac OS. There were any number of things which could be simply trashed which magically rebuilt themselves, like preferences and desktop db.

      Now the major problem of course is that the preferences and desktop database got corrupted in the first place, and rather too frequently for some people. I think the idea was nice enough, it is just that some details in the implementation might have stood some reorganizing. Perhaps a more robust desktop db (imagine MySQL as your desktop db!) or something. Then the whole situation is rather different.

    7. Re:Evil bit support by Trolling4Dollars · · Score: 1

      Why do I think the "evil bit" thing is going to be the next "In Soviet Russia" for a lot of people? (I happen to like a good "In Soviet Russia" joke BTW...

    8. Re:Evil bit support by b17bmbr · · Score: 1

      a file system that, for example, can allow for different files of essentially the same "file type" yet be launched by different apps

      this was one of the macs biggest problems. what if i sent you an html file done in dreamweaver and you don't have it. you'd have to figure out what type of doc it is, and what app to use. PITA. talk about file incompatibility. why do yo think apple dropped this "feature"?

      --
      My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
    9. Re:Evil bit support by rifter · · Score: 0

      I should also point out that the problem with the extension approach is that all files of a given type are always opened by one application. That is not necessarily what the user wants to do. What if you want to look at the jpgs in your html folder in Mozilla, but look at the "portraits of models" in a slideshow app? Apparently some people were editing type and creator code info in different areas of their disk so that different groups of files of the same type woudl be opened in a different application. That is something you cannot do with the paradigm where the opening application is decided by the extension alone.

      Granted, there are hacks. For instance in Windows I have frequently done something like named Unix text files with a .out extension, which I associate with wordpad, and windows text files with .txt so they will open in notepad. Then if there is some file I know I want to open in wordpad regardless of the real type I make it .out (or use "open with," and by the way isn't it nice that Macs can use usb mice with more than 0 buttons so that you can right-click on things to bring up context windows like even Windows can do?).
      Of course all of these are things we should consider as we discuss the future of Linux. I am one of those foolish dreamers who sees Linux as the future of computing. But in order to make it so, we must learn from others who have gone through the UI battle.

      Also the neat thing about Linux is we aren't tied to one interface necvessarily (though this presents other problems to some degree) so I can use my fvwm2, which serves my purposes best, and my mom can deal with Gnome or KDE since they remind her of Windows. So if someone implemented an interface that includes a Finder with a desktop db, you don't have to use it if you don't like it. Much like I am never going to use RPM again if I can help it at all. Talk about non-robust databases and rebuild functions that don't really work! I'd like to see you delete your RPM database and just rebuild it from nothing!

    10. Re:Evil bit support by sjonke · · Score: 1

      FYI, I am a Mac user since the days of the Mac SE. In its day, even with the problems, the OS = 9 desktop database was a great thing - it was indeed a good concept. OS X's approach is, however, better IMHO.

      FYI, I did try trashing the desktop database, several times. It didn't work and in some ways it made matters worse. True that in the past it had worked for me, but for whatever reason it stopped working and I was never able to resolve it (backing up my files, erasing the disk, reinstalling OS, restoring files, etc probably would have fixed it, but that's an agonizing process, especially if the only thing you had to backup to was 100MB zip disk!

      --
      --- What?
    11. Re:Evil bit support by Anonymous Coward · · Score: 0

      Did u even read the post you were replying to? He JUST SAID you can change the app that opens any file in the Get Info window, regardless of the default for that filename's ext. DUH! MORON! IDIOT! Go die now please.

      Sorry, stupid people just piss me off.

    12. Re:Evil bit support by Anonymous Coward · · Score: 0

      That's a weak argument. What if you got the same file and had no idea what app is was created in, wanted to be opened by?

      Duh! You would use your own default app for that file type or you would determine its file type and what apps could open it?

      Same situation, but in the Mac example--if you happen to have the "creator" app it would launch that application. But in no way does this create a unique or Mac-only situation.

    13. Re:Evil bit support by Raffaello · · Score: 1

      " should also point out that the problem with the extension approach is that all files of a given type are always opened by one application. That is not necessarily what the user wants to do."

      This is not true under Mac OS X, which does use file extension to determine which application(s) may open a file.

      Under Mac OS X the user can set the application to open on a per file basis, and can set a default as well. You can have 10 different jpegs each open with a different application when you double click them.

    14. Re:Evil bit support by Raffaello · · Score: 1

      Yes, but under KDE, does KDE *remember* which application you set to edit that particular file next time you double click it?

      Under Mac OS X, it does.

    15. Re:Evil bit support by Anonymous Coward · · Score: 0

      In Soviet Russia, the "In Soviet Russia" joke likes YOU!

    16. Re:Evil bit support by Anonymous Coward · · Score: 0

      you mean, eeeeeeeeevil bit support

    17. Re:Evil bit support by osu-neko · · Score: 1
      Because they switched operating systems (from MacOS to NextStep), and their new OS never had that feature. It wasn't dropped, just never added.

      The problem you talk about is easily solvable by simply having a default app for filetypes when you don't have the creator. Or give a list of existing apps that can handle that kind of app when you double click on this. There was an extension for System 7 that did this IIRC...

      --
      "Convictions are more dangerous enemies of truth than lies."
    18. Re:Evil bit support by Cyno · · Score: 1

      Yes, but under KDE it is completely customizable. You can create a list of applications to use for each type of file and launch them from the right-click menu. There are also konqueror plugins for many file types so you might not even need to launch an application if that's your preference.

    19. Re:Evil bit support by Anonymous Coward · · Score: 0

      We're not talking about file types; we're talking about individual files. Mac OS (X and previous versions) can remember creator types for individual files, regardless of the extension. (It can also associate file types by the extension, but that's not the point of this discourse.)

    20. Re:Evil bit support by randyest · · Score: 1

      You seem to be ignoring (or ignorant of) the simple right-click + "open with" option (in windows, at least, dunno about mac). Xp even remembers the apps with which you've opened a file type, and adds them to the "open with" list.

      So, you have a .txt file, and .txt is associated with notepad. Right click, select open with, and choose wordpad. Next time you right click+open with a .txt file, you'll see notepad, wordpad, and "choose program".

      --
      everything in moderation
    21. Re:Evil bit support by bursch-X · · Score: 1

      Yes and no. If there is no type and/or creator set for the file, the Finder uses the extension to recognize the file type.

      Also with bundles (which are folders that act as if they were "flat" files) extensions can be the determining factor whether they are even recognized as such (otherwise it's just a folder).

      --
      There are two rules for success:
      1. Never tell everything you know.
    22. Re:Evil bit support by rifter · · Score: 1

      Yes I did. Did you?

      I was pointing out that whereas in Windows and the current MacOS you can set what application opens a kind of file by extension, in the old MacOS you could set by individual files which application opens a file. So I can open one jpg in one application, and other jpgs in another application, all by default. Stupid people annoy me, too. :P

    23. Re:Evil bit support by rifter · · Score: 1

      I know all about "open with..." I must have been unclear, and for someone who has never used a Mac this is kind of an odd concept, anyhow (for that matter it is for most Mac Users) but I was saying that you can open files with more than one application. At least one other person had the same reaction to my post, so I suppose anything is possible.

      The file associations in Windows let you associate one file with one extension. But on the Macintosh you could set the creator code to other programs and therafter that file got opened by a different program. So I could have a folder full of jpgs that, when double-clicked, open in Photoshop, and another folder, also full of jpgs, which open in Gimp when double-clicked. This is not possible under Windows unless you want to right-click, and in many cases you hold shift and then right click because Microsoft hides the "open with" option under certain circumstances.

      Besides, it takes ages for that stupid application menu to open on a lot of machines, and it is kind of silly when I *know* what kind of application I want to open the files with.

      FWIW, I never used this functionality, but then I usually had one favorite program to work with a given type of file. I also tend to use File -> Open more often than not. Even in vi I tend to use :e about as often as, if not more often than, I use vi $MYFILE . But that is because I was not used to having it around. A lot of people got used to it, and bitched mightily when they thought they could not do it. (Someone in this thread has said that the current Mac OS X can deal with type and creator codes, but I need to confirm that, and if it does, it is not simple to find, though I rarely even deal with Macs anymore except when helping my girlfriend with her new iBook).

      Anyway, I think it would be neat, and anything which empowers the user is good, especially if it makes things easier to do.

    24. Re:Evil bit support by randyest · · Score: 1

      Ah, I get your point. And, that is pretty cool. Assuming, of course, that you can set it on a folder level, and not necessarily on a per-file basis (which I think would have too much overhead associated with it, and might be annoying when I no longer want to use gimp for x.jpg, but forgot to change the metadata or whatever to set it back to a simple viewer).

      You're right, the full "application list" browser can take a long time to populate, even on a fairly fast box. But, as I mentioned, under XP, the "open with" menu gets a very fast submenu with a list of programs you've ever used to open that file type automatically, and it's instant, so you don't need to wait for the full application list browser.

      Not to be a MS fanboy (a sure karma killer, especially in a mac thread), but XP puts the open with menu on right click always (a good thing), and you can easily add/remove apps from that menu. I think all previous MS OSes required the shift or control right click to get the open with menu, which is annoying.

      I'm not sure I'd use the folder-based association thing, since I rarely group things by app I want to use them. That changes depending on what I'm doing, so I want an easy, non-permanent, per-file based, quick way to choose what app to open any file with. Having a quick, short list of apps I've used for that file type seems to be the best way to do this IMHO. But, if the metadata/creator code thing could be changed as quickly, or nearly as quickly, it would be sufficient.

      I love this sort of discussion, BTW, and I think the major weakness of GUI's is that they're often not tweaked or refined enough to be as efficient (and consistent) as they can be. They seem to be either dumbed-down for the lowest-common-denominator, or hyper-complex for the power-user and requiring lots of setup or learning to be efficient.

      The happy medium would be (and has yet to surface, AFAIK) a GUI that's trivially easy to use by default, but massively configurable a la gnome/KDE/CDE. I think mac OS is moving away from this, and MS OS is moving closer to it. This is a bad thing -- someone should merge the best from all OS GUIs and make a really good one.

      On older macs I've used, I found the GUI very efficient (but always lamented the single mouse button limitation -- seemes like it would have been 2x better with another button, and 2.5x better with a 3rd button. No scroller is annoying too). I think these things are available now (I've seen 2-button, 3-button, and scroller mac mice, but I'm not sure how well they integrate into the OS or apps, or how configurable they are). But OS X seems to be a bit of a regression -- it's prettier, but less efficient to me. And not for the same reasons that the spatial finder guy lists. It simply seems less consistent than the pre-OS X GUIs. And slower. A lot slower. I want BeOS responsiveness, even if it is an illusion, or sucks my RAM dry on boot (RAM's cheap).

      Now, XP is a big improvement. Pre-XP win OSs always had so many annoyances, and the 3 buttons + scroller could not make up for them (like having to hold ctrl or shift while clicking to get certain options in the context/right-click menu -- that's just dumb, to me).

      Of course, most of my real work is done via CLI (solaris at work and home, and sometimes linux). So, OS X with it's UNIX underbelly is very attractive. But, the GUI seems slow and inefficient compared to older mac OSes, and even to XP (or CDE, or gnome, . . . ). Sometimes I want a GUI for casual computing. It has to be fast, easy , predictable, consistent, AND configurable.

      --
      everything in moderation
    25. Re:Evil bit support by Pope · · Score: 1

      The biggest going generic problem was with Quark, and that could easily be remidied with Norton Disk Doctor. One of the menus had an option to "Add file to desktop" which would take care of that.

      --
      It doesn't mean much now, it's built for the future.
    26. Re:Evil bit support by bruddahmax · · Score: 1

      i think the point here is that the parent post explained that in Mac OS X not only can one set a default app for any given .xxx filename extension, but for individual files (or groups of files) one can use the "Get Info" command in the finder to change the application that opens the files to something other than the default app. so some .jpg files open in GraphicConverter, but these that i've highlighted and changed the program for will open in Preview (and their icon will change to match the associated program).

      so Mac OS X appears to have combined the best bits of Windows (automatic assignment of files to a default app based on filename extension) and Mac OS 9.x (opening of files based on hidden creator metadata) when it comes to file assignments. it really is quite flexible and the Ars Technical article makes it seem like the most archaic file system ever designed. oh well. he means well. i think.

    27. Re:Evil bit support by rifter · · Score: 1

      Ah, I get your point. And, that is pretty cool. Assuming, of course, that you can set it on a folder level, and not necessarily on a per-file basis (which I think would have too much overhead associated with it, and might be annoying when I no longer want to use gimp for x.jpg, but forgot to change the metadata or whatever to set it back to a simple viewer).

      Unfortunately, this was controlled on a per file basis. I think there might have been programs that would batch-process files, but the only one I ever used to mess with type and creator codes was resedit, which did other things, too...

      I love this sort of discussion, BTW, and I think the major weakness of GUI's is that they're often not tweaked or refined enough to be as efficient (and consistent) as they can be. They seem to be either dumbed-down for the lowest-common-denominator, or hyper-complex for the power-user and requiring lots of setup or learning to be efficient.

      I agree and this is a problem with computing in general. Of course in the GUI interface problems are easier to see because of the nature of the interface. Hopefully we will learn. I think the idea of having levels ("basic" and "advanced" with "basic" as default) is a good way to go and has been tried in MacOS, Windows to some extent, and Mozilla to name a few... But the idea coudl be expanded, maybe even a "newbie bit" that could be set globally for all apps run from a user or that could be set by default and unset by the user.

      On older macs I've used, I found the GUI very efficient (but always lamented the single mouse button limitation -- seemes like it would have been 2x better with another button, and 2.5x better with a 3rd button. No scroller is annoying too). I think these things are available now (I've seen 2-button, 3-button, and scroller mac mice, but I'm not sure how well they integrate into the OS or apps, or how configurable they are). But OS X seems to be a bit of a regression -- it's prettier, but less efficient to me. And not for the same reasons that the spatial finder guy lists. It simply seems less consistent than the pre-OS X GUIs. And slower. A lot slower. I want BeOS responsiveness, even if it is an illusion, or sucks my RAM dry on boot (RAM's cheap).

      I agree with you on the mouse problem (unfortunately for mac users, Steve Jobs does not agree). But it is entirely possible to have mice with many buttons and have them work in MacOS, Windows, and even Linux. I have seen mice that had about 5-7 buttons being used on Macs, and they came with driver software that let you configure the buttons. One of the first things I did after having to muck with my girlfriend's iBook awhile (helping her get it set up right) was to take my favorite (of all time) Logitech USB trackball and install the drivers on her iBook, configureing the right button for ctrl-click and the middle button for Command-V so that middle button pastes and right click brings up a context menu.

      In an aside, I am still pissed off at Logitech for discontinuing this kick-butt mouse. It is hard for me to find a good mouse, and this one was the best. The one I am talking about is the marble trackball with wheel, and the current version has lost the space provided by the third button and is therefore far too small for me to use comfortably. The old one was spaced out enough I could just drop my hand on it and generally expect the buttons to be near the right fingers, whereas the new one requires far more precision. Oh well, back to the used computer parts stores for me :(.

  2. I don't agree with the article by MarkWatson · · Score: 5, Interesting
    It is easy to criticize. I use OS X about 80% of the time, Linux/KDE about 15%, and Windows 2000 about 5%. OS X, in my opinion, gives the best desktop experience.

    Any desktop uses a spacial metaphor for data - however, for me, the desktop is just a holding area - short term memory, if you will.

    I do like the idea of other means of filtering: LifeStreams seems like a good idea: being able to filter based on time and document type (for example).

    Anyway, it is a free world - I will stick with OS X.

    -Mark

    1. Re:I don't agree with the article by Build6 · · Score: 2, Interesting

      Well I'm not saying I am going to "abandon OS X" (and I don't think the article writer is?) but the point is... it could be so much better, you know? (at least for me) OS X would be *perfect* if on top of the new UNIX innards there was a "classic" theme where OS X acted exactly like the old macOS. I'm not saying I'll never switch to the existing OS X/Aqua UI, but I certainly miss the old MacOS.

      yes, I dual-boot my Macs and I still use OS9. Am looking warily at the new generation of machines that won't boot OS9, although apparently there are some indications that special ROM files are available to Apple service providers that would allow OS9 bootability even on those not "officially" OS9 bootable.

    2. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      " LifeStreams seems like a good idea: being able to filter based on time and document type (for example)." .. This is new? WIndows (that OS you use 5% of the time - obviously) has had this since like windows 95. Start , Search "for files". Could it be easier?

    3. Re:I don't agree with the article by feldsteins · · Score: 4, Insightful

      Yeah I remember lifestreams and I agree it's a fantastic idea. I'd love to see it developed further!

      I also appreciate (sincerely!) the criticisms of OS X one finds at Ars. They are consistently thorough and honest. Still, sometimes it seems like OS X is held to a far higher standard with regard to UI than other products. I mean, correct me if I'm wrong, but I don't think Linux (any flavor) or Windows (any flavor) has recieved nearly the same amount of scrutiny and criticism with regard to UI. Why is that? Is it simply because Apple brags about it so much? Is it a recognition that Apple does it best (usually) and therefore it is fair that they should be evaluated based on that claim? I suspect that this is the reason.

      I fear, however, that it gives the casual Windows or Linux-using reader the wrong impression - the impression that OS X UI stinks. It doesn't. It's a relatively new UI and needs refinement, but as I said, I believe the level of criticism leveled at it is mostly due to the recognized fact that Apple does it better than most others.

      --
      You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
    4. Re:I don't agree with the article by bay43270 · · Score: 1

      I think even the author would agree with you that Mac OSX offers the best desktop experience. That's why we need to criticize Mac OSX... because it's the leader. Criticizing Windows, KDE and others is easy (and pointless): "make your OS more like Mac OSX and call me when your there".

    5. Re:I don't agree with the article by IamTheRealMike · · Score: 4, Insightful
      Still, sometimes it seems like OS X is held to a far higher standard with regard to UI than other products. I mean, correct me if I'm wrong, but I don't think Linux (any flavor) or Windows (any flavor) has recieved nearly the same amount of scrutiny and criticism with regard to UI.

      I can't speak for Windows but Linux does for sure, in the past 12 months I must have seen more "usability reviews" of various parts of the Linux desktop than I've had hot meals. Most of them are worthless, but in general the noise over usability has had an effect, go see the effort and elbow grease being put into GNOME (especially) and KDE now for instance. The Nautilus team have been hard at work doing what is basically just polish and optimization (just as well, it really needed it!) lately for instance.

      Why is that? Is it simply because Apple brags about it so much?

      Well, when you look at the Mac value proposition, basically it boils down to their user interface. They can't sell on price or speed or number of apps, nor do they have the "nobody got fired for buying Foo" mentality on their side. Their no 1 selling point is that Macs are supposedly easier and more efficient to work with.

      As such, people talk about that, it's the one thing that makes Apple unique. Personally, although they still do better than most companies, I think their reputation for UI expertise has taken a bit of a battering with the Jobsian era - go read some reviews of MacOS X from former OS 9 users, who point out some of the more laughable usability errors in OS X. These days, I think they're trading a lot on reputation, people think "Macs are easy!" and because ease of use is so subjective, they rarely get challenged on that point. That's what makes articles like this one so fascinating.

    6. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      The only thing that justifies the outrageous price/performance of Apple computers is their OS and it's famed "usability". It needs to be held to a very high standard commensurate with that.

    7. Re:I don't agree with the article by feldsteins · · Score: 1

      I concur with just about eveything you say. I would also add that Apple's "value proposition" is a tad wider than simply "better UI." I think it's got a lot to do with the integrated experience they are always pimping. You know, like end-to-end stuff like iPhoto. Insert digicam here, get database archives, editing, prints, books, etc, out the other end. No worries about somene else's software being required, either. They sell, to use a vendors term, "solutions." Solutions to problems like "I have a digital camera but.." Or "I have a digital video camera, now how to I get this stuff I shot onto on grandma's TV?"

      Bah, you know what I mean. But it's a lot more than just "we put interface buttons in sensible places."

      --
      You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
    8. Re:I don't agree with the article by feldsteins · · Score: 1

      I think you're overstating the "outrageous" nature of a Macintosh's value. But in principle I agree with you. As I said elsewhere above, however, I also add:

      I buy that totally. I do wish, however, that the steady stream of criticism from sources like Ars would clearly indicate that this is where it's coming from, rather than letting the reader suppose that it is meant as a comparative criticism against Windows' and/or Linux's UI.

      --
      You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
    9. Re:I don't agree with the article by timeOday · · Score: 1

      Me neither, find + grep, baby! None of this "spatial orientation" rubbish :)

    10. Re:I don't agree with the article by Nurgled · · Score: 2, Insightful

      I don't think Linux (any flavor) or Windows (any flavor) has recieved nearly the same amount of scrutiny and criticism with regard to UI. Why is that?

      I'd say that is because Mac users are a lot more opinionated about how their little world should be than most. There are lots of quirks in the Windows UI, but people just learn to deal with them and move on. Mac users write five-page articles.

    11. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      It is easy to criticize.

      It sure is, and you provide an excellent example.

      So I hope you're not suggesting that one should not criticize.

    12. Re:I don't agree with the article by rifter · · Score: 1

      I think the poster was talking about being able to see the result of a given query all the time, much like was available in the BeOS. In other words, I would not have to type a query every time I want to see all config files modified today. I would just click on that and get it. Windows has never had that.
      Here is a link Google gave me for an article on LifeStreams:
      http://www.acm.org/sigchi/chi96/proc eedings/videos /Fertig/etf.htm

    13. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      I think you're overstating the "outrageous" nature of a Macintosh's value.

      Are you kidding? For the price of one Mac, I can build two equivilent PCs running Linux.

    14. Re:I don't agree with the article by cpt+kangarooski · · Score: 1

      Meh. It was just that kind of dissatisfaction with the status quo that's led to pretty much every UI improvement. What's wrong with wanting things to be better?

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    15. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      It is a free world? Where do you live?

    16. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      Equivalent in what way?

      Equivalent in video editing capabilities? Nope.
      Equivalent in user interface? Nope.
      Equivalent in digital music management? Nope.
      Equivalent in choice of software? Nope.
      Equivalent in ease of hardware access (G4 tower)? Nope.
      Equivalent in battery life (laptops)? Nope.

      I could go on, but I'll spare you. Now of course many people don't care about those, and that's totally cool. Macs would be a waste of money for them. But your use of the word equivalent is overbroad and ridiculous. Equivalent for your needs perhaps. But that's it.

    17. Re:I don't agree with the article by CaptnMArk · · Score: 1

      I never used a Mac, but this guy is describing everything (and more) that made OS/2 WPS by far the best GUI for me.

      GNOME and KDE developers would do well to look at this article (and OS/2 too).

    18. Re:I don't agree with the article by Moofie · · Score: 1

      Replace "user interface" with "user experience", and you've got it.

      The user experience IS Apple's product. Period.

      --
      Why yes, I AM a rocket scientist!
    19. Re:I don't agree with the article by Eccles · · Score: 1

      I'm not much in agreement with the author either. As a developer, with multiple versions to deal with, I have a whole bunch of folders with the same name. The insistence of the Mac OS of not showing the path means that I have a hell of a time determining which particular copy of the Source folder a given finder window refers to.

      By the way, who decided that the way to sort one's documents is by type? Isn't a picture a document? If I have both pictures and vid clips from my trip to Vegas, shouldn't those be grouped together? This proliferation of specializations of the Documents folders makes no sense to me. (On Mac or on Windows.)

      --
      Ooh, a sarcasm detector. Oh, that's a real useful invention.
    20. Re:I don't agree with the article by code_nerd · · Score: 1

      Well, it really depends on what you want from your OS and your system. Personally, I have no trouble with digital music management on my Linux box, I don't do editing, I find that Linux has plenty of software fo the sort I need, and so on. Plus it is free, and the system I can run it on does not require that I take out a loan to do so. So, from my perspective, I could indeed get two equivalent (for me) systems for the price of a single Mac. Which is why I don't use a Mac. YMMV, and I am sure that it does.

    21. Re:I don't agree with the article by SewersOfRivendell · · Score: 5, Informative
      I mean, correct me if I'm wrong, but I don't think Linux (any flavor) or Windows (any flavor) has recieved nearly the same amount of scrutiny and criticism with regard to UI. Why is that? Is it simply because Apple brags about it so much? Is it a recognition that Apple does it best (usually) and therefore it is fair that they should be evaluated based on that claim? I suspect that this is the reason.

      Well, somewhat. The parent post is correct in that OS X has still by far the best UI out there. Mac OS is the benchmark by which all user interfaces are judged, and so all changes to it are held to a much higher standard.

      The reason why the author wrote this article, though, is that, compared to the Mac OS 9 Fnder, the X Finder really is a mess (better in 10.2, but a polished turd is still a turd). Compared to Windows Explorer, X Finder still wins, but that's saying very little, isn't it? Nautilus is much better than Windows Explorer, but it still has at least a couple more major revs ahead of it before it approaches Mac OS Finder-territory.

      For those who didn't bother to read the article: the author's not saying that everything from Mac OS 9 should be brought back. He's not saying that Mac OS 9 was the end-all of user interface. He's saying that the Finder, as the center of the user's OS X experience, should be a substantial advancement over OS 9, and right now it's not. It's a kludgy, poorly-integrated hybrid of NeXT and classic Mac OS. He's saying the Finder should bring the best of NeXT and classic Mac OS into a unified whole, along with a few other much-needed enhancements.

      And I think he's right. Hopefully Panther (10.3) Finder will head in the direction suggested by this article.

      For any newbies out there who might be confused: the Finder is the Mac file browser, equivalent to Windows Explorer, Midnight Commander, or Nautilus. It is not the user interface to all applications -- it is the tool you use to get to (or "find") your applications and documents.

    22. Re:I don't agree with the article by feldsteins · · Score: 1

      Excellent points, every one. If I had mod points right now you'd know it.

      --
      You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
    23. Re:I don't agree with the article by drsmithy · · Score: 1
      I mean, correct me if I'm wrong, but I don't think Linux (any flavor) or Windows (any flavor) has recieved nearly the same amount of scrutiny and criticism with regard to UI.

      Windows certainly does (or did). There are numerous sites around the 'net dedicated to criticising Windows' little UI oddities.

      You don't see much of it anymore simply because the UI hasn't changed majorly since IE4 appeared in late '97/early '98 (and I'd argue even that was a relatively minor update). Most of the UI critiqueing has already been done.

    24. Re:I don't agree with the article by Anonymous Coward · · Score: 0

      Also, on top of the valid criticism and analysis, there is a whole slew of interface 'criticism' from anti-mac zealots... as in "Here's a whole bunch of reasons the Mac UI sucks!" from a bunch of people who would never use a Mac, even if it were improved. If you're not paying attention, you might lump all the criticism in the 'valid' pile.

      Something about the Mac makes teenage PC users froth at the mouth (I know, I used to be the same). I think it might have something to do with the difficulty of learning an inconsistent interface, and seeing anything simpler as somehow derogatory to their intelligence.

    25. Re:I don't agree with the article by andrewski · · Score: 1

      Maybe you should try column view. The column to the left of the 'active' one will have the current folder highlighted.

    26. Re:I don't agree with the article by torpor · · Score: 1

      I don't agree either.

      I've used practically every OS in existence which offers a GUI, and so far, OSX (combined with Launchbar) has given me the most satisfying personal productivity experience.

      Finder is something I rarely use for anything more than just quick-click launching of files, and for basic file management.

      But I have to say that Launchbar has definitely become the #1 reason it's so productive to use OSX these days. If you're on OSX and you haven't tried Launchbar, you're missing out on a power tool.

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    27. Re:I don't agree with the article by Herbmaster · · Score: 1

      It's not just that people have high expectations from Apple. It's also that Apple just completely rotated its feature set while keeping the user base the same - and the expectations of those users. With OS9, users had a certain UI which was really, really strong in a lot of ways. OSX brings a number of enhancements to that UI (the dock, aqua), but also makes it a lot worse in a lot of ways (the dock, aqua - and read the article). A large subset of Apple users are going to notice these failures and complain about them. Many aspects of OSX did this, BTW. OSX is faster than OS9 (multitasking), but it's also a lot slower (actually using anything, especially graphically intensive things). OSX has much better memory management (VM doesn't suck), but it's also a little worse (VM can't be turned off and is used in situations where it shouldn't be). The system became much more open (Darwin is open source) but it also became much more closed (the amount of stuff you can customize, at least for now, is a lot less - display control, input device control, lots of functionality provided by 3rd party extensions in OS9 land).

      This is not comparable to anything that happened elsewhere recently. Linux 2.4 did not come out missing a lot of what Linux 2.2 offerred (well, maybe it did in terms of stability, but I don't think the situation is comparable). Windows XP did not come out missing a lot of what Windows 95/98/ME offered. Now, if Microsoft had come out with Win98 and WinME and promoted them as replacements for NT 4, that would have been comparable. But they knew better than to do that. Apple was smart for not forking their OS into 2 products (a move Microsoft has only really recovered from with XP, but even so it's still forked much more than OSX/OSX Server are).

      This *is* comparable to the 68k to PPC transition. PPC Macs were a lot faster, but they were also a lot slower since everything had to be emulated. However, that transition really wasn't that bad. And since it's just speed, it's easy enough to let Moore's law take care of that problem with time. Except for the part where Motorolla suspended Moore's law for PPCs for a year in 1999, but I digress...
      --
      I'm not a smorgasbord.
    28. Re:I don't agree with the article by mixmasta · · Score: 1

      I do agree with it. You say in the next sentence you don't really use the original Mac OS, and that's the problem. The gui's you mention are all just poor copies of each other. Maybe you used it a few times and didn't see what the fuss is about.

      Really, until you sit down in front of an old mac for 6 months, without anything else available, you wont understand. About 10 years ago this was what happened to me at a job, until they coughed up a PC for me to use as well. Once you learn how things should work, it just sucks to go back.

      Imagine a computer where you almost always know where your shit is, because you recognize it by sight, as well as name. If you don't like an application in this folder..... move it to that folder, and it still works!! Try such a simple thing on dos or unix and watch it crash and burn, bitching and complaining about its libraries, as if I care.

      They solved that problem 20 years ago for crying out loud.

      Of course this simplicity is also saddled by piss poor multitasking and Windows 95 level stability. It is an imperfect world =(.

      OS X still hasn't reached the goal of a mac gui on a modern kernel, although it is arguably the closest.

      Acutally I prefer the fonts and feel of the gui on windows xp (de-fischer-priced, of course), although it still doesn't have the elegance of the finder a decade ago. YMMV.

      --
      #6495ED - cornflower blue
  3. Paying more, getting less by Mainframes+ROCK! · · Score: 1, Interesting

    I have been a Mac user for some years and I just want to bleat that with OS X we have been paying more for a crippled and slow Finder as compared to Mac OS 9. This is the primary user interface to the computer and should have gotten as least as much attention as iTunes and those other toys. Also, what happened to AppleScript recordability of the Finder? BAH!!!!!

    1. Re:Paying more, getting less by theWrkncacnter · · Score: 1, Interesting

      The problem is that for some reason they coded the Finder in carbon instead of cocoa. I've heard it was to show people the viability of coding in Carbon and that there was some continuity between the two systems. Whatever the reason, it wasn't a good decision IMO. I mean could you imagine how cool the finder would be if we could use Cocoa Gestures in it? Not to mention that it would be much faster. Maybe in 10.3 we'll get a cocoa Finder, thats first on my list.

      --
      -1 (Troll) is antihammer
    2. Re:Paying more, getting less by Raffaello · · Score: 1

      Or you could just get PathFinder now:

      PathFinder is a cocoa Finder replacement, and is really quite nice.

  4. Pah, cann't be bothered reading the article by Neophytus · · Score: 0, Insightful

    But one gripe I have is that they have dumped the chooser for some connect to network location thing. I may not use Macs much, but at school I have too and having to fumble about with an unfamiliar inferface when trying to get onto my shared folder is a pain. Adding to the functionality should of been a priority (it was quite restrictive imo) - not replacing it.

    1. Re:Pah, cann't be bothered reading the article by EvilStein · · Score: 1

      The Chooser wasn't really meant to be a network tool anyway - it just kind of ended up that way after people thought "Hey, let's plug AppleShare into here!"

    2. Re:Pah, cann't be bothered reading the article by adri · · Score: 1

      Regardless of its origins the Chooser interface is sorely missed by just about any MacOS user I've come across.

      That aside, there is gobs of room for improvement in mounting SMB shares. The interface is .. cubersome feeling. That big empty dialog box with a small drop-down box to select a share - eww. Those error _CODES_ when an SMB mount fails - double eww.

      It feels like someone just slapped it on as an afterthought. ;/

      Apple, if you're listening, please improve your SMB mount interface!

    3. Re:Pah, cann't be bothered reading the article by diverman · · Score: 1

      Well, I tried not to use a Mac pre-OSX, but from what I remember, I used Chooser to do something like select a printer on the network. Rendezvous has replaced the need for a user to do ANYTHING to access a printer.

      It never made any sense to me why what should have been a "Finder" interface (connecting to shares...essentially a folder that's saved somewhere else) was in a burried configuration utility. Hmmm... in OSX, if I want to connect to a machine, I use the Finder now. "Go->Connect to Server". Or for you quick-key weenies (yes, I am one myself), Command-K. I always thought the Chooser to be a very unintuitive interface compared to the Finder.

      Anyway... you old-Mac users really need to think about the design sometimes. As another reply to this post pointed out... Chooser just got STUCK with AppleShare. It wasn't even designed for it. And if something wasn't designed for a particular use, it often times shouldn't be there. Hmmm...where can we hack this support into?

      I admit, OSX's Finder could use some improvement. Better use of extended attributes would be nice. But before OSX, I wouldn't touch a Mac if I could help it. I even preferred Linux with X-Windows for God's sake, because I could do more than one thing at a time, at the sacrafice of a pretty interface. REAL productivity people! If you are going to use that argument for a Mac, lets remain consistent to the Big Picture.

      -Alex

    4. Re:Pah, cann't be bothered reading the article by Dephex+Twin · · Score: 2, Informative

      The Chooser for file sharing was a hacked together piece of shit. Even when they were still in OS 8 and 9, they made an app to replace the network part of it. If someone spends 5 minutes with the new Connect to Server dialog they will be used to it. Sure, if you're looking for something like the Chooser, you might not know what you *should* be looking for, but that is the case for anything that is changed between 9 and X. The Chooser was probably one of the more embarrassing things about the Mac OS, and bringing it on into OS X would have been like putting a rotary dial on a cell phone.

      Honestly, if Apple *had* ported the Chooser to OS X, I think a lot of people would have pointed to that as an indicator that the Mac OS was doomed.

      I can't think of a worse idea.

      --

      If you want to make an apple pie from scratch, you must first create the universe. -- Carl Sagan
    5. Re:Pah, cann't be bothered reading the article by mosch · · Score: 1
      Yeah the error codes can suck a cock. 'error -47' what the fuck is that?

      Though honestly the far, far more annoying bug is that an smb mount failure can result in the shift key not functioning properly in Illustrator. I'm not kidding.

    6. Re:Pah, cann't be bothered reading the article by Anonymous Coward · · Score: 0

      THen there's the kernel panic that ocurrs when you mount an SMB share and that computer drops its connection

    7. Re:Pah, cann't be bothered reading the article by cpt+kangarooski · · Score: 1
      Regardless of its origins the Chooser interface is sorely missed by just about any MacOS user I've come across.


      You're kidding, right? Everyone knew the Chooser was a big mistake at about the time it went from involving more than which serial port the printer was plugged into.

      The real problem has just been that no one's ever had a good replacement for it.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    8. Re:Pah, cann't be bothered reading the article by Arctic+Fox · · Score: 1

      It's kind of funny/kind of sad that that dialog box (which i've seen many times), goes against the Apple Interface Guidelines.
      I'm new to MacOSX, had a long flight, so i started reading random PDFs on the disk. Found that one. Neat reading, but long.... and sometimes boring.

    9. Re:Pah, cann't be bothered reading the article by drsmithy · · Score: 1
      But one gripe I have is that they have dumped the chooser for some connect to network location thing.

      Ugh. The chooser was horrible. OTOH, in OS X they actually managed to make it *worse* with the "Connect To" dialog. Quite an achievement...

  5. OS X is in its infancy by Seanasy · · Score: 5, Informative

    I love OS X. But it is such a huge change from OS 9- that I consider it a newborn new OS albeit with a very rich parents. I think what we've seen so far is just the beginning. They had to get things to work first. Refinements will be forthcoming.

    While a lot of the article is interesting -- live folders sound useful -- I'm content with the Finder. It could -- and I'm sure will -- get some tweaking but I don't find it an obstacle in my daily work.

    1. Re:OS X is in its infancy by EnderWiggnz · · Score: 2, Funny

      i'm just happy that Apple implemented RFC 3514

      its very important, and i dont understand why slashdot isnt posting it.

      --
      ... hi bingo ...
    2. Re:OS X is in its infancy by Kingpin · · Score: 1


      I agree 100%. I compare the development of OS X to Mozilla, after the initial production quality (10.0 and 1.0 respectively in my eyes) release, the products have just kept in getting better with astonishing speed.

      --
      Unable to read configuration file '/bigassraid/htdig//conf/14229.conf'
      Geocrawler error message.
    3. Re:OS X is in its infancy by Seanasy · · Score: 1, Troll

      OK, I admit I only skimmed the article. But, I've gone back and skimmed it again and now I think the author is an idiot.

      Bookmarks - A simplified version of this feature already exists in the form for "Favorites", but it seems only natural to expand this feature to match the bookmarking facilities found in web browsers.

      How is favorites different from bookmarks again?

      Back/forward buttons with history - The OS X Finder already has back and forward buttons, but they lack history pop-up menus. And although the "Recent folders" menu item keeps track of a handful of past locations, it is very limited when compared with the robust history tracking found in most web browsers.

      So he says the Finder needs' Back/forward buttons with history.' Then he goes on to say that is has them. His only complaint is that the history isn't long enough.

      A stop button - In a browser environment, users should decide when to stop waiting for a slow network disk, or other long-running task. A folder can just be closed if the contents are taking a long time to load, but browser windows are "reusable" and should not be tied to the performance or accessibility of any single location.

      This is just dumb and the web browser comparisons are going too far. How can he be criticizing the Finder for HCI problems then go on to complain that it's missing web browser features. He later claims he isn't trying to make it into a web browser yet he wants most web browser features. The confusion of the two in Winbdows and KDE is, in my opinion, one of the biggest usability disasters to hit desktops. 'Stop' does not make sense in the context of a file browser. Network drives shouldn't take a long time to browse but other ways must be found to keep the Finder from hanging.

      An address bar with auto-completion - This is probably an "expert" feature, but why not add a proper address bar to the list of toolbar components? In addition to history-based auto-completion, it should also support shell-style tab-completion for file paths.

      Command-Shift-G. Auto-completion and everything. Put it in the toolbar and you'll confuse the average user as well as make the Finder look more like a web browser. Leave it as it is and the 'experts' have it at their fingertips, average users don't have to even think about it.

    4. Re:OS X is in its infancy by Anonymous Coward · · Score: 0

      I quite like the current finder too. That said I am currently trialing "lauchbar" which enables me to access the finder without the mouse and IS an improvement (though i also like to use the finders column view at times.)

      http://www.obdev.at/products/launchbar/index.htm l

    5. Re:OS X is in its infancy by groomed · · Score: 3, Insightful
      You are missing the point. Classic had all these things that the author is talking about -consistency, spatiality, concreteness- from the very beginning. Those weren't properties that evolved out of a process of refinement: instead they permeated the system throughout and guided every development effort, sometimes to detrimental effect: the 2-fork file concept makes it rather difficult to transmit files for example.

      In any case, I agree with the author. Just to name an example, having to "associate" icons with "file types", as both Windows and Nautilus do, is a totally retarded way of doing things. One thing you could do on the Mac was click any icon on the desktop and paste in a new image from the clipboard. Because Classic MacOS files stores icons in the files themselves, this would work, always, even if you put the file on a floppy and moved it to another Mac: the file would retain its icon. This was also true for icon and window positions: thus, you could arrange icons and windows (and the icons within windows) in the way that makes the most sense, then burn a CD that preserves all this information.

      The whole mess we have now with "icon databases" that maintain relationships between files and their icons is dumb and broken in comparison. Even now, as filesystems slowly are starting to acquire metadata in the form of file attributes (fifteen years after Classic MacOS), a system like Linux has yet to learn how to copy a file and actually retain the attributes on the copy.

      In my more cynical moods, I sometimes think that as long as we have "minimalist" CS types telling us that "files should be flat" and that "everything should happen in userspace" we will continue to suffer schizophrenic, fractured interfaces.

    6. Re:OS X is in its infancy by ianscot · · Score: 1
      You are missing the point. Classic had all these things that the author is talking about -consistency, spatiality, concreteness- from the very beginning.

      I've used the Mac OS off and on since it could boot on a single 800k floppy -- my 512ke's -- and "from the very beginning" is a little much there. It's been a great OS, still is very usable, but along the way any snowball's going to pick up some dog stuff from the yard.

      "Consistency"? In any Mac OS pre-X, drag a folder containing both files and folders to the trash. What happens to it? Now drag a mounted disk there -- again, one with files and folders "inside." What happens to that? Not the same thing. Pretty unsettling lack of consistency for many users. 'Nother example: to manipulate files and folders on my hard drive, I use the finder... to open a folder over a network, though, I "choose" the network resource as I would a printer... Bad attempt to double-up features within the Chooser, if you ask me.

      I basically agree with the parent that the new OS is young yet. Classic prior to this had a lot of history and refinement behind it -- and no, OS X isn't there yet. It's sometimes pretty amusing seeing 'Nix people say how smooth X is, because it just isn't where the old OS was in terms of UI in my book. But neither one was or is perfect -- and neither one seems especially wrongheaded, to me.

      --
      "Fundamentalism" isn't about divine morality. It's about human authority.
    7. Re:OS X is in its infancy by Anonymous Coward · · Score: 0

      anyone who's anyone is 3514 compliant!!

    8. Re:OS X is in its infancy by John+Siracusa · · Score: 2, Insightful
      "Bookmarks - A simplified version of this feature already exists in the form for "Favorites", but it seems only natural to expand this feature to match the bookmarking facilities found in web browsers."

      How is favorites different from bookmarks again?

      I could be snide and say "use each feature and find out for yourself", but I'll be nice and say that Favorites are a flat list with a fixed order, whereas most web browsers allow bookmarks to be arranged into folders, ordered arbitrarily, and include niceties like menu separators.

      "Back/forward buttons with history - The OS X Finder already has back and forward buttons, but they lack history pop-up menus. And although the "Recent folders" menu item keeps track of a handful of past locations, it is very limited when compared with the robust history tracking found in most web browsers."

      So he says the Finder needs' Back/forward buttons with history.' Then he goes on to say that is has them. His only complaint is that the history isn't long enough.

      First, you're ignoring the request for history pop-ups on the back/forward buttons. Second, decent web browsers do more than just provide a long, linear history list. Take a look at Safari's history menu or Mozilla's history pane for some examples.

    9. Re:OS X is in its infancy by Seanasy · · Score: 1

      Wow, I was a jerk in that post. I apologize. Thanks for calling me on it so gracefully. I responded with more emotion than the subject deserves.

      I still disagree if only because I don't want my file manager becoming more web-browser-like. You're correct that those features differ but I think the difference is important.

    10. Re:OS X is in its infancy by drew · · Score: 1

      so when somebody sends me a file (or i download one) i'm stuck with all the previous users (or creator's) metadata and icon choices? NO THANKS!!

      it already drives me nuts to have to delete the id3 tags on any mp3's i download because they're often wrong and almost always not in my desired format. i can only imagine how infuriating it would be if icon preferences and who knows what else was also stored along with the file. and burning it all onto a cd where this information is read only? it would make me want to scream.

      in short, as soon as you want to exchange a file with somebody else, all of your precious metadata becomes a curse rather than a blessing. but hey, as long as you live in an isolated world where you're the only person who uses or sees your files, go nuts! but when you decide to join the rest of the internet, please store your metadata somewhere else....

      --
      If I don't put anything here, will anyone recognize me anymore?
    11. Re:OS X is in its infancy by Anonymous Coward · · Score: 0

      Sure, if you're a neurotic control freak with a micromanagement fetish, I can see how metadata would freak you out. I suppose other things you feel uncomfortable around include women, other people, and life in general. A word of advice: if and when it all becomes too much, remember to slit lengthwise! A perfectionist such as yourself owes it to himself to get it right the first time around.

  6. Re:a better finder? by BWJones · · Score: 2, Insightful

    Now seriously, I've been thinking in buying a Mac to port software to MacOS... I wish they had some more market share so my decission would be a bit safer.

    Actually, a smaller market share means fewer potential competitors that you will have to worry about. In the Windows market, you have to worry about competing with dozens of other developers and companies. There are many other advantages to developing for OS X as well, and if your code is already written for another UNIX platform, in many cases, much of the code can be brought over through a simple recompile. I am running code originally written for SGI that was simply recompiled for OS X and it runs in an X windows environment. Easy peasy.

    --
    Visit Jonesblog and say hello.
  7. Re:a better finder? by reiggin · · Score: 2, Interesting

    Ok, I'll bite. If you're porting useful software to the Mac, there's no need to give that pudgy comment about "more market share." Useful software sells on the Mac. Heck, sometimes even seemingly un-useful software sells (Konfabulator?). I don't think a small business software designer (which I assume you are) needs to worry about Apple having 5% marketshare verses 15% or 20% marketshare. You'll sell just as much either way, most likely.

  8. A Better Finder by nf0 · · Score: 4, Interesting

    As a long time user of Linux, new to the world of OS X. I've found the best finder , is just to drop in to a terminal or iTerm and do things the easy way. Command line is faster, to me anyway.

    1. Re:A Better Finder by peter_gzowski · · Score: 4, Insightful

      The command line is faster if you have a good memory. And it's easier to search for and manipulate files based on their filename/size/type from the command line (assuming you have a decent shell, and a good command of regex expressions). However, if all you want to do is go a couple directories deep and copy a group of files from that directory to another, a file browswer like Konqueror is just as fast. What I think would be great is a shell that's linked to a graphical file browser. If Konsole and Konqueror were linked, such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff," then I would get the power of a terminal but the easy visualization of the graphical file browser. THAT would be killer.

      --
      "Now gluttony and exploitation serves eight!" - TV's Frank
    2. Re:A Better Finder by Corgha · · Score: 1

      That sort of functionality was present in "efm", the file manager for Enlightenment 0.17, before they yanked it so they could waste the past three years or so re-writing everything from scratch and putting wrapper libraries around stuff (then re-writing those wrapper libraries). (OK, so I'm bitter -- yesterday's joke opened up old wounds.)

      Anyway, it had other cool features. You could execute commands in the window as well. For instance, type "make" and it would pop up an xterm with make running in it. You could type "*.mp3" and all the mp3s in the directory would be highlighted. It seemed like it was going to be a really good synthesis of command line and GUI.

      You can probably still get out of CVS, but since everything is constantly being re-written from scratch, I'm not sure if it's worth the time trying to find stable points in all the various libraries and components.

    3. Re:A Better Finder by IamTheRealMike · · Score: 1
      Yes, for experienced users. The command line is deadly for anybody else though - even for people with lots of experience it's all too easy to accidentally delete files, overwrite them with junk because you're going so fast the slightest mental slip and you're dead.

      GUIs like the Finder are slower for most operations, but they give users a safety net that is usually appreciated.

    4. Re:A Better Finder by usotsuki · · Score: 1

      Hmm, what about running Midnight Commander on MacOS X?

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    5. Re:A Better Finder by jimm · · Score: 1
      What I think would be great is a shell that's linked to a graphical file browser. If Konsole and Konqueror were linked, such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff," then I would get the power of a terminal but the easy visualization of the graphical file browser. THAT would be killer.
      OS X has that. Type Command-Shift-G and a small popup "sheet" lets you type in a path. It does tab completion, too.
      --
      Transcript show: self sigs atRandom.
    6. Re:A Better Finder by Moloch666 · · Score: 1

      WOW, those features sound perfect. I wish KDE or some one would step up and implement that. I always find my self using a terminal and a GUI file manager at the same time.

      --
      Understanding is a three-edged sword. -- Kosh Naranek
    7. Re:A Better Finder by Christianfreak · · Score: 1

      That would be awesome, I'd also like if files in my command shell were clickable or selectable and opened the correct application when clicked.

    8. Re:A Better Finder by evilviper · · Score: 1
      What I think would be great is a shell that's linked to a graphical file browser. If Konsole and Konqueror were linked, such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff," then I would get the power of a terminal but the easy visualization of the graphical file browser. THAT would be killer.

      You are thinking about it the wrong way. What you apparently want is a command-line in your filemanager. Personally, I use emelfm, which has a command-line which acts just like an xterm. You read the output in a part of the filemanager, so I wouldn't recomend doing serious work on the command-line, but it's perfect for highlighting a few files/folders in the filemanager and running DU or something else on them... It's much quicker and easier than typing everything out in a terminal.

      The feature closest to what you want, is the ability to open an xterm from the directory you are looking at. It's very quick and easy, and I use it very often (eg. change to a folder, click on a TGZ to extract it, open an xterm and type make). It's a very nice gtk-based filemanager. I suggest everyone at least spend 5 minutes to try it.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    9. Re:A Better Finder by ceswiedler · · Score: 1

      You can do this, exactly as you say. I forget where the option is, but it lets you have a Konsole window attached to the bottom of a Konq window. When you change dirs in Konq, it cd's in the Konsole. That's about as far as they're linked, but it lets you do pretty much what you say.

    10. Re:A Better Finder by Merk · · Score: 1

      This brings up a question...

      Ever since I've started using OS X I've used the Terminal too, the trouble is that it seems just slightly unresponsive. I especially notice it when I'm trying to autocomplete using the tab key. It's almost as if it has to reload some sound library to make the bell sound, and that ties things up for a fraction of a second. Has anybody else noticed this slight lack of responsiveness in Terminal?

      In case it matters I'm using the newest release of Jaguar on an iBook with 256 MB of RAM.

    11. Re:A Better Finder by Phroggy · · Score: 1

      That would be awesome, I'd also like if files in my command shell were clickable or selectable and opened the correct application when clicked.

      Type "open filename"; "man open" for details.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    12. Re:A Better Finder by jpkunst · · Score: 1

      such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff,"

      Guess what happens when you type open ~/Documents or open . or open .. in OS X's Terminal.

    13. Re:A Better Finder by DebtAngel · · Score: 1

      fwiw, you can turn on the command line in the Konqueror window, and it puts a little xterm at the bottom (about eight lines long). The option is in the Window menu, if I recall correctly.

      --

      Is this post not nifty? Sluggy Freelance. Worshi

    14. Re:A Better Finder by spencerogden · · Score: 1

      What I think would be great is a shell that's linked to a graphical file browser. If Konsole and Konqueror were linked, such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff," then I would get the power of a terminal but the easy visualization of the graphical file browser. THAT would be killer.

      Go to the 'Window' menu -> Show Terminal Emulator

      Does exactly what you want.

    15. Re:A Better Finder by Anonymous Coward · · Score: 0

      nope, you just get the konsole (no linking). try typing ~/Stuff in the address bar - and yes, it does tab completion

    16. Re:A Better Finder by Anonymous Coward · · Score: 0

      This has to be the most useful thread that I've stumbed across. I do most of my work in the terminal, but I do occasionally like to open a finder window. Since I usually want to open a Finder window in my current directory, I just created the following alias (for tcsh):

      alias finder 'open `pwd`'

    17. Re:A Better Finder by dingman · · Score: 1

      I've tried all sorts of file managers on all sorts of systems, and I find anything that doesn't display a file path or a folder tree confusing. The "spatial" file managers completely fail to convey the idea that one "open" folder may be *inside* another. A folder called "Amy" inside one named "family" is completely different from a folder called "Amy" inside one named "College friends", and if I blithely drop a copy of a letter I just wrote into one because it's open and the title bar says "Amy", I may never find it again.

      I don't memorize file paths, either. I use tab completion to look around inside directories, and it's a fact that I can find a file whose name and location I don't know in my home directory faster with Bash than with any graphical file manager.

      That said, I also find it easier to think about re-arranging files using a graphical manager - but not the "spatial" systems the author describes. Two windows, each with a pane for the folder tree and a pane for the selected folder's contents.

    18. Re:A Better Finder by Moloch666 · · Score: 1

      Thanks! I'll check it out when I get home. Depending on functionality it may be just what I need.

      --
      Understanding is a three-edged sword. -- Kosh Naranek
    19. Re:A Better Finder by Doctor+O · · Score: 1
      What I think would be great is a shell that's linked to a graphical file browser. If Konsole and Konqueror were linked, such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff," then I would get the power of a terminal but the easy visualization of the graphical file browser

      Maybe I'm just not getting what you want, this is what you can do in Windows since Windows 95. Entering the path (with tab-completion like in a shell) into the address bar an Explorer window will display the contents of that folder just fine. How is this different from what you describe? For your example, you can even spare the 'cd '.

      While thinking about it, I was wondering about uses of a shell-linked browser window apart from moving in the filesystem, but maybe I don't just have enough fantasy or knowledge of using shells for other than moving around and editing files and managing processes (in the widest sense).

      This is not a troll. I'm just getting interested for GUI design, and maybe there's something to learn for me here which I just don't get.

      --
      Who is General Failure and why is he reading my hard disk?
    20. Re:A Better Finder by SoupIsGoodFood_42 · · Score: 1

      It's not just about safty nets. I could easly use a CLI if I had to. But I just find a GUI much easier and better to work in.

    21. Re:A Better Finder by peter_gzowski · · Score: 1

      No, it doesn't. It's sort of close, but it only goes one way. Open Konq, hit Window -> Show Terminal Emulator. Yes, now they're both at my home directory. Click on some directory in the GUI, and it cd's to that directory in the shell, but if I cd in the shell, it doesn't change directory in the GUI. In fact, this is exactly the wrong way for me. I want to navigate with the shell and visualize with the GUI. Thanks for the tip, though. I guess I didn't explore Konq enough before posting.

      --
      "Now gluttony and exploitation serves eight!" - TV's Frank
    22. Re:A Better Finder by jlaxson · · Score: 1

      Just turn off the audio bell and use the visual one.

      --
      On Apple Input Peripherals: They're okay, I guess, but I was really hoping for a one-key keyboard and a 109-button mouse
    23. Re:A Better Finder by tmalone · · Score: 1

      you could also try ROX which is just about the most perfect file manager available. I still find myself switching back to the shell much of the time, but when I remember that its there, I find it very intuitive and fast. get it at: http://rox.sourceforge.net

    24. Re:A Better Finder by peter_gzowski · · Score: 1

      Entering the path (with tab-completion like in a shell) into the address bar an Explorer window will display the contents of that folder just fine. How is this different from what you describe? For your example, you can even spare the 'cd '.

      I guess if all I wanted to do was change directories, this would be ok (assuming that the focus stays in the URL bar, so that I didn't have to keep clicking there with my mouse). But I also want to see all files that match a regex pattern, rename a batch of files using a while loop, or whatever else I usually do in the shell, and then immediately see the change reflected in the GUI. I hope this is a bit more clear.

      --
      "Now gluttony and exploitation serves eight!" - TV's Frank
    25. Re:A Better Finder by Doctor+O · · Score: 1

      ACK. I don't use regex that much (only bread-and-butter usage when editing files), so it didn't come to mind. Thanks for explaining. I agree that would be a great thing. Shouldn't be that hard to implement?

      --
      Who is General Failure and why is he reading my hard disk?
    26. Re:A Better Finder by Anonymous Coward · · Score: 0

      Though I'am AC, some tips for you :

      In konq, you can : type CTL-O and your URL -- it does autocomplete.

      In fact, it autocompletes environment variables ! Type $HOME in the adress bar...

      Funky stuff is then possible : ALT-F2 -> setenv SOMEURL www.slashdot.org. In konq : $SOMEURL, press enter.

      you can also alias cd to something like : cd ; dcop konqueror OpenURL $PWD. (check out the exact syntax :))

      I hope you stoop so low as to read what ACs post ;)

    27. Re:A Better Finder by peter_gzowski · · Score: 1

      I do stoop so low. That alias is a good idea, but there are two problems:

      1) the "cd" before the semicolon needs to be able to take the argument (i.e. the directory that you want to cd to). I forget how to do this, I'll go look it up after I post...

      2) this will open a new konqueror every time you change directories, I think, unless that "dcop" you have in there causes it to use an already open konq. I'm not sure what that is, and I couldn't bring up a man page on it.

      Getting closer...

      --
      "Now gluttony and exploitation serves eight!" - TV's Frank
    28. Re:A Better Finder by biggyfishy · · Score: 1
      This is exactly how I imagined Mac OS X would be when I first heard about it.

      There would be a command line in Finder windows (as an option, of course) with the working directory in that folder.

      Unfortunately, it was not to be.

    29. Re:A Better Finder by dalamcd · · Score: 1
      I'm not sure, but I think the grandparent was being sarcastic... although open is, indeed, quite useful.

      dalamcd

      --
      moer liek CELtroid prime!!@1!
    30. Re:A Better Finder by roskakori · · Score: 1
      If Konsole and Konqueror were linked, such that when I typed, "cd ~/Stuff" in Konsole, Konqueror would act like I'd clicked on "~/Stuff," then I would get the power of a terminal but the easy visualization of the graphical file browser.
      in the terminal of mac os x, you can type
      open ~/Stuff
      and the finder will open the specified folder. my personal favourite is "open .", which saves a lot of time for many common tasks.

      btw, you can do the same in windows' console, for example "start ." and "start c:\stuff".

    31. Re:A Better Finder by spencerogden · · Score: 1

      dcop is KDE's interprocess communication protocol. So in theory you could communicate with the konq window you were in. I don't know the details though and it would seem to me that the dcop command would have to be different for each window.

  9. Re:mac problem by ruiner13 · · Score: 1, Informative
    "I've been sitting here at my freelance gig in front of a Mac (a 8600/300 w/64 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this Mac, the same operation would take about 2 minutes. If that."

    8600 you say? a computer made in 1995? I don't think anyone would ever expect an 8 year old computer to do things as fast as one today. Plus, IIRC, that computer has a blistering 5MB/sec SCSI bus internally, not exactly made for fast file transfers (in today's terms). Try the same transfer on anything made in 1997+ (with the ATA bus in it) and I think you will see a huge difference. Not to mention your computer seems pretty hackneyed, there was no 8600 with a 300MHz proc. I guess you may have upgraded to a G3 (or worse yet a 300MHz 604), but it is still on OLD computer and if you are trying to use OSX on it (read not supported), don't judge it.

    --

    today is spelling optional day.

  10. Re:mac problem troll by teamhasnoi · · Score: 1

    I love this one.

  11. Re:mac problem by ecchi_0 · · Score: 1

    It's an old mac not running OS X. What's your point? (plus this is a troll I've seen a couple of times...)

  12. Re:mac problem by Anonymous Coward · · Score: 1, Insightful

    YHBT, YHL, HAND.

  13. Locate? by luzrek · · Score: 4, Insightful

    Maybe this is showing my ignorance of Mac OSs, but why cannot Mac OSX simply have a graphical interface for locate? Locate looks at a database and very quickly returns all the matches (vs. searching through the whole disk). Since Mac OSX is supposed to be a close relative of NeXT this should be trivial.

    --

    Galium Arsenide is the material of the future, and always will be.

    1. Re:Locate? by mbbac · · Score: 1

      People have made GUI front ends for locate.

      --

      mbbac

    2. Re:Locate? by Anonymous Coward · · Score: 0

      Bam, there you go. And that's only one of several.

    3. Re:Locate? by cbowland · · Score: 1

      This depends on how frequently the locate database is updated. Obviously, any file created after the last update will not be found. I don't remember how often the updatedb command is run (I think is is weekly) but this would not serve as a replacement for the Finder. Of course, you can edit the crontab and have updatedb run more frequently, but that does not solve the problem of files created after that point (it just shortens the window).

      --

      Give a man a fish and he will eat for a day.
      Teach him to eat and he will fish forever.

    4. Re:Locate? by luzrek · · Score: 1

      I run updatedb dayly. Also, I don't ussually forget where I just saved a file, but I'm a command prompt person. However, provided that the DB that updatedb updates is normalized, it should be pretty easy and fast to update individual entries everytime a file is added or moved. Maybe it would be faster to have a second, suplamentary database for storing short term updates. I don't think its done on file servers/default *nix systems because lots of users would mean lots of updating. For a single user system it should be practical however.

      --

      Galium Arsenide is the material of the future, and always will be.

    5. Re:Locate? by cbowland · · Score: 1

      The locatedb database is not a relational database, so it cannot be "normalized."

      --

      Give a man a fish and he will eat for a day.
      Teach him to eat and he will fish forever.

    6. Re:Locate? by luzrek · · Score: 1

      Guess making a smaller database or a flat file for temporary access would be the way to go then.

      --

      Galium Arsenide is the material of the future, and always will be.

    7. Re:Locate? by Anonymous Coward · · Score: 0

      Locator is a Cocoa GUI to locate, grab it here:

    8. Re:Locate? by Anonymous Coward · · Score: 0

      Locator is a Cocoa GUI to locate, grab it here:

      http://www.sebastian-krauss.de/software/

      Having said that, the search field at the top of every window is very fast, so I've used locator less and less.

  14. Re:mac problem by reiggin · · Score: 1
    I'd rather hear some intelligent reasons why anyone would choose to use a Mac over other faster, cheaper, more stable systems.

    I'd rather hear some intellingent arguments rather than some very lame ones using outdated, unsupported hardware for current positions. That's just ignorant and pointless. Of course your NT 4 box is going to outperform a 8600 running OS 8.5 or 9. AND if you're running OS X on that... shame on you! Put Linux on it if you want a fair hardware comparison to that NT4. We all already know and admit that everything before OS X sucks. We dont need to be reminded. And, again, if you were talking about OS X, stop. You can't make legit comments on OS X sucking if you're not running it on recommended hardware.

    Did I just get hooked by a troll?

  15. I may sound really stupid, but.... by Captain+Rotundo · · Score: 4, Informative

    What the hell is a 'finder' ? I don't use Mac OSX and never used MacOS, but I constantly see people talking about the 'finder' I am very curious what is it? I use GNOME, so if you could related it to a feature of that maybe I would understand better.

    1. Re:I may sound really stupid, but.... by gnuadam · · Score: 1

      Think Nautilus. On windows, it's the "my computer"/explorer stuff.

      --
      You say :wq, I say ZZ. Why can't we all just get along?
    2. Re:I may sound really stupid, but.... by monadicIO · · Score: 1
      Imagine trying to take all of the great shell command-line utilities like ls, find, grep and combine them into one gui mess.

      I'm not criticising MacOS in particular, but there really are places where a GUI is just not the right thing to use.

      --

      The law of excluded middle : Either I'm foo or I'm foobar

    3. Re:I may sound really stupid, but.... by IamTheRealMike · · Score: 3, Informative
      The finder, for those who might not have used a Mac (ie quite a lot of people I should imagine), works something like this:

      Basically, it is like Explorer in Windows, or Nautilus in GNOME. It runs all the time, you cannot quit it. I think it draws the desktop. The finders default mode is column based, this is rather different to traditional file managers. Each folder "level" in the heirarchy gets a new column, starting from left to right. Clicking a folder shows a new column with the contents and a vertical scrollbar on the right. You click and scroll your way through the hard disk, rather than interacting with a tree, like in Explorer/Konqueror.

      This is quite a bit different from the one in MacOS 9. My knowledge of that OS is a little rusty these days, but I think it was traditionally what is called an "object oriented" file browser, see ROX on Linux for an example. Win95 took this approach by default (in the very first releases). In this model, each window shows one folder, clicking a folder opens a new window. There is no concept of a "file manager" as such, it's an integral part of the desktop. There is no concept of pathing - although MacOS 9 did indeed have a path separator, virtually nobody knows what it is (a : character).

      Normally OO browsers have a spring loaded folders implementation to make the large number of windows that can be generated with this approach more manageable, unfortunately this technique is patented by Apple which one reason why Nautilus hasn't moved to it, the GNOME guys have been thinking of possible ways around this patent, as well as other browsing metaphors.

      Anyway, I digress. Basically, IIRC people have several issues with the OS X Finder beyond its design, namely that it's slow (perhaps why it doesn't use lots of new windows??) and not multithreaded, so a blocking connection or blocked device will freeze it. Window resizes are also very slow, but that's more an issue with OS X in general.

      It also pretty much abandoned the OO model in favour of a navigational one, the usability merits of which are hotly debated. You can still have OO style windows of course if you want them, but I don't think that's what new users see. The first releases didn't even have spring loaded folders, pretty essential for the OO model.

      Other than that, I think the Finder is really quite a nice program, though I never used it heavily. The column system is OK, it's not fantastic or anything but gets the job done. The tree widget it uses is incredibly feeble, so it's just as well. The fact that you can drag any object into the toolbars is also a nice touch, think iconic bookmarks.

    4. Re:I may sound really stupid, but.... by kalidasa · · Score: 1

      File manager/desktop manager, basically.

    5. Re:I may sound really stupid, but.... by Anonymous Coward · · Score: 0

      If only I had moderator points. Mod the parent UP UP UP!!!

    6. Re:I may sound really stupid, but.... by remusrm · · Score: 1

      for a dude that use linux and gnome your knowleged of computers is less then I exprected.

    7. Re:I may sound really stupid, but.... by Anonymous Coward · · Score: 0

      it's a stupid word.

      the finder=kde
      the finder=gnome
      the finder=win xp gui

      it's the freaken gui, more specifically it's the thing that lets you FIND YOUR SHIT.

      when you double click on the "drive" icon, and start surfing folders...you are using the ALL MIGHTY FINDER.

      it should be more aptly named, the HIDER.

    8. Re:I may sound really stupid, but.... by Captain+Rotundo · · Score: 1

      so simply because I use one piece of software you exprected me to know something about another piece of software?

    9. Re:I may sound really stupid, but.... by sgi_oh_too · · Score: 1

      usually people into open source operating systems have tried all the other operating systems first ... unfortunately over the years the bloated click to install linux distros have spawned lots of ignorant schmucks in the open source world ... leeches that never fix/report bugs ... just yap about how they want all the features of windows and big time server iron operating systems (that they read about in a mag at b&n that they will never buy) put into linux ... its a sham ... how about you wake up and get your damn head out of the hole you leave it in ... buy an sgi machine on ebay ... sell it ... get an amiga ... sell it ... get an old sun machine ... etc ... just get out there and learn something!

    10. Re:I may sound really stupid, but.... by cpt+kangarooski · · Score: 1

      Oh, you can quit the Finder. And even run a different program in its stead. Such as (back in the day) Multifinder, or Minifinder. At Ease was originally a Finder replacement as well.

      And of course, since the OS would automatically run any program named Finder in the System Folder at boot, lots of people made boot disks with other programs that would run automatically, particularly diagnostic and repair tools, but it could be anything.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    11. Re:I may sound really stupid, but.... by remusrm · · Score: 1

      some broad knowleged yes

    12. Re:I may sound really stupid, but.... by MrTangent · · Score: 1

      "What the hell is a 'finder'?"

      Unfortunately no one can be told what the finder is... you have to experience it for yourself.

  16. could be better (Re:I don't agree with the articl) by Anonymous Coward · · Score: 0

    The author isn't saying that it sucks, just that from a usability point of view he believes that earlier Mac OS versions (Mac OS <= 9) were better.

    Apple has (arguably) one of the best UIs around, the author is simply saying that they could do better. The article is a list of stuff that could be done to improve what's already there.

  17. Re:Stupid OSX by Anonymous Coward · · Score: 0

    Stupid User.

    See the finder?
    See the 3 buttons above the word "View"?
    Click the 3rd button.
    Click the date column.

  18. Re:mac problem by objekt · · Score: 1

    You could run BeOS on that 8600 and really see how fast it can go.

    --
    -- Boycott Shell
  19. How did this get modded to 5? by Anonymous Coward · · Score: 1, Interesting
    It is easy to criticize. I use OS X about 80% of the time, Linux/KDE about 15%, and Windows 2000 about 5%. OS X, in my opinion, gives the best desktop experience.
    So the environment you work in the overwhelming majority of the time (and thus the one to which you are the most acclimatized) is, in your personal, anecdotal opinion, ubsubstantiated by any actual arguments, the best one. Congratulations.
    Any desktop uses a spacial metaphor for data - however, for me, the desktop is just a holding area - short term memory, if you will.
    Uh... this article is about the Finder. The Finder is an application, not a "desktop".
    Anyway, it is a free world - I will stick with OS X.
    Uh... where in the article did anyone ask you to switch? A "free world" (a phrase which is demonstrably false to the extent that it's even meaningful) doesn't mean "best of all possible worlds, so let's stop working on software."
    1. Re:How did this get modded to 5? by Paradise+Pete · · Score: 1
      in your personal, anecdotal opinion

      His opinion isn't anecdotal. He gets it first hand, through his own observation.

    2. Re:How did this get modded to 5? by nullard · · Score: 1

      Uh... this article is about the Finder. The Finder is an application, not a "desktop"

      The Finder is what provides the desktop metaphor on the Mac.

      --


      t'nera semordnilap
  20. how many times... by so1omon · · Score: 0

    how many times is this EXACT post going to be made before people stop responding to it? this is an ancient troll folks... move along.

    and how the hell did it get moderated informative?

    --
    i'm the jedidiahmarkfoster your parents warned you about
    1. Re:how many times... by tuxedobob · · Score: 1

      I don't know, but I hope I get to metamod it. It is less obvious than the other trolls/flamebaits though.

  21. Re:mac problem by luzrek · · Score: 1
    He is compairing it to a smiliarly price PC from the same point in time. That is a valid comparison. However, it is offtopic since this is supposed to be about the finder.

    I don't know why people on both sides of the MAC vs WIntel debate are always tring to compair based on what X Mac does vs what Y PC does when X Mac costs $5000 and Y PC costs $2000. MacAdict had a laughable coverstory allong the lines of "Mac beats Windows in performance" and when you read it it turned out they were compairing $7k and $10k Macs to two $2k PCs (a Dell and a Gateway). People should be saying, "I really like my computer and use it all the time, that's why it is better than yours." Then, they respect eachother's opinions since both poeple can be right. Of course both camps are wrong, GNU/Linux is the way to go 8-)

    --

    Galium Arsenide is the material of the future, and always will be.

  22. What the Finder is... by Millennium · · Score: 1

    The Finder is basically a file manager. Coming from a GNOME perspective, you could think of it as performing the same role as Nautilus, or gmc before that.

    1. Re:What the Finder is... by Captain+Rotundo · · Score: 1

      Now you see that makes sense, because being a Nautilus user, I also understand that nothing gets more discussion/flame wars than the file manager! I guess maybe thats try of every desktop ? :)

  23. Re:a better finder? by derch · · Score: 1

    Yes, it'd be nice if the Mac market was a little larger. However, the Mac market is more tightly knit and word of new, cool, and useful software travels quickly.

    When Konfabulator came out, I had three different people tell me about it. I've told several people about WeatherPop, and they've downloaded and used it. Same with NetNewsWire, Fire, and Watson. Because of the fewer Mac titles, there's less competition, too.

  24. Re:a better finder? by Anonymous Coward · · Score: 0

    Actually, a smaller market share means fewer potential competitors

    Congratulations!! You have the most idiotic post of the day! If there are 1,000 mac users and 10 mac vendors then there are 100 users per vendor. If there are 20,000 PC users and 200 PC vendors then there are 100 users per vendor. Obviously this is a simplified example but having a smaller customer base does not decrease competition.

  25. screenshots by Anonymous Coward · · Score: 0

    I tried to read the first 3 pages but there were
    no pictures. How can an article like have have no pics (at least in the first 3 pages).

  26. odd by Anonymous Coward · · Score: 0

    I got one good reason, a great reason really. How about years and years on the net and not getting owned, or even having to take any special precautions? Never having your hardware bork on you? Being able to use any decent app you download without jumping through huge hoops or having it destroy something else? Getting any peripheral that says "works with a mac" and then by golly it works.

    Besides that, that does seem like an excessively long time to copy that file. I don't ever recall anything like that happening to me. Now transferring from one machine to another with a printer cable, serial to serial, yes, 56k speed limitation, but on the hard drive? Something else is going on, and I can't tell you what it is. Maccentral forum question there for a more expert opinion wouldn't hurt for you.

    With that said, old classic mac OS you had to set your memory by hand, I have found the default limits are always too low, it's like tiny cans of soup that say "serves four", it's just not realistic. Bump up your total RAM, max it out completely, and go around and up your application memory allotments, and only set virtual to existing physical RAM plus one meg.

    Oh, the browser, don't use netscape, nyet, nein, nej, non, nope, use iCab instead, you'll be amazed how much faster it is and it uses a lot less system resources. On my much older mac than yours, only a 166 speed same 64 meg RAM, I can listen to mp3 streams (low bitrate but still live) from a net radio station and still surf adequately with iCab and using soundjam for the player, but if I switch to netscape I can't,or worse, netscape and quicktime, yech, that's a bad combo for system resource hogging. It makes that much difference picking better quality applications. And if you don't need all the features for a project that bbedit lite has, use textedit plus instead. Any time you can use a more efficient app when you are trying to multi task the better with classic OS, just is, is all.

    1. Re:odd by LeotheQuick · · Score: 1

      Man... i don't even want to here that bull****. MAN! Sorry, my mom uses Macs at her office (she's in publishing, and macs have the best software for them). She's ALWAYS complaining about the macs. I mean, let's not leave out the fact that it's just a friggin OS and it competes will allll the other OSes , and having used it, it's not BAD. I'm simply refuting your point about the stability and ease of use! Jesus christ man, i cannot list how many times i got the bomb, and i hardly ever use Macs! I'm sure it's been improved, but you CANNOT tell me macs haven't been shitty in the past. Furthermore, my mother tells me about how they're always have to upgrade and buy new software, and that they keep releasing new version after new version of the Mac OS, and what's more, Adobe Pagemaker DOESN'T WORK FOR THE OLDER VERSIONS so they have to buy a new one! How's that for jumping through hoops for software? You all know that software suffers the same problems with compatibility and upgrades on EVERY OS so don't even try to bull**** it with the Mac OS, this point is completely useless. -Erich

  27. Re:mac problem by Anonymous Coward · · Score: 0

    Yes.

    20 minutes for a 17 MB file? Duh, it's called lying.

  28. Meta data may be coming by MrMickS · · Score: 4, Interesting
    In order to support some aspects of this finder filesystem meta data must be supported in a more complete way than it is at the moment. You don't want the system to have to trawl through the tags in every MP3 file everytime it lists the folder contents (that would make it even slower :).

    The filesystems used by OS X are the same ones that have been used by OS 9 for years, with the recent addition of journalling. Apple have employed the designer of the BeOS filesysem (which is widely held up as the best example of a desktop filesystem) and is keeping everything under wraps for Panther. I would expect some developments in this area to be revealed in July.

    Once the meta data is in place, and people have moved over to the new filesystem, look for a more intelligent finder.

    --
    You may think me a tired, old, cynic. I'd have to disagree about the tired bit.
    1. Re:Meta data may be coming by tuffy · · Score: 2, Interesting
      In order to support some aspects of this finder filesystem meta data must be supported in a more complete way than it is at the moment. You don't want the system to have to trawl through the tags in every MP3 file everytime it lists the folder contents (that would make it even slower :).

      System-specific metadata should be left at the filesystem level (file permissions, ownership, etc.) but file-specific metadata shouldn't be moved out of the file. Keeping one's data files as one big block of data is a Good Thing, especially when transferring them around between systems or over the internet. Having said that, I do think that the OS should be willing and able to cache that info so that users can sort their mp3s by ID3 tags (for example) without a nasty performance hit.

      --

      Ita erat quando hic adveni.

    2. Re:Meta data may be coming by drinkypoo · · Score: 1
      I don't necessarily think that putting the data in/on the file makes any sense either, we have to deal with legacy file formats which have no provision for such tampering, some of which will not work with additional data added to the end, which is the usual suggestion in these cases. If you want to add metadata to legacy files, you can either put it in that file format's proprietary comment fields and then have your metadata handler look for it in a variety of places (this is undesirable for obvious reasons but better than the next option) or you add it to the end of the file and your C library (or similar) has to handle making it look like it hasn't been added onto.

      Rather than putting the metadata in the file (we want to be able to store arbitrary metadata for any file, right?) we should be putting it in the filesystem alongside the file. In unix terms, we should store a link to it from the superblock. As I understand, this is pretty much what ReiserFS does today, which pretty much makes it the only really conceptually modern filesystem. (I know jack about implementation issues, however, other than I personally lost data to an older version of Reiser, which doesn't necessarily say anything about the current version.)

      We're better off concentrating on solutions for how to move the metadata than trying to come up with ways to stick it on the file. Some sort of XML DTD for metadata would be a Good Thing (tm).

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Meta data may be coming by curious.corn · · Score: 3, Insightful

      Oh, and the cached metadata should hide in a dotfile right? user:group 0000 was fine for '70 textfiles but it's excuciatingly insufficient today; that's why KDE, GNOME and the other lots have resolved to dotfiles or (I'm a unix guy sorry for any mistake) forks. The natural evolution for filesystems is to extract previews, tags, extended attributes in short and index them for fast live searches like in BeOS. Man, one reason I HATE M$ is that it crushed BeOS into oblivion without doing anything remotely close in functionality; M$ groupies you don't know what chance you passed by!
      EA are the future, they're on Solaris (as far as I know, though I've never played with one; only old DIGITAL, sigh!), FreeBSD and of course LINUX. These are pretty much staple food for every system like 16 bit sound vs PC Speaker. It's time they be put to use and I think next wave of unix Desktops will do.
      Apple is only doing what's obvious (perhaps duplicating some data but who cares if my mp3 ID3 tags are indexed by the kernel). No more mailbox maintenance code, just make a MUA from a souped up live query on the email datatype tag. Cool (BeOS was there...)

      --
      Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
    4. Re:Meta data may be coming by Anonymous Coward · · Score: 0

      No way. Moving metadata out of the file and into the FS is a *great* idea. Keep the actual 'data', the stuff that is critical, in the file for transferring them around. If people keep compatibility as their number one goal, we'll never get anything new.

      One thing that I think would be awesome about arbitrary FS-level metadata is the sort of super-maildir you could do.

      #include "maildir-advantages"

      On top of all that, now that I have all my easily manipulated msgs in a dir with other arbitrary tags on them, I can have a gui mailclient that can give me shitloads of awesome views on that data. Rather than keeping messages in folders, I could assign them to multiple projects so I could view all the email on a given project at a time, quickly...so much about my email would become awesome, and while this could all be done with a straight-up database-backed mail client, fact is, I've had so many problems with fucked up disks, corrupted filesystems, corrupted binary files, moving between systems, etc., etc., with email in the past that I'd really like to keep the critical parts of the messages as a series of files in a directory.

      Please apple, give us the metadata.

    5. Re:Meta data may be coming by Draoi · · Score: 1
      Apple also spec'd the file system (HFS+) to have the ability to store metadata in a btree, similar to the catalog file. This is the 'attributes file', explained in TN1150. Right now, it's unused so I imagine there are plans for this.

      Having said that, there's no place in UFS for this sorta thing & I doubt Apple could get around it by 'bundling' (using folders) like they did the last time.

      Just guessing ...

      --
      Alison

      "It is a miracle that curiosity survives formal education." - Albert Einstein

    6. Re:Meta data may be coming by tuffy · · Score: 1
      I don't necessarily think that putting the data in/on the file makes any sense either, we have to deal with legacy file formats which have no provision for such tampering, some of which will not work with additional data added to the end, which is the usual suggestion in these cases.

      Legacy data formats are a problem when it comes to metadata, especially for non-open formats that haven't evolved much over the years (mp3's ID tags are something of a hack, for example). In those cases, the best solutions is probably some sort of wrapper file format around the original data - a bit like how ogg is a wrapper for raw vorbis audio files. But, that would require a change in the way the legacy format is handled. In those cases, there probably isn't a perfect solution :(

      Rather than putting the metadata in the file (we want to be able to store arbitrary metadata for any file, right?) we should be putting it in the filesystem alongside the file.

      The problem is that storing the metadata seperately is inherently fragile and will need to be standardized *everywhere* in order for it to work at all. Otherwise, all the precious metadata I've assigned to file X would be lost if system Foo is unable to extract it from system Bar's archive files (which would contain such data). Plus, even our archive formats would have to be adjusted to handle the switch.

      So of the evils of where to store metadata, I think keeping it in the file but having the system able to extract/cache it is the lesser of the two.

      --

      Ita erat quando hic adveni.

    7. Re:Meta data may be coming by tuffy · · Score: 1
      No way. Moving metadata out of the file and into the FS is a *great* idea. Keep the actual 'data', the stuff that is critical, in the file for transferring them around. If people keep compatibility as their number one goal, we'll never get anything new.

      Compatibility is important, but avoiding lossage is the most important thing of all when storing data. Imagine, as an example, I store the album titles of all my ripped songs as filesystem-specific metadata rather than in the files themselves. If, at a later date, I transfer them to another system without support for that metadata, I will lose that data and won't get it back - a bit like losing one's file ownership by untarring them on Windows. By keeping the metadata in the file, even if the OS/player/viewer/whatever doesn't support it, I won't lose that data simply by moving it between various systems with varying levels of compatibility.

      --

      Ita erat quando hic adveni.

    8. Re:Meta data may be coming by spitzak · · Score: 1
      However in *most* cases the metadata can be extracted from the file. I recommend it be put into comment fields whenever possible. Otherwise tack it on the end or wrap the file if possible. Notice also that some metadata (preview images, cache) by *definition* are extracted from the file!

      "extended attributes" should be used for a "cache" of this extracted data, but a program should recreate it if at all possible from the data.

      The problem with attributes is that they cannot be read/written by normal tools and are thus often lost when files are transferred or edited. When they are not lost you require seperate tools to alter them. It also appears that for best performance they should not be stored in the same filesystem, for instance you may prefer the "attributes" of web pages (ie the cached copy, things like "favicons", etc) to be stored on your machine rather than on the web server.

      For these reasons I strongly recommend that all "attributes" be considered more like a cache of extracted data. It would still be very useful for there to be low-level support of this in the system, however. Since user-level programs would set the attributes you could set them arbitrary, but the programs should be designed with caching and extracting them, rather than generating them.

    9. Re:Meta data may be coming by 3.1415926535 · · Score: 1

      Yeah, because we all know how easily files with resource forks could be transferred across the Internet in Mac OS

    10. Re:Meta data may be coming by Anonymous Coward · · Score: 0

      A/C because I can't be bothered to login..

      I agree that metadata should be kept *with* the file.

      MacOS (any version) does this quite intelligently already, with resource forks or .DS_Store files. Globbing a load of data into a single file is bad for resiliency and portability.

      Remember that compatibility only has to be enforced when a file is actually moved to the other system. You can keep the file in any form you want with any data attached to it you like, so long as the OS that's accessing it has the APIs to give apps the data they expect.

      It's only when the file's accessed on a foreign system, or moved to a filesystem with different needs that 'compatibility' becomes an issue.

      For instance, OS X handles file extensions excellently. It creates them, but when it displays the file extension, it treats is as part of the name.

      For example, given a file called FOO.JPG, I can rename it and delete the .JPG

      However, on the filesystem, the extension is still present. If I thenr rename FOO to FOO.GIF, I'm warned that the file already has a JPG filetype, and do I really want to mangle it?

      Windows filesharing clients never realise what's going on. I can remove the extensions for any file I like, but the Win clients still see the proper type.

      OS X, for filetypes, already embraces this idea of "Let the user do what they like, without breaking things for apps or other systems."

    11. Re:Meta data may be coming by Phroggy · · Score: 1

      Having said that, there's no place in UFS for this sorta thing & I doubt Apple could get around it by 'bundling' (using folders) like they did the last time.

      What's in .DS_Store?

      Putting metadata in hidden files wouldn't be worse than putting whatever's in .DS_Store in hidden files, I would think.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    12. Re:Meta data may be coming by Anonymous Coward · · Score: 0

      Hello? Forks? This is the exact purpose for which they were created, folks.

      Just stick the metadata in a fork. NTFS supports forks. Mac supports forks. Only problem is, Unix doesn't.

    13. Re:Meta data may be coming by Draoi · · Score: 1
      What's in .DS_Store?

      Information that the Finder uses to display the directory contents; geometry, mode, colours, etc ..

      Putting metadata in hidden files wouldn't be worse than putting whatever's in .DS_Store in hidden files, I would think.

      Only you'd need a hidden file for every non-hidden one which contained metadata. Major waste .. .DS_Store is already a hidden file. Fortunately, there's only (up to) one for each directory. You should look through TN 1150 and see what the Attributes File's all about ..

      --
      Alison

      "It is a miracle that curiosity survives formal education." - Albert Einstein

    14. Re:Meta data may be coming by drinkypoo · · Score: 1

      It's true that you have to agree on how you transfer the metadata, this is why I stress the important of same. XML seems an obvious choice for the format because it lends itself to forward and backward compatibility, it's easy to parse, and it's a reasonable non-endian-specific way to store information.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  29. He's dead on. by BoomerSooner · · Score: 1, Funny

    Everything the author said would make life using a Mac easier, more productive and significantly more intuitive.

    Watch out, someone might be moving your cheese.

  30. Magazine year by Anonymous Coward · · Score: 0

    That article was from the summer of 1997.

  31. Solution is a more flexible "finder" api by binaryDigit · · Score: 2, Interesting

    Perhaps OSX can take a page from the X world and to think of the interface more as a component and less as an integral part of the OS (skin the OS if you will). It would be better than the X world currently is since the "default" Apple interface would rule since most people wouldn't bother to make any substantial changes. But for those "power" users, they can either tweak it themselves or use someone elses "video editing power user interface".

    The difference between this and what some people already offer would be on Apple's end. Trying to make a very good desktop alternative is often difficult because it becomes too much of a monumental task to become a true replacement. And if your app just sits on top of the original gui, often times there are many things you either can't do, or can do but in a kludgey way. If the powers that be at Apple sat down and thought of a way to provide hooks into the gui (as well as the most important thing, to make sure that functionality is separated from the gui), then doing these types of things could be much simpler as well as providing a viable market for alternative interfaces.

    1. Re:Solution is a more flexible "finder" api by IamTheRealMike · · Score: 1
      Perhaps OSX can take a page from the X world and to think of the interface more as a component and less as an integral part of the OS (skin the OS if you will).

      I think you're a bit confused, X has nothing to do with component embedding (or very little). Windows for instance is the master of this, has been for years, no X there. I think I understand what you're talking about though.

      If the powers that be at Apple sat down and thought of a way to provide hooks into the gui (as well as the most important thing, to make sure that functionality is separated from the gui), then doing these types of things could be much simpler as well as providing a viable market for alternative interfaces.

      I would guess the reason Apple don't do this is because:

      a) They don't want people to use alternative interfaces (branding). They will anyway, that's just the nature of users, but Apple don't want to go out of their way to make it easy for people.

      b) Component embedding using something like Bonobo/ActiveX/KParts is added overhead, and as you may have noticed, people aren't too impressed with the speed of MacOS anyway. That doesn't mean component models HAVE to be slow, they don't, but they add extra complexity for little user visible gain. One of the reasons Nautilus and Konqueror use the navigational model is AFAIK because window creation times are too high, partly because of their use of component tech. ROX on the other hand, which does not, opens new windows nearly instantly, but sacrifices some flexibility in order to do so (imo).

      c) MacOS X isn't too hot on component technologies. Apple used to have OpenDoc which was the closest equivalent to ActiveX/Bonobo/KParts, but they dropped it. I think there's something called distributed objects, inherited from NeXTStep, but as you might expect that's rather tied into Cocoa as far as I know, and I think it only does object remoting rather than GUI merging, structured storage and all the other gizmos B/Ax/KP bring to the party.

      Basically, I wouldn't expect to see that happen in MacOS X any time soon. Although a cool demonstration of the platforms component tech, the true value of those features are debatable anyway, see the recent AbiWord in Nautilus thread for a discussion of the pros/cons of being able to treat the filing system as a set of embeddable components.

    2. Re:Solution is a more flexible "finder" api by usotsuki · · Score: 1

      ??? Apple themselves supports the porting of XFree86 (!) to OSX...

      -uso.
      My next machine will be a BSD box.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    3. Re:Solution is a more flexible "finder" api by IamTheRealMike · · Score: 1

      X/XFree is a graphics abstraction layer, not a component embedding model. They do completely different things.

  32. 8600/300 was real, here's info by Anonymous Coward · · Score: 0
    8600/300 info. Guess what, it's a real machine and it had a 300mhz 604e - which was *damn* fast for its time.

    All 8600-class machines had 2 SCSI buses: a 5MB/sec external bus and a 10MB/sec internal bus. The same holds true for the 7x00-class machines, and I think the 9x00s too.

    Also, notice that the OP said that his PPro 200 was faster. That's *also* 8 years old or whatever. It's not like he's comparing the 8600 to an Athlon XP w/ SATA.

    Even though you were completely wrong about everything you said, we appreciate the effort. Thanks for playin.

    Love,
    Slashdot

  33. Best by comparison by w3weasel · · Score: 1

    Isn't it swell that we can all imagine a perfect world? By COMPARISON, OS X has (IMHO) the quickest, simplest, and most elegant 'finder' [aka GUI] available today. All systems out there could stand some improvement, and while criticism of the sort can be constructive, wouldn't it be better to illustrate improvements rather than point out flaws?

    --

    Just as irrigation is the lifeblood of the Southwest, lifeblood is the soup of cannibals. -- Jack Handy

    1. Re:Best by comparison by iocat · · Score: 1
      Quickest? Quickest? Are you high? I am using, right now, a 1ghz Athlon from early 2001, and Windows 98. I don't maintain or clean my system regularly -- I think my 30GB drive has like 2GB free, and there are files scattered everywhere. I've never de-fragmented the drive. (yeah, yeah, I know, I'm sloppy.)

      Yet, when I click on My Documents folder, with 1200+ items in it, it opens instantly. There is no perceived pause at all. When I click on the Word icon, Word opens in well under 2 seconds.

      In short, the "Finder" on my PC is hella fast. On the fastest, most expensive and memory laden Mac they have at the Apple store, which features pretty stipped down content, folders take forever to open in my perception. Way longer then with OS9 on my G3 at home, and way longer than my PC at work. Applications (well, Word and Photoshop, which I tested opening) load faster than on the G3, but still way, way, slower than on my PC.

      I really, really wanted to buy a new Mac, but given the amount of file and application switching I do on a daily basis, the thing is just way to gd slow to justify a purchase. Maybe if I ran difficulty Photoshop filters all day it would be ok, but I don't. And what is slowing things down? Stupid animations you can't turn off? The animating dock? Poorly executed programs? I have no clue, but there's no way I'm dropping $2000+ on a computer that goes (in my perception) slower than a two year old PC.

      Note: I have to say the people at the Apple store in Emeryville, CA, were super friendly, super well informed about their product, and really took some time with me to help optimize the OS 10.2 finder for speed (turning off doc animations, using the least annoying folder animation, letting the folders cache, etc.). I really appreciated that level of customer service; but until I don't consciously perceive the Macintosh as "going slow" in the Finder, I won't be buying one.

      --

      Dude, I think I can see my house from here.

  34. Re:mac problem by Otter · · Score: 1
    You know, the OS X Finder can be set to give the Windows Explorer-like behavior you want. In fact, isn't that the default option, as opposed to the multicolumn and OS9-like behaviors?

    About the sluggishness of the screen redraws and interctivity, I agree.

  35. BeOS wouldn't work by Anonymous Coward · · Score: 0

    BeOS didn't support the 604 series of CPUs. It only ran on the 603s.

    1. Re:BeOS wouldn't work by piggy · · Score: 1

      That's not true. I used BeOS on my 604e200 Mac clone. And it was significantly faster than MacOS on the same Mac -- more stable too.

    2. Re:BeOS wouldn't work by objekt · · Score: 1

      Here's a list of compatible BeOS systems including many 604-based machines.

      Unfortunately it looks like BeOS on an 8600 is a bit iffy, due to logic board idiosyncracies.

      --
      -- Boycott Shell
  36. But nautilus... by Frequanaut · · Score: 1


    Did anyone read the article and think, that with the exception of saved searches and popup folders, that they're describing nautilus?

    Really, the latest from debian unstable is very very good. very good.

    1. Re:But nautilus... by Anonymous Coward · · Score: 0

      Euhm, read the article again.. Nautilus is a browser with a one to many relation to files, and the author doesn't want that.

  37. Re:mac problem by Capt.+Zap · · Score: 1

    Wow.. Still there? why do ou always post this mindless flame every time an apple story gets posted?

  38. Re:mac problem by Anonymous Coward · · Score: 0

    I think i`ll have to point out that my old amiga a1500 could transfer said 17meg file with no problems ,wut your saying at 16mhz 68000? Yup i`ll say,and if memory servs thats pre 1995.

  39. Metadata benefits by Shrac · · Score: 1

    I for one understand it, and I can't wait until a version of NTFS comes out that steals the idea. :) Well, either that or an x86 port of Jaguar.

    1. Re:Metadata benefits by GigsVT · · Score: 3, Interesting

      NTFS already has it, no one uses it because hidden metadata is a stupid idea that breaks all the time. As someone who works with Mac OS 9 clients and Unix servers, I can tell you it's a lame and unnecessary hack, designed to compensate for incompetant users.

      Do a google search for "alternate data streams NTFS"

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:Metadata benefits by Shrac · · Score: 1

      Interesting; thanks for the info. Unless I'm mistaken though, there's no built-in way to launch files in different apps based on the extended file properties.

      So what do you consider to be an alternative? Up until my first install of FreeBSD a few days ago I'd always used MS products, so I'm not really aware of how such things work in *nix. I just know that almost anything would be better than how Windows handles it right now.

    3. Re:Metadata benefits by Trolling4Dollars · · Score: 1

      I can tell you it's a lame and unnecessary hack, designed to compensate for incompetant users.

      Hmmm... don't you think that's who we should be writing programming for? I wouldn't put it in those unkind terms of course. I tend to refer to them as "Joe Average" since that's who you are really talking about. Metadata is not a lame and unnecessary hack for the guy who can't tell the difference between a GIF a JPEG and an MPEG.

    4. Re:Metadata benefits by rifter · · Score: 2, Funny

      Oh come now, it is intuitively obvious to anyone who is smart enough to deserve the breath of life by reading the raw file data on their glass tty what kind of file a given file is. ;)

    5. Re:Metadata benefits by Trolling4Dollars · · Score: 1

      Hehehe... or they can always run the 'file' command in Linux to tell them what kind of file it is....

    6. Re:Metadata benefits by rifter · · Score: 2, Funny

      This is true. Of course they still have to have the right magic numbers in /usr/share/misc/magic ;).

    7. Re:Metadata benefits by Oculus+Habent · · Score: 2, Informative

      Mac OS X opens the program in it's default application - determined by metadata if there is any, determined by the extension if there isn't. You can bring up the Contextual Menu and choose from a list of other programs registered to handle that file type, if you so choose.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    8. Re:Metadata benefits by Oculus+Habent · · Score: 1

      It was a great departure from the .xyz file extensions that DOS used, which allowed for only one application to control all files of a certain type. The inability to easily switch a file's "creator" value was annoying, though there were several programs that would do it for you. There was the awesome capability of the Finder that allowed you to drag a file onto a application, which would become highlighted if it supported the file type.

      When PC interoperability became an issue, there was the PC Exchange (later File Exchange) Control Panel that came with a large list of .xyz to type/creator combinations.

      If someone had come up with this concept in UNIX it would undoubtably be touted as one of the greatest features of all time. Indeed it was such a useful, natural design that BeOS included metadata in the BFS, which is an awesome filing system by every report I've ever heard.

      The only qualm I ever had with the Type and Creator system was the inability to switch easily, something remedied with a small app, or 15 seconds in ResEdit.

      --
      That what was all this school was for... to teach us how to solve our own problems. -- janeowit
    9. Re:Metadata benefits by andrewski · · Score: 1

      The correct way in Unix of including file-type metadata is to include a 'magic number' at the beginning of the file. Unfortunately, few programs create datafiles with this magic number, and few programs recognize it.

    10. Re:Metadata benefits by GigsVT · · Score: 1

      I don't think you understand magic number correctly. The magic number is part of the file format itself. For example, a valid JPEG will always start out with the same bytes "ÿØÿà^@^PJFIF". Most file format specs include a part at the beginning that identify the file to consumer applications.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    11. Re:Metadata benefits by andrewski · · Score: 1

      Most files on unix are plain text or binary. Many binary files lack magic numbers. Most text files lack it too.

      File formats created recently often lack magic numbers, as do formats created by a vendor and not standardized and documented.

    12. Re:Metadata benefits by dalamcd · · Score: 1
      Or Snitch, which expands the Get Info window and puts type and creator in there. I use OS 9 maybe twice a year for old games that I don't want to play in Classic, and I still have Snitch installed.

      dalamcd

      --
      moer liek CELtroid prime!!@1!
    13. Re:Metadata benefits by GigsVT · · Score: 1

      How could a text file ever have one?

      What binary files lack one? I really can't think of one offhand that doesn't have one.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
  40. You're joking, right? by wfolta · · Score: 1

    In the Finder, press CMD-K and up pops a nice network mounting interface that shows local SMB as well as Apple servers. Way simpler than Chooser. And it actually makes sense, unlike the overloaded Chooser which was meant to choose printers back when people had, say, two choices.

  41. Re:if nothing else, by jgerman · · Score: 1

    Funny, Bill G doesn't seem to have wiped the floor with Unix from my perspective. I haven't used Windows for anything but games since at least 1995. Why? Because *nicies (*nixes) are musch more usable.

    --
    I'm the big fish in the big pond bitch.
  42. If Ars Technica is so concerned about usability by T1girl · · Score: 5, Insightful

    ...why is this article in white print on a black background? ... There's a reason books and newspapers are printed in black print on a white background: IT'S EASIER TO READ.

    A person who can't hold a job can always make a living as a career coach.

    1. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 4, Interesting

      It's easier to read because paper's natural state is white. Subtracting light/color gives you the text, images, whatever. A CRT's natural state is black, so you *add* light to get text, images, etc. Using white background with black text on a screen is equivalent to printing a page solid black and leaving blank spots for the text. aka - not natural. I don't care if most of the web has adopted black on white for the mainstream design - it hurts my eyes. A medium's natural state is the easiest to read.

    2. Re:If Ars Technica is so concerned about usability by Pig+Hogger · · Score: 1
      ...why is this article in white print on a black background? ... There's a reason books and newspapers are printed in black print on a white background: IT'S EASIER TO READ.
      Amen, brother.

      Fortunately, I use Opera, which has a nifty "remove fancy-schmancy" formatting and presents everything in an eminently readable black-on-white (or whatever you configure it to be) font.

    3. Re:If Ars Technica is so concerned about usability by potaz · · Score: 2, Interesting
      I've heard just the opposite. In fact, I knew a guy who had problems reading, and the only way he could understand text at a regular level was with black text on a white background.

      The only reason black-on-white seems natural is when we started printing, it cost money to make a page full of black ink, while a white page was free.

      For web pages, it makes sense to have white text on a black background - it is easier to read, especially if you're on a CRT... at least with all that black there it's not like you're trying to read off a lightbulb.

    4. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      Paper's "natural" state? CRT's "natural" state? Please provide the definition of a medium's natural state, remembering that tree pulp isn't white and the glass on my CRT is clear.

    5. Re:If Ars Technica is so concerned about usability by Zoop · · Score: 2, Interesting

      Actually one usability found that black or brown text (I forget) against a light-pink background was easiest on CRTs.

      Gag me with a spoon, but it's more readable once you get your lunch wiped off it.

      All studies have found that dark text against a plain light background is easier than the opposite on CRTs with reasonable refresh rates.

    6. Re:If Ars Technica is so concerned about usability by usotsuki · · Score: 1

      I agree. In fact, I would venture to say that 75% white on black, or 75% green on black, or 75% brown on black are the best colors for the screen to have.

      Black on white gives me a migraine.

      -uso.
      <BODY BGCOLOR=#000000 TEXT=#FFFFFF ...

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    7. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      Actually white on black is WAY easier to read. Used emacs lately?
      Newspapers print black on white because it's far cheaper to use less die/ink.

    8. Re:If Ars Technica is so concerned about usability by Laurion · · Score: 1

      Also note that it's far cheaper to print the letters than it is to print everything but the letters.

      --
      "Is this not a rare fellow, my lord? He's as good at any thing, and yet a fool." -from "As You Like It", Act 5,
    9. Re:If Ars Technica is so concerned about usability by poot_rootbeer · · Score: 3, Insightful

      "There's a reason books and newspapers are printed in black print on a white background: THE LESS BLACK ON A PAGE, THE LESS INK REQUIRED AND THUS THE CHEAPER IT IS TO PRINT."

      Fixed your post.

    10. Re:If Ars Technica is so concerned about usability by Chris+Marlowe · · Score: 1
      It's easier to read because paper's natural state is white. Subtracting light/color gives you the text, images, whatever. A CRT's natural state is black, so you *add* light to get text, images, etc. Using white background with black text on a screen is equivalent to printing a page solid black and leaving blank spots for the text. aka - not natural. I don't care if most of the web has adopted black on white for the mainstream design - it hurts my eyes. A medium's natural state is the easiest to read.

      By that logic, an LCD's "natural" state is white, the color of the backlight, with the pixels filtered by liquid-crystal cells. And the same black-on-white page should be much more readable on an LCD than on the CRT or plasma-discharge display right next to it.

      I am prepared to doubt the living shit out of this.

      Maybe you're just used to crappy CRTs? Try turning down the brightness control.

    11. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      That was exactly my reaction. I despise sites that persist in using anything but black text on a white background because it is sacrifices readability for the sake of (being kind here) "style".

      I also was bothered that they only offer a printer-friendly version (assuming the PDF version isn't white text on a black background) if you are a paid "Premiere member". While that is their right I suppose, it is another indicator that their reader's priorities fall beneath their own.

    12. Re:If Ars Technica is so concerned about usability by Christianfreak · · Score: 1, Informative

      BS. The black when your screen is on is created the same way the white is when its on. There is no 'natural color' for a CRT unless its off and you can't have portions of the screen off and portions on.

    13. Re:If Ars Technica is so concerned about usability by Korth · · Score: 1

      It depends.
      See the following link:
      http://www.ergogero.com/FAQ/Part6/cfaqPart6 .html#p 6.2

    14. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      Actually, it has nothing to do with being easier to read. Ink is expensive and paper is already light in hue. Easy reading is simply a by-product.

    15. Re:If Ars Technica is so concerned about usability by Gropo · · Score: 2, Informative

      Do what I do:

      System Preferences/Universal Access/Seeing - "Switch to Black on White"

      Then, when you need to look at a screenshot/diagram, switch back. Works for me :P

      --
      I hate Grammar Nazi's
    16. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      Hmm, no. If we wanted we could use black paper and white ink.

    17. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      ...why is this article in white print on a black background? ... There's a reason books and newspapers are printed in black print on a white background: IT'S EASIER TO READ.

      Ok, everyone who's saying that paper is black on white because it's cheaper is WRONG. The "natural state" argument is similarly misguided.

      The key is this: monitors glow, paper does not. (and, at least in the case of my crappy monitor, monitors flash)

      Reflective media should use black on white. (brightly) Emittive media should use white on black because it reduces the eyestrain caused by staring into a light source.

    18. Re:If Ars Technica is so concerned about usability by kliklik · · Score: 1

      Simply use some of these bookmarklets to zap all anoying colors/embeds/effects.

      --
      guru in training
    19. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      This is similarly wrong, emittive media (I think you've managed to misspell a word that doesn't even exist) do not cause eyestrain because you are staring into a light source. Otherwise, everyone with a TV set would suffer from raging headaches.

    20. Re:If Ars Technica is so concerned about usability by 3.1415926535 · · Score: 1

      the glass on my CRT is clear.

      Yes, but the mask behind it is not - it's naturally black. In this case I think what the original poster is complaining about is that the monitor is actively glowing, whereas the paper is just reflecting the room light. That means that if the monitor is not properly adjusted for the surrounding light levels, it will be difficult to read the small patches of darkness amid a sea of glowing white.

    21. Re:If Ars Technica is so concerned about usability by TheOneEyedMan · · Score: 1

      Print is mostly white with black text because it was wasteful to use all that ink to print pages in black minus the white for text. It would also be much more difficult to make neat, movable type prints because you'd need to seemlessly join all the blocks and have flat blocks for the empty areas. That makes it more likely to bad output. Ever seen the banding on an all black page printed on a laser printer? Blueprints are white test on blue paper because the process is easier to do that way.
      Maybe it isn't a good idea to print light on dark, but the blooberg data terminals are light on dark too, and they at used to claim (and may still) that this was too make it easier to stare at all day long. Recall that paper is front lit and CRTs are back lit so their optimal usage colors may differ.

      --
      Reality is that which refuses to go away when I stop believing in it. --Phillip K. Dick (remove SPAM to email)
    22. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      No, no, no. You're all wrong. The _technical_ reason book and newspapers are printed in black is due to the fact that light type on a dark background tends to 'fill in' -- ie, the fine serifs and counters in the type disappear.

      For an example of this, print a page of white, 12 point type against a black background on the nearest inkjet. That should adequately reproduce the results you'd get from a CMYK press.

      Now, useability-wise, I'd say you've got the right idea.

    23. Re:If Ars Technica is so concerned about usability by 3.1415926535 · · Score: 4, Interesting

      That's completely, 100% false. Look closely at a monitor that's on but black with a magnifying glass some time, and compare it to the same monitor that's off. You'll notice that when it's on, the phospohors are glowing only because of leakage from the electron gun, and not because it's somehow actively painting black onto the screen.

      There might be some useful information here.

    24. Re:If Ars Technica is so concerned about usability by 3.1415926535 · · Score: 1

      Making a white page requires running the pulp through a bit of bleach. Bleach is easy (i.e. cheap) to make. Making a black page, on the other hand, requires running the pulp through a bunch of black ink, which is more expensive to make.

    25. Re:If Ars Technica is so concerned about usability by cpt+kangarooski · · Score: 1

      I'd say that it dates to when people started to use paper. Even writing by hand on paper tends to encourage black ink on the light background. Before that writing was carved into things -- stone, clay, sand, etc.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    26. Re:If Ars Technica is so concerned about usability by alernon · · Score: 1

      This is totally correct. The web centered on white backgrounds with black text in the mid to late 90s because when you tried to print out white text from early browsers, nothing printed. There are several workarounds to this now, but black-on-white is pretty much the standard now.

    27. Re:If Ars Technica is so concerned about usability by Alrescha · · Score: 2, Interesting

      "It's easier to read because paper's natural state is white."

      No it isn't. Paper is made out of wood. It's 'natural' color is a nasty dirty brown. We bleach the hell out of it to make it white.

      off topic:

      when I was in college, my professor was highlighting the volume of nasty chemicals used to process the things in our homes. One example was this: If you take a roll of toilet paper, soak it overnight in a jar of water, then drink the water, it'll probably kill you. Kids, don't try this at home.

      A.

      --
      ...bringing you cynical quips since 1998
    28. Re:If Ars Technica is so concerned about usability by angle_slam · · Score: 1
      For web pages, it makes sense to have white text on a black background - it is easier to read, especially if you're on a CRT... at least with all that black there it's not like you're trying to read off a lightbulb.

      At home, I have no problem reading white text on a black background. But that's because I have a properly calibrated monitor at home. At the office, I have a monitor that basically is busted: it doesn't display black correctly. There are many sites available that will show you a strip of boxes from pure white to pure black. I found one with 17 steps. At home, I can see the difference in every step. At work, the last 6 steps look completely black to me. I cannot fix that problem. Thus, it is very difficult to read white text on a black background. Considering the fact that a lot of companies cheap out when buying monitors, this may be a problem prevalent in offices. I think you're a lot safe putting black text on a white background.

    29. Re:If Ars Technica is so concerned about usability by tgibbs · · Score: 1

      The key issue is that a sheet of paper does not generate light, so the issue of glare from an excessive expansive of white does not occur. If it is too bright, you automatically and instantly adjust it by changing the angle to the light source. That sort of instantaneous real time conrol of brightness is not available with a monitor.

      In general, a white background works best on a monitor, because a lot of what we do still eventually ends up on paper, and we want to be aware of how it will look. But for material that is intended to be read online, I find white on black easier to read.

    30. Re:If Ars Technica is so concerned about usability by TomorrowPlusX · · Score: 1

      Maybe that works for your bizarro-world eyeballs, but for the rest of humanity, and believe me (I work as a graphic designer, and have an education in art and graphic design): dark text on light/medium tones is demonstrably superior and overwhelmingly preferred for reading large sets of text. This does not include things like logos, business cards, TV adverts, etc. I'm talking about body text for essays, articles, and so on.

      Feel free to say it's all a matter of opinion -- of course, it is. Some people like all sorts of naughty, painful things the rest of humanity would prefer to avoid.

      The fact is, it's hard to read white on black for the *vast* majority of people. Personally, it gave me a headache and blurred vision.

      And, what basis do you have to say "A medium's natural state is the easiest to read." That's the most preposterous thing I've ever heard.

      --

      lorem ipsum, dolor sit amet
    31. Re:If Ars Technica is so concerned about usability by PocketAces · · Score: 1

      A pet peeve of mine is web sites (like AT) which force the font size. I'm (fortunately) not visually challenged, but 10 points is way too small for me. Thank goodness for Mozilla's "minimum size" feature.

    32. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      People don't read large bodies of text on TV sets.

    33. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      Maybe you're just used to crappy CRTs? Try turning down the brightness control.

      Turning down the brightness control effectively gives you black on grey instead of black on white.

      White is harsh and nasty as a background color on CRTs, as it represents unfiltered light at full strength. Your suggestion to turn the brightness down gives this away.

      Frankly, I'm surprised the original post got modded to 5 for such an uninsightful comment. CRTs are different to text on paper, your eyes are receiving light in an entirely different way.

    34. Re:If Ars Technica is so concerned about usability by Anonymous Coward · · Score: 0

      Opera's 'magnification' level option works better, IMHO.

      Also, Opera will let you specify your own CSS file if you like, and view each and every webpage in your own preferred background and text colours/sizes. Opera is incredibly customizable - at this stage, much more so than Moz (though I have no doubt Moz will catch up - they just need to use, and steal more ideas from, Opera).

    35. Re:If Ars Technica is so concerned about usability by bjb · · Score: 1
      ...why is this article in white print on a black background? ... There's a reason books and newspapers are printed in black print on a white background: IT'S EASIER TO READ.

      C'mon, its just as easy to read as white on black. You're talking about your personal preference, or what you're used to.

      The reason why they went black on white with the original GUIs was because they wanted to have the WYSIWYG concept of "this is your sheet of paper on which you're writing/drawing/scribbling/etc".

      Personally, while I appreciate the concept, I find it is one of the large causes of bad eyesight among computer users. Most people crank their monitor brightness. Now, add a white/bright background in which you're straining to read little black letters. I think this is just as wise as trying to read the wattage of a lightbulb while its on.

      If you care, you can see my tips for saving your eyesight as a computer user. I've been using computers for over 20 years and I still have the same 15/20 vision I've had since I was a child.

      --
      Never hit your grandmother with a shovel, for it leaves a bad impression on her mind...
    36. Re:If Ars Technica is so concerned about usability by Yet+Another+Smith · · Score: 1

      Well... Not really. The guy might not be 100% right, but he's definitely not 100% false. The electron gun paints every single pixel on the screen. When a pixel is white, the electron gun (cathode ray, for the vocablularily strict) hits them at full power on all phosfors. For a black pixel, it hits it at minimum power on all phosfors. However, even a black screen emits light. If you have a computer room that's dark enough, you can cover up all the LEDs and so forth, set the screen to be totally black (how you do this on different OSes will vary). Even if your entire screen is 000000, you'll still be able to see it in a dark room. The reason? Its emitting light because the phosfors are getting hit by the electron gun at minimum power.

      I know for TVs there are varying levels of black. Better TVs will allow for their black to be more black than cheap TVs (How much more black could it be? The answer is none... more black).

      Anyway, my point is that the electron gun does paint every pixel at every screen pass, even the black ones. Its just at its minimum power setting for the black.

      --
      if ($it != $onething) {$it = $another;}
    37. Re:If Ars Technica is so concerned about usability by fractaltiger · · Score: 1

      Yup... here is an obligatory inclusion of
      my default stylesheet. Console Green on black, with gray links, cool highlit hovering and strikethrough for visited links. It's pretty nifty, give it a try. Sorry, Netscape flavors don't seem to support it, but since people here DO use IE and Galeon and Opera, chances are you can try it for free. Drop me a line at my journal!

      Sorry if The lameness filter made me smush some stuff together... You may format and modify this at will...

      BODY {
      /* line-height: 105%; */
      background: black;
      color: #00FF00;
      }

      H1, H2, H3, H4, H5, H6, P, UL, OL, DIR, MENU, DIV,
      DT, DD, ADDRESS, BLOCKQUOTE, PRE, BR, HR, FORM, DL {
      color: #00FF00 !important;
      background-color: #000000;
      }

      B, STRONG, I, EM, CITE, VAR, TT, CODE, KBD, SAMP,
      SPAN {
      color: #00FF00;
      background-color: #000000;
      }
      IMG { color: #00FF00; background-color: #222222 }
      LI { display: list-item }
      B, STRONG { font-weight: bolder } /* relative to the parent */
      I, CITE, EM, VAR, ADDRESS, BLOCKQUOTE { font-style: italic }
      PRE, TT, CODE, KBD, SAMP { font-family: monospace }
      PRE { white-space: pre }

      ADDRESS { margin-left: 2em } BLOCKQUOTE { marg {
      display: block } }
      H1 { font-size: xx-large } H2 { font-size: x-large } H3 { font-size: large } H4 { font-size: normal } H5 { font-size: small} H6 { font-size: x-small}

      UL, DIR { list-style: disc } OL { list-style: decimal }
      MENU { margin: 0 } /* tight formatting */
      DT { margin-bottom: 0 } DD { margin-top: 0; margin-left: 3em }

      HR { border-top: solid } /* 'border-bottom' could also have been used */

      A B {color: red; text-decoration: underline;}
      A:hover B { background: red; color: white; text-decoration: overline}

      A:link { color: #B0C6E2 } /* unvisited link */
      A:visited { color: #8090AF; text-decoration: line-through } /* visited links */
      A:active { color: gray } /* active links */
      A:visited:hover { text-decoration: overline; } /* strikethrough's reaction to hovering */
      A:hover {color: white; text-decoration: underline; background: #01809F; font-style: bold}

      /* setting the anchor border around IMG elements
      requires contextual selectors */

      A:link IMG { border: 1px solid blue }
      A:visited IMG { border: 1px solid red }
      A:active IMG { border: 1px solid lime }
      A:hover IMG {border: 1px solid white }
      table {
      color: #00FF00; background-color: black;
      }

      TD { border-bottom: 1px dotted Scrollbar}

      --
      "Wireless : LAN :: Laptop : Desktop"
  43. Expectations by Shrac · · Score: 1

    I think it is definitely because of the fact that Apple is known for/touts the UI in its products. More specifically though, people pay a high premium to get the Mac UI, and are therefore less forgiving of its faults.

    1. Re:Expectations by feldsteins · · Score: 1

      I buy that totally. I do wish, however, that the steady stream of criticism from sources like Ars would clearly indicate that this is where it's coming from, rather than letting the reader suppose that it is meant as a comparative criticism against Windows' and/or Linux's UI.

      --
      You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
    2. Re:Expectations by rifter · · Score: 1

      I don't know how they can suppose that unless they fail to read the article. I mean the articles explicitly compare Mac OS through 9 to Mac OS X. They do not say anything about Linux or Windows being better. That would be silly ;).

  44. One thing I really agree on... by Jon+Abbott · · Score: 4, Interesting

    OS X should handle the iPhoto Library folder (where all iPhoto JPEG images are stored) like it handles Application bundles -- instead of showing the directory structure uncut and raw, it should display the photos in an easily-navigable format. The "Live Search" feature could be useful in this regard, as OS X could have a live search folder that contains all iPhoto pictures, or possibly variations like "all photos within the last month" or "all photos within the last year". This would make it easier to peruse one's photo collection, as you wouldn't need to fire up iPhoto every time you just wanted to look at your photos. It would also make it easier to have your rotating Desktop backgrounds show your entire photo collection.

    I know that the "all photos in one folder" feature could be accomplished at the command prompt by running "find ~/Pictures/iPhoto\ Library/* -type f -print0 | xargs -0i ln -s {} destination ", but it would be nice to have it automatically done for you by the Finder.

    1. Re:One thing I really agree on... by Rellik66 · · Score: 1

      I'm agahst! thats a Feature that was implemented into Windows XP. What! did Microsoft actually beat Apple to the punch for once, or did they rip it from somewhere else other than Apple?

      --

      Too many zeros, not enough ones

    2. Re:One thing I really agree on... by Jon+Abbott · · Score: 1

      I'm unfamiliar with XP -- does it offer the "live search" capabilities I mentioned, or just the thumbnail browsing? OS X can already do thumbnail browsing, depending on what program edited the image.

  45. Re:That twit by Anonymous Coward · · Score: 0

    I'm still waiting for how a WAR IN THE MIDDLE EAST promotes peace in the Middle East.

  46. Vestigial Finder Remnants by shmert · · Score: 1

    Honestly, I'm amazed by how little I even use the Finder in OS X. I use LaunchBar to launch all my applications (and about a million other things). I use the terminal or Project Builder to edit single text files. iPhoto to organize my pictures. iTunes to search through MP3s. locate to, well, find things. When I'm tabbing around between apps, Finder is usually one of the last things on the list. The main time I seem to use the Finder is to manage my downloaded files, or drag some new app from a disk image into the Applications folder.

    It seems like a lot of the functionality that the Finder used to handle is now taken care of by indiviual, specialized apps, that know more about the files in question than the Finder does (i.e. MP3 tags, photo import batch, etc) and can manipulate the files better using that information.

    In OS 9, the Finder was indispensible. In OS X, it has really become just another app. An interface for examining file system contents, dragging files around, and opening files and applications. But unlike OS 9 days, it's hard to think of much that the Finder does that can't be done using some other method. More options is a good thing.

    Not to say that the Finder couldn't be improved. Maybe its pokiness and poor design is what has prompted so many to use alternative methods. But, I'm happy when the Finder just stays out of my way, which it does quite well now.

    --
    You drank my drink, you drunk!
    1. Re:Vestigial Finder Remnants by Anonymous Coward · · Score: 0
      Fixing the Finder won't help. You see, Apple is already on very shaky ground financially. Frankly, many prominent industry analysts have crunched the numbers, concluding that Apple's outlook is bleak indeed.

      In Apple's latest numbers released in January for its fiscal first quarter of 2003, revenue fell from a year earlier and all of the company's major computer lines saw diminished numbers. PowerMac sales were down 20%, while iBook sales fell 8%.

      At the same time Apple's sales were falling, PC sales rose, though just slightly, according to figures from IDC released last month.

      The last time Apple was in this state, it brought back co-founder Steve Jobs to fix its issues. He fostered the development of the iMac and secured a US$150-million investment from Microsoft. But there aren't any new iMacs in Apple's future and Microsoft, bolstered by its victory over the U.S. Department of Justice, is clearly not going to help the beleaguered computer maker this time.

      So what have you got left? Apple is a company that controls around 3% of the computer market, has recently undergone a restructuring and is slowly fading into nothingness. Software makers don't even have Mac users on their radar and it's not like Apple can bring Mr. Jobs back to right the ship this time -- he's already there.

      Stick a fork in 'em -- this Apple is cooked.

    2. Re:Vestigial Finder Remnants by Anonymous Coward · · Score: 0

      and bsd is dying, the world is coming to an end, we're all going to get cancer from eating red meat, the ice caps are melting, our children are getting dumber, and so on.

  47. Re:Full Mirror by IamTheRealMike · · Score: 4, Insightful
    It's offtopic, but what the hell.

    You know, slashdot has very specific reasons for not caching web pages, ranging from bandwidth usage to the fact that a page might update in the middle of a slashdotting.

    Shifting the bandwidth usage onto Sourceforge, in particular, seems a bit dumb - they are run by the same company. If Slashdot can't financially justify caching, what makes you think SourceForge can.

    Oh, and I'd note that ars technica is not one that's going to get slashdotted anytime soon :)

  48. Re:Stupid OSX - Not really. by Caleb+Rutan · · Score: 2, Informative

    Huh? Of course you can list by date:

    Open finder. View->As List, or OpenApple-2, click 'Date Modified'.

    There you go.

    caleb

    --
    -- caleb
  49. Live search folders are amazing by Ececheira · · Score: 1

    One of the things the article mentions are live search folders--basically folders comprised of an pregenerated search result (for which the index is automaticly updated).

    This allows you to have different views of your existing data to separate the physical location from what you actually want.

    Microsoft Outlook 2003 includes these search folders in it now. For example, you can have a search folder for all unread items in all folders. So if you have rules that filter your incoming mail to various foldes, you can just go to the search folder to see all unread items--and then mark them all as read there rather than having to select mark all as read for each folder.

    If you want to have access to all email pertaining to a particular project, you can create a search folder to do so. The actual messages might be in your read and sent folders, and perhaps even in other public shared folders, but they'd all appear in your search folder.

    Given how useful it is for Outlook, I can't imagine how useful it'd be for an entire filesystem.

    Something tells me that this will be possbile in Longhorn with the new WinFS filesystem based on Yukon. It certainly will be interesting.

  50. I beg to differ... by ratboy666 · · Score: 1

    To quote from the article:

    Even the seemingly chaotic and messy act of "drilling down" to a deeply nested file using the Spatial Finder, double-clicking one folder after another and spawning windows like crazy, can be accomplished with comparatively little conscious thought. The user finds his way using visual cues (reinforced by the coherency and stability of the Spatial Finder) rather than by rote memorization of file paths. In the same way that you might drive a familiar route without knowing all the street names or exit numbers, the Spatial Finder user might not know the actual path of the file on disk. But like the driver, the user does not need to know all the names of the places along the way. He only needs to know where he is, and how to get there from here. In a non-spatial system, users must remember "addresses." The Spatial Finder enables users to remember locations.

    Now, there is a problem with spatial locations. Specifically, I can't remember the location of EVERY HOUSE AND BUILDING IN THE F*CKING CITY. Given that I have 100GB on line, in 60,000+ documents, and piles more on tape, I can't remember each file. What I do is give each of these and ADDRESS, just like my house has an ADDRESS. We have directories (on-line and off-line) that let us retrieve the location given the address. In other words, to manage larger pieces of data, people resort to EXACTELY the scheme that OSX uses (and most other modern GUIs). Also, addresses can be manipulated symbolically. If I know the library location of a book I am interested in (in the card catalog -- another fine example), I can look for other related material.Kind of demolishes the rest of the argument.

    I do wonder if some people just can't reason symbolically. If so, there should be computer (and other) interfaces for them. As to light switches, etc., switches are ok, but if you are in a large building, -or- wish to automate, you need some form of symbolic addressing for the switches. A hierarchy then makes sense (assume lights/ac/sprinklers). And you're back to paths.
    So, people who CAN'T deal with the "path" interfaces should have the "direct" option, but its their own problem when trying to deal with complexity.

    Ratboy

    --
    Just another "Cubible(sic) Joe" 2 17 3061
    1. Re:I beg to differ... by Steve+Cowan · · Score: 1
      Now, there is a problem with spatial locations. Specifically, I can't remember the location of EVERY HOUSE AND BUILDING IN THE F*CKING CITY. Given that I have 100GB on line, in 60,000+ documents, and piles more on tape, I can't remember each file. What I do is give each of these and ADDRESS, just like my house has an ADDRESS. We have directories (on-line and off-line) that let us retrieve the location given the address. In other words, to manage larger pieces of data, people resort to EXACTELY the scheme that OSX uses (and most other modern GUIs). Also, addresses can be manipulated symbolically.

      Once you know the address, you use a map to find the house. And after you've travelled there a few times, you "know the way" to the house. You may forget street names, but you still know where to turn.

      This is the kind of natural interaction with your files Sircusa is referring to. If you think in terms of path names you largely defeat the purpose of having a GUI in the first place. This is what non-Mac users just "don't get" when we refer to ease of use, because it's not easily explained.

      To really appreciate Sircusa's article you have to have used the Classic Mac OS Finder, in a productive environment, for some time. To me there is not a more natural way to handle your files and folders. I don't think it's possible for it to be explained any better than it has been explained on Ars, and if you still disagree, you really have to experience it first-hand.

      To this date there is no better user interface for general-purpose file navigation and administration than the classic Mac OS Finder.

    2. Re:I beg to differ... by ratboy666 · · Score: 1

      Yes, I *have* used the "Classic Mac OS Finder". And quite detested it. I tried to use it in a production environment, where the clients demanded use of Mac technology. Problem was... files (work) is scattered over a network of machines, with automatically generated names (001-00156, 001-00157, etc. -- names chosen to be useful within the problem domain). Now, we have 300-400 such files per unit, and several thousand units on the go... There is a problem with a file, now, drill down to find and fix (or select based on templates). Of course, I attempted this BEFORE scripting was available on Macs. Being an old Unix guy, I just ASSUMED that this type of operation was tivial--after all this is a COMPUTER, right?

      As a result of this experience, I NEVER USED A MAC AGAIN. Maybe now, with OSX I'll think about it.

      I don't have any problems with a "spatial" interface, for those users that can't deal with anything else. Go ahead, put it in... In fact, I use a "spatial" interface on at least one of my machines -- I have folders on the desktop that refer to directories on the 'net. So, I don't have to think about opening up my status folder to update work status. You know what? It probably does save me time. But for the "real work", I still go back to a symbolic command interface.

      Ratboy.

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    3. Re:I beg to differ... by Steve+Cowan · · Score: 1
      If you are referring to running into this problem before the Finder was scriptable, then you are talking about before 1995, before there was a mainstream desktop *nix to achieve your task.

      Besides, there will always be special cases when a particular application will require a different approach. I am referring to desktop productivity, while your batch renaming requirement seems more like system administration to me. (And you could have tried one of many shareware file browsing and/or batch-renaming utilities which even then were plentiful for the Mac).

      As a creative professional dealing with lots of graphics and audio files, I felt more in touch with my stuff with OS 9 than I do with OS X. I found my files and launched them faster. I grabbed big handfulls of files (often by just positioning them to be close together in a window and rubber-band selecting the ones I want) and then dragged them into a different folder.

      Let's say you have a dozen files in a folder, mixed in with other files, and they all have completely different names. I want to move the files "Picasso", "Monet" and "Matisse" into a folder one level up called "painted works", and I want to move "Devo", "Smashing Pumpkins" and "Beethoven" into a folder called "music". I want to leave all of the remaining files (some logos and my downloaded Elvis songs) in the folder I currently have. How would you do this quickly with a "symbolic command interface"?

      This is stuff that desktop power-users need to be able to do with their eyes closed. Using Mac OS 9 I could do all that in about 5 seconds and carry on a conversation with somebody at the same time.

    4. Re:I beg to differ... by ratboy666 · · Score: 1

      Ok, I'll take your challenge:

      mv PiMoMa..
      mv DeSmBe/mu

      should do it. 32 keystrokes, no mouse.

      Timed myself doing it -- took 4-5 seconds when I was paying attention, 10 seconds when I wasn't.

      The sequence MAY be smaller, depends on OTHER file names -- feedback is a [beep] if it isn't unique yet.

      Ratboy.

      PS. Yes, Unix systems were available (SCO, IDRIS, IBM, XENIS, others) The only reason that they were not used is that the client insisted on Macs. And, this was in 1989/90.

      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    5. Re:I beg to differ... by ratboy666 · · Score: 1

      Sorry to be replying to myself: Slashdot ate part of my message: Here is the sequence (tab) and (return) refer to the keypress:

      mv Pi(tab)Mo(tab)Ma(tab)..(return)
      mv De(tab)Sm(tab)Be(tab)/mu(tab)(return)

      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    6. Re:I beg to differ... by NickV · · Score: 1

      God, his point is that his approach scales and yours doesn't.

      Let's say he has 65 paintings by about 35 artists... sometimes the artists names are spilled differently or in a different format (Da Vinci vs Leonardo)

      And now let's say you have 85 different songs (and in an ideal world the extension isn't there because it's a superfulous computer concept that really has no real world equivalent) by different artists, this still will take him about 5 seconds ..

      Now let's say I want some of these artists in impressionists and some in Avant Garde...

      You see where he's getting?

      The CLI user will be writing ALOT of lines of commands (or doing an ungodly amount of tab completion) to complete something that will take the desktop spatial user a few seconds at most.

  51. Re:a better finder? by Anonymous Coward · · Score: 1, Informative
    Both of your posts are over simplifications. The number of customers is irrelevant. It is the revenue and profit that can be generated from the customer base that are important. If Mac vendors can expect $10 per customer in revenue and $3 in profit, they make $10,000 and $3,000, respectively (Apple's own profit is about 30% of revenue).

    Windows vendors generate the same $10,000 in revenue, but only clear 8% profit (or even less, in many cases), because of a crowded and much more competitive environment (ie, competitive pressures among 200 vendors than 10 vendors is a very differenct competitive landscape). Therefore, the PC vendors each generates only $800 of profit from the same $10,000 of revenue. That is why Gateway and Apple can have similar revenue lines but vastly different returns and cash reserves (eg, Gateway is bankrupt and Apple is flush with cash). That is why the MacBU at Microsoft is one of the most profitable centers for MS. It is an important reason why Mercedes and BMW are so profitable, but GM and Ford struggle. Being small and addressing a smaller market can be a much better strategy than being all things to all people.

  52. OS X Finder Laundry List - Please add yours. by teamhasnoi · · Score: 3, Interesting
    Too many files: Apple's Finder chokes on multiple thousands of files. If I want to put/copy/paste that many files in a folder, I damn well should be able to without the system grinding to a halt or finder crashing. I had to use 'Path Finder' ( a finder replacement, ala Windows Explorer) to handle this situation.

    Renaming files: There is a delay in renaming that makes me crazy. I'll click on a file and it won't go into the rename unless I wait a moment and click again.
    There is no undo for renaming. If I accidentally rename a file, I have to find the file (not easy with numbered files), find out what the original name was (could take a few minutes to never) and manually rename it. I want 'apple-z' to undo the rename. (It works for copy, paste and other finder operations.)
    There is a delay in the update of windows after a file has been renamed and/or saved. This also shifts the files viewable up or down so that when I go to click on the next one, I click on the file that has somehow magically appeared under my cursor. Most annoying.

    Copy/replace dialogs: There is information missing from these, that I could use to make my decision of whether or not to replace that file/s. Where is the date? It just gives me 'newer'.

    Collumn view: No viewing by date, size, or anything but name. It's there in the other 'views', why can't I have it here?

    Save Dialogs: Same with collumn view. I hated how the old os9 save dialog (think pagemaker - grr.) would pop up and be immovable - invaribly, I needed some info that was immediately under that window. Let me move it. Let me sort the contents by date, size, name.

    Labels: If you haven't used labels, you have no idea what you missed out on. Putting a colored cast to an icon was about the most useful thing I had ever seen. I used it extensively in the short time before I moved to OS X. Now the labels are gone, still visible in some os9 apps, but unused by OS X. Nothing would allow me to find a folder in a sea of blue like one with a red sheen to it.

    In fact, icons were easier to maipulate in os9 than X. It seemed I could take anything and make an icon out of it, whereas X requires more forethought and a concerted effort. This may be different now; I've stopped trying.

    Pop-up folders were swell, however I don't miss them like the labels.

    Lastly, Unresponsiveness and Instabillity: The Finder likes to sit for a moment and think about how it's going to perform the operation you told it to do. Copy the file, already. You've done it a million times, and you're wondering how this one is different? (pardon my anthromorphising). Recently, I had to ftp several thousand jpgs, and had to do it at home on my windows machine, since the finder choked at the prospect. "You want me to do what? Uh. I'm busy that weekend..."

    Mac users should know that my widows machine said nothing, but did the requested operation with no flair at all, of course.

    Apple *should* incorporate some of these features (LABELS!); they have years of a great user interface to build on. They have already impressed the hell out of me with OS X, it just needs some polishing.

    Please add your thoughts.

    1. Re:OS X Finder Laundry List - Please add yours. by jtdubs · · Score: 1

      Here's another one.

      Why the hell is it easier to rename a file or folder than to run/open it?

      Pressing Enter, which in win32 or linux land would in some way activate an item, in instead delegated to the mundane activity of renaming on OS X. Do people really rename so frequently that they need to steal the Enter key for this purpose.

      To actually open you have to use Apple+O, which is considerably harder to key.

      Justin Dubs

    2. Re:OS X Finder Laundry List - Please add yours. by Chmarr · · Score: 3, Informative

      Too many files: Apple's Finder chokes on multiple thousands of files.

      Does not. I have one directory with some 3000 directories in it, each with from 1-500 files inside, and I can open them up and do tonnes of stuff with them. Yes, it starts to slow down, but no more than my Windows box does on the same directory.

      Renaming files: There is a delay in renaming that makes me crazy. I'll click on a file and it won't go into the rename unless I wait a moment and click again.

      Does not. Here, I'll test. Click and keep the mouse pointer over the file name. After 2 seconds it goes into rename mode, no further click required. (Yes, the delay is still required)

      There is no undo for renaming.
      Just renamed a file, and hit command-Z, and it undooed the rename just fine.

      Collumn view: No viewing by date, size, or anything but name. It's there in the other 'views', why can't I have it here?

      Click on the detail view (The icon with the number of horizonal lines), and then click on the column title that you want to sort by. How hard is this?

      Save Dialogs: Same with collumn view. I hated how the old os9 save dialog (think pagemaker - grr.) would pop up and be immovable - invaribly, I needed some info that was immediately under that window. Let me move it. Let me sort the contents by date, size, name.

      Granted the save dialog doesn't have the same viewing options as a finder window, but it's certainly movable.

      Pop-up folders were swell, however I don't miss them like the labels.

      Older versions of OS/X were missing this feature, but 'spring-loaded folders' are back.

    3. Re:OS X Finder Laundry List - Please add yours. by jkabbe · · Score: 1

      Does not. I have one directory with some 3000 directories in it, each with from 1-500 files inside, and I can open them up and do tonnes of stuff with them. Yes, it starts to slow down, but no more than my Windows box does on the same directory.

      If I try to move 100+ files from one directory to another it takes over a minute. The Finder just hangs. Of course the files moved instantly (verified at the command line) but the Finder spends a ton of time cleaning up its mess.

    4. Re:OS X Finder Laundry List - Please add yours. by teamhasnoi · · Score: 1
      I can't speak for your directory as I have one folder with 8,521 tifs in it. It's a crazy amount I know, but there for Pagemaker linking and finding purposes.

      You are right about the rename (I was typing this from home ((Windows)) and so going from memory - I have managed to do what I said, I may have had my hands over some key combo and spaztically messed it up.

      The collumn view is the last of the three choices, is it not? Icon, list and collumn. I still can't get it to sort by anything but name, even if I sort by date in the list view,it doesn't change in the collumn view.

      Save dialogs in OS X are certainly movable; I was referring to os 9 there. My problem with os X save dialogs is the same at with the collumn view, it would be useful to be able to choose icon or list view, or sort the collumn view. (Photoshop 7 specifically)

      Pop up folders are different from spring loaded folders. OS9 Pop up folders sit at the bottom of the screen, and 'pop up' when single clicked on . Spring loaded folders 'spring' open when dragging a document and hover over a folder.

    5. Re:OS X Finder Laundry List - Please add yours. by pressman · · Score: 1

      Well pop-up folders and spring loaded folders are two different things. I think the original poster meant tabbed folders that would reside at the bottom of the screen and pop open only when you clicked the tab. I gotta say I mess this feature. I used it as a subsitute for the Launcher.... which I hated more than Hitler. I also miss the Windowshade feature. Sometimes I like to have my wondows up on the screen, but minimized with Windowshade.

      After 2 years of using OS X almost exclusively, I can't imagine going back to OS 9 full time now. Sure there are things I miss, but I have a feeling a lot of our favorite features will make their way back into the OS in upcoming revisions.

      --
      Pooty tweet
    6. Re:OS X Finder Laundry List - Please add yours. by Alrescha · · Score: 1

      "Too many files: Apple's Finder chokes on multiple thousands of files. If I want to put/copy/paste that many files in a folder, I damn well should be able to without the system grinding to a halt or finder crashing. I had to use 'Path Finder' ( a finder replacement, ala Windows Explorer) to handle this situation."

      I could not reproduce this problem. I have a folder with 10,596 files in it (I have all my old mail - sick, I know) and Finder didn't have any issues opening and displaying it. It did take 10 seconds to do it, but I don't think that's unreasonable.

      off topic:

      I remember trying to get this collection off of it's original machine using FTP (didn't have tar/zip). It was a serious challenge finding a PC client that could deal with that many files. "mget *" would usually cause a long pause followed by an application crash :-)

      A.

      --
      ...bringing you cynical quips since 1998
    7. Re:OS X Finder Laundry List - Please add yours. by Phrogz · · Score: 1

      Renaming files - as has always been the case with MacOS, either hit return to instantly start renaming, or click on the name and then jog your mouse to the side. You'll enter rename mode immediately.

      Column view - yeah, sometimes I'd like to be able to sort by date. But...you don't SEE the date in the column. Sorting by some arbitrary attribute which you can't SEE to compare from one to the other is rightly omitted, IMO.

      Save Dialogs - I don't know what your problem is here. You're annoyed by their modality? For applications properly using the OS X Sheet API the save sheet is attached the the window it is modal to and you can still access other items outside that window. If you're upset that it's modal, well then talk to the software developer who chose to make the Save dialog modal.

      Labels - although I firmly believe that, just as spring loaded folders were added back in with Jaguar, we'll see labels and other tried-and-true features in 10.3 and later. BUT, for now, you can get this 100% effective haxie to give you labels in the finder.

    8. Re:OS X Finder Laundry List - Please add yours. by pressman · · Score: 1

      To actually open you have to use Apple+O, which is considerably harder to key.

      This is simply nitpicking IMHO. To open a document in any application it's always cmd+O. It is the same in the Finder for the sake of consistency. In fact, in most applications with tabbed interfaces, the "Enter" key is used to designate that an alteration to a object (done via a form field in a tabbed palette) is final. Want to reselect the data in the field, hit "Enter" again.

      For the most part, Finder key commands behave similarly to they way they do in most applications. For the most part... they are always always always exceptions... sometime too numerous to count.

      And, come on, is cmd+O really that HARD to key. I can do it in my sleep as well as close documents, etc. etc. And it certainly makes more sense that alt+f4 to close a window in Windows!

      --
      Pooty tweet
    9. Re:OS X Finder Laundry List - Please add yours. by cpt+kangarooski · · Score: 1

      1) Because Cmd-O is already in use in pretty much every other program that can open files, and consistency is a virtue.

      2) Because it is felt that modes should be avoided, where possible. So the Return key is thought of as the toggle-renaming-of-icons key, and this duality is believed to be important to the anti-mode goal.

      And there may be a third factor, in that the preferred way to open files is with the mouse. People who have hands on the keyboard are more likely trying to rename something or use a keyboard shortcut than open anything.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    10. Re:OS X Finder Laundry List - Please add yours. by Racher · · Score: 1

      To rename something in the finder just select the file and hit 'return' it will then allow you to type, no waiting.

      yes I know with Windows 'return' launches the application.

    11. Re:OS X Finder Laundry List - Please add yours. by nichrome · · Score: 2, Interesting

      "The Finder likes to sit for a moment and think about how it's going to perform the operation you told it to do. Copy the file, already. You've done it a million times, and you're wondering how this one is different?"

      You're forgetting that it can very well be different from those million other copy operations. The Mac OS does (and always has done) so-called preflighting before initiating a copy. It checks to see if the item you are copying can fit onto the disk you're copying it to. This means that it will not try to write a file onto a disk that's full and then throw an error at you if it fails like most flavors of Windows do. It'll check to see if it can do the copy, and tell you to free up space or use another disk if it can't fit the item on the destination disk.

      Additionally, imagine running five copy operations at once. Imagine that four copies run, but the fifth can't fit onto the disk now that you just filled up the disk with the four other copies. If the system didn't do preflighting, you would have no clue as to which operation failed. If things went badly, the system might have tried to write parts of each of the five files onto disk, failing to complete even one of them. Preflighting makes sure you know which copy operations were succesful and which weren't. It will also make sure that an ongoing copy doesn't fill up the disk while other copies are being written onto the same disk.

      Essentially, you're screaming at the OS for being slow, while it's actually being smart for you. I imagine you'd scream at least twice as hard if the OS was faster but much more stupid -- like most other OSes.

      --
      --You think you've found my weakness, but I have more.--
    12. Re:OS X Finder Laundry List - Please add yours. by jtdubs · · Score: 1

      Yeah, it is nitpicking.

      Cmd+O is the standard for opening, and Enter does seem to be the standard for renaming/editing fields. You're right about that.

      No, Cmd+O isn't that hard. But it is substantially harder than Enter. Especially when your right hand is over on the arrow keys moving between icons.

      I definitly agree that Alt+F4 sucks. I like Cmd+O, Cmd+W, Cmd+Q. Very standard. I just tend to open more often than I rename, so I'd prefer the simple Enter be used for that as well as Cmd+O, and maybe use Cmd+R for renaming.

      Justin Dubs

    13. Re:OS X Finder Laundry List - Please add yours. by jtdubs · · Score: 1

      Your first point is undeniably true.

      Your second confuses me. You indicate that modes are bad, which seems to be a common belief. Then, you indicate that Return is a toggle key.

      The thing is... toggle implies modes. The Return key changes you from Not-Renaming-Mode to Renaming-Mode. You know it's a mode change because it changes how the keys work. Before right-arrow would move you to the icon to the right, now it moves you a character to the right. And so on.

      So, anyway, you seem to indicate that they are introducing a mode with a Return key because of their anti-mode beliefs.

      Unless I am horribly mistaken.

      Your third point is kind of a chicken/egg situation. The only reason people with their hands on the keyboard are more likely to be renaming is that Apple makes it such a pain in the butt to navigate with the keyboard. I almost never have to use the mouse to navigate from windows. On the mac the mouse seems required.

      Justin Dubs

    14. Re:OS X Finder Laundry List - Please add yours. by cpt+kangarooski · · Score: 1

      2) Oh, I know. I didn't say I agreed, or that it made sense. I said that that was what, AFAICT, the point of doing it that way was.

      3) Well, the thing about keyboard navigation is that it certainly _seems_ faster. And I won't deny that catering to user perception is not always a bad thing. But Apple had done some research along similar lines and determined that despite user perception, the mouse was in fact faster. Whether this still holds true, I can't say, but I encourage you to have someone time you doing various things with each method and check for yourself.

      And yes, the mouse -- or at least a pointing device -- was basically required on the Mac. Keyboards were not. (which presumably is why you had to buy them seperately for a time in the 80's and 90's, no joke)

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    15. Re:OS X Finder Laundry List - Please add yours. by jcbphi · · Score: 2, Informative

      Renaming files: There is a delay in renaming that makes me crazy. I'll click on a file and it won't go into the rename unless I wait a moment and click again.

      Does not. Here, I'll test. Click and keep the mouse pointer over the file name. After 2 seconds it goes into rename mode, no further click required. (Yes, the delay is still required)

      Click twice, but quickly move the mouse after the second click. No delay, except for that between the clicks. Not fast enough? Click once, hit return. Instantly in rename mode.

    16. Re:OS X Finder Laundry List - Please add yours. by jtdubs · · Score: 1

      Thanks for the info.

    17. Re:OS X Finder Laundry List - Please add yours. by Phroggy · · Score: 1

      To actually open you have to use Apple+O, which is considerably harder to key.

      I use Command-down arrow to open files or folders. Conveniently, Command-up arrow does "cd ..". Add option to automatically close the folder you're in when opening the new one (if you fixed your preferences to make windows behave how they should).

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    18. Re:OS X Finder Laundry List - Please add yours. by Paradise+Pete · · Score: 1
      Too many files: Apple's Finder chokes on multiple thousands of files.

      Yes it does. I resort to using the command line in these situations. Amazingly, moving thousands of files there is nearly instantaneous.

      There is no undo for renaming.

      Maybe I misunderstand, but there is. The edit menu even says "Undo Rename."

      Collumn view: No viewing by date, size, or anything but name.

      Yeah. Column view is great except for that. If it had it I wouldn't use anything else.

    19. Re:OS X Finder Laundry List - Please add yours. by Steve+Cowan · · Score: 1

      Empty trash dialog: In OS 9 when you chose empty trash the dialog would tell you how many items it contains and how much space it takes up. In OS X we get nothing more than an "are you sure" warning.

    20. Re:OS X Finder Laundry List - Please add yours. by Sentry21 · · Score: 1

      Renaming files: There is a delay in renaming that makes me crazy. I'll click on a file and it won't go into the rename unless I wait a moment and click again.

      This is intentional. I don't know for sure about OS X, but in OS everythingelse, you could click on the name and then move the mouse, and it would go into rename mode immediately. Just a few pixels will do.

      Labels: If you haven't blah blah...

      Clearly, you've never discovered Unsanity Software's products. Their haxies are a must-have for any OS X user. Check it out.

      --Dan

    21. Re:OS X Finder Laundry List - Please add yours. by cpt+kangarooski · · Score: 1

      To clarify re: #2, I think that it was felt that since there _was_ going to be an unavoidable mode switch (or else filenames would have to be never-editable or always editable all the time), it was better to have no more than necessary.

      Thus it's better to have an editing mode that changes the meaning of the alphanumeric keys from (IIRC on the original Mac) 'nothing' to 'type' and that would be all than to have it be that AND the button for 'open file' becomes 'go back to non-editing mode without opening the file.'

      The original Mac team did have a strong anti-mode mentality, but it's not as though modes are completely avoidable. Mostly they just tried to minimize them.

      However, modern thinking seems to be AFAIK that modes are acceptable IF the user is naturally making a mode switch anyway, and fully expects the function to change. The behavior of different tools in a paint program is a good example. Unexpected or undesired mode switches should still be avoided however.

      Whether the enter key functions are expected or not seems to me to be debatable.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    22. Re:OS X Finder Laundry List - Please add yours. by tuxedobob · · Score: 1

      Too many files: Apple's Finder chokes on multiple thousands of files. If I want to put/copy/paste that many files in a folder, I damn well should be able to without the system grinding to a halt or finder crashing. I had to use 'Path Finder' ( a finder replacement, ala Windows Explorer) to handle this situation.

      Copy the folder, not the files. If the files you want are a much smaller subset, why not simply copy them in small groups? If you try to drag and drop thousands of items, it's going to sit there and try to draw lots of translucent files before yes, crapping out.

      Renaming files: There is a delay in renaming that makes me crazy. I'll click on a file and it won't go into the rename unless I wait a moment and click again.
      There is no undo for renaming. If I accidentally rename a file, I have to find the file (not easy with numbered files), find out what the original name was (could take a few minutes to never) and manually rename it. I want 'apple-z' to undo the rename. (It works for copy, paste and other finder operations.)


      This is for the sake of double-clicking. As it is, if you double-click a file's name, the file opens. If there wasn't a rename delay, double-clicking a file's name would put you in rename mode at the point you double-clicked.

      There is a delay in the update of windows after a file has been renamed and/or saved. This also shifts the files viewable up or down so that when I go to click on the next one, I click on the file that has somehow magically appeared under my cursor. Most annoying.

      I think I come across this every now and then, but it doesn't happen often enough for me to complain about it.

      Copy/replace dialogs: There is information missing from these, that I could use to make my decision of whether or not to replace that file/s. Where is the date? It just gives me 'newer'.

      You mean you want to replace an older file if it's from February but not if it's from March? I think you have more file organizational issues than the Finder does.

      Collumn view: No viewing by date, size, or anything but name. It's there in the other 'views', why can't I have it here?

      Because it's not in the column view. Only names (and icons) are. It would be much more confusing if you forgot you had it set to sort by date and saw only the names.

      Save Dialogs: Same with collumn view. I hated how the old os9 save dialog (think pagemaker - grr.) would pop up and be immovable - invaribly, I needed some info that was immediately under that window. Let me move it. Let me sort the contents by date, size, name.

      Hence Apple's push toward developers using sheets for this purpose. If you mean something underneath within that document, though, what could you possibly need that you could forget so quickly?

      Labels: If you haven't used labels, you have no idea what you missed out on. Putting a colored cast to an icon was about the most useful thing I had ever seen. I used it extensively in the short time before I moved to OS X. Now the labels are gone, still visible in some os9 apps, but unused by OS X. Nothing would allow me to find a folder in a sea of blue like one with a red sheen to it.

      On this I have to agree with you. Labels were useful, albeit rarely. Rumor has it these are coming back.

      In fact, icons were easier to maipulate in os9 than X. It seemed I could take anything and make an icon out of it, whereas X requires more forethought and a concerted effort. This may be different now; I've stopped trying.

      I would have a response for this, but I haven't even tried to mess with icons in OS X. I like them as they are.

      Pop-up folders were swell, however I don't miss them like the labels.

      Gah. I hated pop-up windows. Too quickly does your screen become cluttered with little tabs. I much prefer stuff being sent to the Dock, especially since option-cli

    23. Re:OS X Finder Laundry List - Please add yours. by Pinky · · Score: 1

      Renaming files: There is a delay in renaming that makes me crazy. I'll click on a file and it won't go into the rename unless I wait a moment and click again.

      =-=-=-

      No. If you click on a filename it pauses for a while to make sure that you're not going to do a double click then enters renaming mode.. This delay is actually too short and the finder is too unresponsive so that it's totlay useless because the second click arrives to late sometimes and it goes into renaming mode even if you double clicked on the name. There's also a few other problems with related to the finder loosing the second click.

      The delay was introduced in system 7. System 6 made the file go into renaming mode as soon as you clicked on the filename and I remeber switching back and forth between them and system 6's behavior was really annoying.. I actually get flashback when macOS X finder looses one of the clicks.. I hate that bug! make the damn delay longer or fix the sluggishness that causes the second click to not register in time, Apple.

      of course, if you want to naming right away you can click anywhere on the icon, hit return, and start typing.. again since system 7.

    24. Re:OS X Finder Laundry List - Please add yours. by Pinky · · Score: 1

      The preffered keys for navigating in the finder are

      command - up arrow goes back a directory
      command - down arrow opens or activate an item

      open + the commands above will close the window behind when the new window / app opens...

      command - left or right arrow open up a triangle in list view

    25. Re:OS X Finder Laundry List - Please add yours. by Pinky · · Score: 1

      Mine doesn't do that but it DOES refuse to register a double click if the mouse has moved but slightly from the first click.. So THAT is why it occasionally ignores my double click... Ah-ha! Hummm, I wonder if I can get them to accept that as a bug.... only one way to find out.

    26. Re:OS X Finder Laundry List - Please add yours. by pressman · · Score: 1

      ooooo.... cmd+R has it's own special purpose which is "Find Original" which I use all the time. maybe option+cmd+r or some such thing. I don't mind complicated key chords just because I use Illustrator, Photoshop and InDesign all day lonng and bizarre key chords are typical in design apps.

      Then again, a lot of this is just person preference.

      --
      Pooty tweet
    27. Re:OS X Finder Laundry List - Please add yours. by Anonymous Coward · · Score: 0

      Re: choking on thousands of files

      Turn off icon preview. I found this problem on folders with thousand of JPG files *ahem*. Also, things have gotten much much better in Jaguar.

    28. Re:OS X Finder Laundry List - Please add yours. by Graff · · Score: 1
      Click and keep the mouse pointer over the file name. After 2 seconds it goes into rename mode, no further click required. (Yes, the delay is still required)

      Actually if you click on the file name and then move the mouse just a little bit it will go into rename mode immediately.
    29. Re:OS X Finder Laundry List - Please add yours. by Anonymous Coward · · Score: 0
      I'll tell you what I don't like. I like the column view... except you can't make the columns wide enough. You drag the window to make the columns bigger, except once you get past a certain size it adds *another column* and all the column widths shrink back.

      If there was say, a horizontal scroll bar under the column it might be okay, but OSX has this tendency to abbreviate the long filenames "bblahlbah...2" in the display, so when the the columns are aren't wide enough I can't tell the right file sometimes.

    30. Re:OS X Finder Laundry List - Please add yours. by Chmarr · · Score: 1

      The collumn view is the last of the three choices, is it not? Icon, list and collumn. I still can't get it to sort by anything but name, even if I sort by date in the list view,it doesn't change in the collumn view.

      My bad, I was referring to the list view, where you can change the sorting order just fine. The column view you can't... but... since it doesn't display anything other than file names, why would you want to?

      Pop up folders are different from spring loaded folders. OS9 Pop up folders sit at the bottom of the screen, and 'pop up' when single clicked on . Spring loaded folders 'spring' open when dragging a document and hover over a folder.

      Not really sure what the feature you're describing here, is. Try this: Put a folder into the dock. When you click-hold (or right click, or control-click) the folder, a list pops up with the contents of the folder. You can go n-levels deep, too. Is that the feature you were looking for?

      Other points not mentioned are conceded.

    31. Re:OS X Finder Laundry List - Please add yours. by Chmarr · · Score: 1

      I never used OS9 myself. I 'switched' only when OS/X was available, but the same sentiment is felt with all the Mac users I know in the office. They miss features from OS9, but would never go back.

      OS/X is still evolving, though... every minor release has resolved many a gripe. Compare this to Windows... which seems to create MORE gripes as things progress :)

    32. Re:OS X Finder Laundry List - Please add yours. by Chmarr · · Score: 1

      Ooo! Thanks!

      Actually, all you have to do is click on the text and move mouse (not drag). No second click required. That's neat.

      And it makes sense, too. You click on the part you want to edit, and move the mouse out of the way so you can edit it.

      (Only works in icon views... in list or column views, there's still the delay)

    33. Re:OS X Finder Laundry List - Please add yours. by Chmarr · · Score: 1

      Granted. Move and copy operations in the finder are SLOW. It's much faster to do that through the shell.

      I'm hoping that's one of the things they'll fix in 10.3

    34. Re:OS X Finder Laundry List - Please add yours. by snolan · · Score: 1

      It is specifically more slow when the view is set such that file type or modification time are used as the key index (sort order). It is much faster if name is used as the key index. At least in column view.

    35. Re:OS X Finder Laundry List - Please add yours. by snolan · · Score: 1

      Copy/Replace Dialogs: i wish they'd tell you the sizes of the files that are being copied and about to be over-written... then I could make the appropriate decision based on the facts that are before me, rather than having to go look in the background...

  53. Just a thought by Ilan+Volow · · Score: 1

    Or perhaps the GUI is the right thing to use, and we have the we have the wrong people developing GUI's.

    --
    Ergonomica Auctorita Illico!
  54. who cares by Anonymous Coward · · Score: 0

    who needs finder when you have... the console :)

    1. Re:who cares by diverman · · Score: 1

      Although I understand your meaning in reference to a *NIX system, however, I think you mean "Terminal". The Console in OS X is more or less a system log of sorts. :)

      Unelss you really like to just sit and watch error messages as they occur. :)

      -Alex

  55. Re:a better finder? by komor · · Score: 1

    Congratulations!! You have the most idiotic post of the day!
    Maybe not. If you think there are 10 mac vendors and 200 PC vendors, then you don't really know how much crap is available for the Windows market...
    But seriously, I can remember from my youth, that being an Atari developer in a small Poland country (which is where I live) was really pleasant and easy - because of lack of competition... I was able to earn some real money (to buy more developer tools...) despite the fact, that Atari had a minor marketshare in Poland, maybe less than Apple today, and mostly in home-user market, not in lucrative creative market, as Apple.
  56. Re:Full Mirror by Caesar · · Score: 5, Informative

    Did you happen to get permission to host that article from Ars? I don't think so. I never gave that permission, nor did the author.

    I know what you're doing is with good intentions, but our server is running just fine, and what you're essentially doing is hurting our business because mirroring this document without our permissions removes our ability to see important stats about the article's readers. We kinda need that info if we're going to continue to provide free content.

  57. Basically, a GIVE ME BACK MY OS 9 article by kalidasa · · Score: 1

    disguised as serious UI theory. Look, the moment the guy writes:

    Labels - Like the feature introduced in System 7, but extensible, and with support for different scopes (e.g. globally visible labels, user-specific labels, etc.) The ability to "colorize" icons is a natural extension of the Spatial Finder, providing a quick visual cue for metadata that would otherwise have to be read as a text.

    he loses credibility. Not because labels are a bad thing, they're a good thing, and I'd like to have them too, along with other metadata improvements; but labels have no connection whatsoever with the spatial metaphor he's talking about in his "spatial finder" rant: one does not normally label a doorknob.

    The article suffers from that tendency in reasoning called "saving the phenomena" - he wants to come up with a catchall argument that explains why OS 9's finder was better than OS X's, damnit, and he'll do any rhetorical gymnastics he has to in order to fit every missing feature of OS 9 into the argument. Anything he says that goes beyond OS 9 is basically just a linear improvement on OS 9, like an OS 10 might have been, rather than a NeXT operating system.

    Too bad, as I would love to see a good, original article on improving the UI.

    1. Re:Basically, a GIVE ME BACK MY OS 9 article by SoupIsGoodFood_42 · · Score: 1
      he loses credibility. Not because labels are a bad thing, they're a good thing, and I'd like to have them too, along with other metadata improvements; but labels have no connection whatsoever with the spatial metaphor he's talking about in his "spatial finder" rant: one does not normally label a doorknob.

      First, I think you missed the point he stated at the begining that many people think that a spatial UI has to be a metaphore to something in real life. Hence your doornob argument is irrelivent.

      Secondly. Why wouldn't you want to color code a doornob or a door? If you had a long hallway, with many doors, color coding some of them may be of use. Especialy things like toilets or emergencey exits (which are quite oftern color coded and/or labeled).

      Anything he says that goes beyond OS 9 is basically just a linear improvement on OS 9, like an OS 10 might have been, rather than a NeXT operating system.

      That might have been a good point if you had mentioned, let alone try and prove that Next had a better GUI. But since you didn't I'm not really sure what your point is. Shold we be re-inventing the wheel instead of improving upon something that already works?

      Too bad, as I would love to see a good, original article on improving the UI.

      Too bad, as I would love to see a proper discussion on /. about GUIs that wasn't dominated by people saying the CLI is better or misinterperating concepts on GUIs and usability.

    2. Re:Basically, a GIVE ME BACK MY OS 9 article by northstarlarry · · Score: 1
      Well, no, you don't label doorknobs as doorknobs, but that's not what labels do. Doorknobs are non-movable tools, more like a button than a folder, and "labels", in this case, means colorizing, not words.

      Imagine you have a bookcase with 15 books, all with the same physical appearance: they're all 10 inches tall, 2 inches thick, and a soothing blue color. They have their names written on them, so that differentiates them, but what if you "labelled" one of them red? I bet you could pick that one out about a hundred times faster.
      That's the connection to spatiality.

    3. Re:Basically, a GIVE ME BACK MY OS 9 article by John+Siracusa · · Score: 1
      the moment the guy writes:
      "Labels - Like the feature introduced in System 7, but extensible, and with support for different scopes (e.g. globally visible labels, user-specific labels, etc.) The ability to "colorize" icons is a natural extension of the Spatial Finder, providing a quick visual cue for metadata that would otherwise have to be read as a text."
      he loses credibility. Not because labels are a bad thing, they're a good thing, and I'd like to have them too, along with other metadata improvements; but labels have no connection whatsoever with the spatial metaphor he's talking about in his "spatial finder"

      As I said, labels are a natural extension of the Spatial Finder in that they provide a quick visual cue for metadata that would otherwise have to be read as a text, just as the Spatial Finder provides visual cues for path/location information that would otherwise have to be read. Perhaps I should have said labels are "a natural extension of the values that form the foundation for the Spatial Finder", but I thought the intent was clear with the existing wording.

    4. Re:Basically, a GIVE ME BACK MY OS 9 article by kalidasa · · Score: 1

      Perhaps I should have said labels are "a natural extension of the values that form the foundation for the Spatial Finder", but I thought the intent was clear with the existing wording.

      No, it wasn't. Rather you should have written what you've just written above, as it is a far more supportable argument.

      Good of you to answer the criticism directly. How would you answer my other criticism: which of the suggestions that you mention were not inspired by OS9?

    5. Re:Basically, a GIVE ME BACK MY OS 9 article by kalidasa · · Score: 1

      First, I think you missed the point he stated at the begining that many people think that a spatial UI has to be a metaphore to something in real life. Hence your doornob argument is irrelivent.

      Nope. I didn't miss the point. Did you not notice that the doorknob metaphor was taken from the article? See his response to me below for a better way of answering that criticism (or actually, your own second sentence). I don't know if I buy the idea that color-coding is "spatial." It's a different kind of real-world-to-virtual metaphor than the spatial one, a qualitative (rather than spatial) metaphor. Maybe I'm taking the word "spatial" too literally, too.

      That might have been a good point if you had mentioned, let alone try and prove that Next had a better GUI. But since you didn't I'm not really sure what your point is. Shold we be re-inventing the wheel instead of improving upon something that already works?

      The wheel has already been reinvented. OS X is NOT a linear progression from OS 9, it is a linear progression from NeXT. Which had the better GUI isn't the issue; the issue is whether the article really says anything more than "they should have brought the whole OS 9 GUI over to OS X, instead of creating a new GUI that is neither fish (OS 9) or fowl (NeXTStep)."

      Given the tendency of some /. readers to post about 3D GUIs, how would the author integrate ideas about 3D GUIs into his spatial metaphor? Is a 3D GUI even better because it is more spatial? I don't remember seeing that in the article (feel free to trump me if I'm wrong).

      How is a tree more spatial than a column-based representation of directory structure? Isn't a tree better described as a useful non-spatial representational element? (I mean the linear trees, not a big spread-out org chart style tree, which would be more "spatial.") Why is a many-to-one representation really so bad? Is it because the user has such a hard time understanding the idea that two windows can point to one folder? The way this was handled (which window is it?) didn't quite capture the argument for me. I think the many-to-one model can be quite useful. I agree with him, though, with the idea that "open every folder in a new frame" would be a better default than "open new folders in the frame of parent" is. That's one place the spatial argument really holds together well.

      Too bad, as I would love to see a proper discussion on /. about GUIs that wasn't dominated by people saying the CLI is better or misinterperating concepts on GUIs and usability.

      Where did I say CLI is better? (It is better for some things, GUI is better for others.) The other half of your last comment is best described as specious.

  58. Oh, wonderful... by Millennium · · Score: 4, Insightful

    Another victim of interface fundamentalism. A few decent points, but for the most part the guy sounds like he just wants his OS9 back. Rather disappointing; his articles are usually much more... hmm, how to put it... independent than this.

    Look. Spatial orientation is a good paradigm. It is not, however, the be-all and end-all of interface design. This appears to be something that Tog and his apostles have yet to understand. There is a better way. I don't claim to know what it is; it's possible that it might not have even been discovered yet. But there's always a better way, and rather than slavishly imitating older designs we should be working to find newer ones.

    The whole interesting thing about NeXT is that they managed to create a non-spatial interface paradigm that actually worked well. For all the theory behind spatial orientation being so much faster, it just doesn't hold up in the real world. In the end, they're basically equal, with each paradigm having its own advantages and disadvantages, but it all comes out in the wash. That's the interesting thing about the human mind: theory is good, but reality often breaks the rules. Would it be nice if the Finder actually remembered window positions and icons in a consistent manner? Yes, it would; it's rather convenient. I wouldn't mind seeing this fixed in OSX's finder, if it can be done in a manner that doesn't cripple its speed. But that's all it is: a convenience; there's nothing to show that it actually precipitates a fundamental, universal improvement in performance or usability.

    Labels: Worse than useless, at least in the incarnation we know from OS9. Better systems can be devised, as the myriad workflow tools in existence have shown us.

    Recordability: OK, touche on this one. I don't use AppleScript much myself, but recordability is a Very Good Thing in terms of convenience.

    The "Finder Browser": I oppose the name pretty strongly, if only because it would likely spread the meme-virus common to Windows and the Linux desktop environments that the file manager and Web browser should be intertwined in the same app. Other than that, what I'd like to see, if Column View is taken out of the Finder, is an option to use it in place of the Finder, not just as a complement. It's a different paradigm, but for many people it's better, and so it should be able to replace the old.

    Live Searches: Interesting, but I don't think these should be part of the Finder, per se. Don't make them folders; make them documents. Siracusa was wondering how to make them visually distinct from folders, and this would be the best way. Double-click, and it opens a new window, visually distinct from the Finder windows (and thus providing another contextual clue). The results are then displayed in a list format; since this is "non-spatial" there's no advantage to icon view and plenty of disadvantages, such as wasted screen space. In the space it takes to display twelve items arranged in a square for icon view, you could display 25 items or more in a list. That ability to see more items at once easily supercedes the advantage to icon-esque views, given the purpose of such searches.

    Finder Plugins: These actually exist in OSX. They're very poorly documented, and almost no one knows about them; the only one I've ever seen was for viewing AppleWorks word-processing documents in the Finder.

    Metadata: Hellz yeah. Metadata is a Great Thing, and needs to be used more extensively in OSX, not less.

    OSX's lack of support for metadata: Um, OSX does support metadata. The problem is, as is the case with most of Apple's best stuff, there's no documentation on it, leaving developers out in the cold.

    As a final note: with a Unix system, it isn't possible to achieve the one-to-one relationships between icons and files seen in OS9 and such. You can do it with windows and folders, which seems to be Siracusa's main beef, but it's impossible with icons and files, which may be equally impor

    1. Re:Oh, wonderful... by ivan256 · · Score: 2, Interesting

      Another victim of interface fundamentalism. ... Spatial orientation is a good paradigm. It is not, however, the be-all and end-all of interface design.

      I think the article's flaw is on a different level. It's not that he wants spacial representation, but that he wants a specific spacial representation that he happens to be familliar with. He says "there must be a one to one relationship between folders and windows." This is not the only way to create a coherent spacial relationship, it's just the one he's used to. He's so convinced that he's right that he came up with this argument, wrote a multi-page article about it, and didn't think it through with the open mind he asked of his readers. A spacial interface, by his definition, only needs a uniform spacial representation for files and folders. The relationship between windows and folders he insists on was the result of a logical leap he made because it seemed obvious to him. He never justified it beyond saying that it was how MacOS 9 and earlier did it, and it never occured to him that there were other posibilities. There is no way he'll ever convince me that he's come up with the perfect spacial interface when he's shown that he's too short sighted to see more than one possibility.

    2. Re:Oh, wonderful... by cpt+kangarooski · · Score: 1
      There is a better way. I don't claim to know what it is; it's possible that it might not have even been discovered yet. But there's always a better way, and rather than slavishly imitating older designs we should be working to find newer ones.


      I agree. However, I don't mind continuing to use existing methods, if they, in toto, work well, until better methods are found.


      Thus, I absolutely agree that MacOS labels needed serious improvement. But that's not an excuse for abandoning a useful feature (one which I used constantly, and would love to have on Windows), particularly since there's little to indicate that it's being improved upon and that the improvements will be shipped out anytime soon.


      That said of course, I really liked MacOS spaciality with regards to arrangement of icons and windows, and would like to get it back. In fact there's a ton of good MacOS features that I wish I had available right now, despite their failings, which should be corrected ASAP.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    3. Re:Oh, wonderful... by tuxedobob · · Score: 1

      Labels: Worse than useless, at least in the incarnation we know from OS9. Better systems can be devised, as the myriad workflow tools in existence have shown us.

      I'll throw an exception to this: labels were good for quickly sorting files into groups in which you didn't want to mess with anything else. Being able to tell immediately from an icon's color what it was labeled was occasionally very helpful. For a while I used it to see which of my apps were PPC-native and which were 68K-only.

      Now to catch it: if Labels were implemented in OS X, I could see them being done in one of two ways:

      1. Similar to how they were in OS 9. However, it would be preferable to have a label list that could be as large as the user needed, using user-defined colors and names, both of which would be visible in the Finder. (This may take a bit of icon wizardry with the new icons in OS X, though.)
      2. File Comments become ToolTips. 'Nuff said.
    4. Re:Oh, wonderful... by Phroggy · · Score: 2, Interesting

      The whole interesting thing about NeXT is that they managed to create a non-spatial interface paradigm that actually worked well.

      As was pointed out in the article, people who are used to remembering file paths can handle non-spacial interfaces better than newbies. If you're trying to access a file buried four layers deep, the column view works fine if you can remember the path, but spacial orientation allows you to use OTHER clues (such as which corner of the window you left it in) to choose the correct folders to open on your way. This is more natural to people who aren't already used to dealing with file paths. For those of us who are used to dealing with file paths, it doesn't get in the way.

      Yes, NeXTStep worked well. The people I know who used it are all intelligent people who are accustomed to dealing with file paths and would not have trouble with that kind of interface. My mother would be lost.

      Labels: Worse than useless, at least in the incarnation we know from OS9.

      I didn't use them that often, but I certainly used them. It's not something I usually thought about much - it was just another tool available to me, that I could use for various purposes. I could color particular icons to make them stand out, or apply different labels to affect search order. I remember taking a bunch of MP3s in folders sorted by artist, going through each one, and making any necessary corrections to the ID3 tags - then using labels to mark which artist folders I had finished going through. Obviously when I was done, I cleared all the labels - I'd never intended for the labels to be permanent. It was just a temporary thing, and there are other ways I could have done it (moved them into a "done" folder), but labels were there so I used them.

      Sure, they could be better. You're right. How? Suggestions?

      The "Finder Browser": I oppose the name pretty strongly...

      Hush. It's not a web browser. It's a file browser. IMHO the Finder is long overdue for renaming, but having browser windows isn't a problem, and doesn't confuse people. "Finder" confuses people.

      Live Searches: Interesting, but I don't think these should be part of the Finder, per se. Don't make them folders; make them documents.

      I completely agree. You should be able to save a search as a sort of bookmark file, and when double-clicking it should open into a Search Results window much like the current Search Results window you get as a result from using the Find command.

      Metadata: Hellz yeah.

      Damn right.

      OSX's lack of support for metadata: Um, OSX does support metadata. The problem is, as is the case with most of Apple's best stuff, there's no documentation on it, leaving developers out in the cold.

      When OSX was initially released, developers were told that when saving a file, setting the file and creator types was optional, because the OS would simply use the file extension (which would be hidden from the user by default) to determine both. I wanted to smack somebody. The importance of metadata was downplayed by Apple, and now that they've maybe realized their mistake, some damage has already been done.

      As a final note: with a Unix system, it isn't possible to achieve the one-to-one relationships between icons and files seen in OS9 and such. You can do it with windows and folders, which seems to be Siracusa's main beef, but it's impossible with icons and files, which may be equally important. The reason: hardlinks. Simply put, a single file can be in multiple locations in OSX; even HFS+ supports this.

      True. Symbolic links appear as aliases, which is fine, but with hardlinks, the same file shows up in two places (with an icon in each place). However, I'm not convinced that this breaks anything. They simply behave as two separate files, that happen to share the same content. Each icon exists spacially (it can be moved around and positioned how you like).

      The fact is, hard links aren't that common, and the average user isn't likely to see one. The more advanced user knows what they are and how to deal with them.

      The UI for handling hard links could certainly be improved, but the existance of hard links doesn't break the entire paradigm.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    5. Re:Oh, wonderful... by Anonymous Coward · · Score: 0
      There is a better way. I don't claim to know what it is; it's possible that it might not have even been discovered yet. But there's always a better way, and rather than slavishly imitating older designs we should be working to find newer ones.

      You sure about that? "Always" a better way? I say until a better way is actually invented, the most you can do is merely postulate that there is a better way. This is what drives innovation, of course, but sometimes there is no better way.

    6. Re:Oh, wonderful... by Drakonian · · Score: 1
      Another victim of interface fundamentalism. A few decent points, but for the most part the guy sounds like he just wants his OS9 back. Rather disappointing; his articles are usually much more... hmm, how to put it... independent than this.

      The rest of your comment makes it clear that you DID actually read the rest of the article, so what's up with this intro? He wasn't whining about having OS9 Finder back - he went and detailed an entire possible replacement! He actually did mockups! If you can do, if you can't, post on Slashdot. He put in a lot of work to suggest a new method, whether you or me approve of his ideas or not.

      --
      Random is the New Order.
    7. Re:Oh, wonderful... by Herbmaster · · Score: 1

      Labels: Worse than useless, at least in the incarnation we know from OS9. Better systems can be devised, as the myriad workflow tools in existence have shown us.

      I think you're trolling. Labels being worse than useless would imply that just having them around without using them is a detriment to your system. They have essentially no overhead to speak of so this is patently false.

      On the contrary, labels are insanely useful. Even though I don't use them very often, I say they're insanely useful because there is no way to replicate a similar behavior without them (i.e. in OSX, in Windows, or in standard DOS or UNIX shells).

      I want to be able to assign a personal tag to a file or a group of files in a directory. I want that tag to have its own namespace and not interfere with the other "metadata" of that file (whatever that may mean in your context). Invading the filename namespace is totally unacceptable and kludgy. The purpose of this tag will be to let me do at least the following two things. It will let me sort a directory by an arbitrary criteria, placing certain items before others, based on categories I have assigned that may have nothing to do with anything else about the file. I used to sort my System Folder this way, back when that was a reasonable thing to do (System 7 through MacOS 9). It will also let me put a long-lasting "selection" tag on some files. Lets say I have a group of files that I want to do a series of operations with. I don't want to change the directory structure of the stuff I'm working with, and I don't want to archive the files together (as in tarring them). I want to email them to someone. Then I want to move them to a different drive. Then I want to delete the originals. Then I want to edit each of the files and put a note in them saying I've sent them to their destination and archived them. I can't do this with the normal Finder selection ability since I might want to do something else in between which would cause that selection to be forgotten about. All of this can be done easily because the Finder provided me a way to mark a bunch of files for <whatever the hell i want>ing. Having a centralized and consistent way to do all this is much less kludgy than any alternative.

      --
      I'm not a smorgasbord.
    8. Re:Oh, wonderful... by payndz · · Score: 1
      Labels: Worse than useless, at least in the incarnation we know from OS9. Better systems can be devised, as the myriad workflow tools in existence have shown us.

      To quote some guy from Duckman, "Dwaaaah?"

      I have to deal with literally hundreds of Word files over the course of a production schedule. Simply sorting by date doesn't tell me anything, because some of them may have been subbed, but not actually completed as they're waiting for additional elements to be pasted in, while others may have been checked by other people but not by me.

      Now I could use different folders for work at different stages of completion. But that would be a needless complication, because I want (note: *want*, as in it's my decision on the best way to work) all the documents in the same place.

      Coloured, personalised labels to tell me at a glance which have been fully completed and which still need work? Hardly "worse than useless"!

      --
      You must think in Russian.
  59. network performance by Ender+Ryan · · Score: 1
    Has anyone else seen absolutely abysmal network performance with the finder?

    We have several folders on our main webserver that contain several thousand files and folders, and OS X always craps out trying to browse through it. This doesn't happen with local files.

    This includes some save dialogs, such as Photoshop's, making OS X very difficult to use on our network. We resorted to making symlinks, based on the first letter of the directory names, into separate folders. eg. `folder2/b' would contain symlinks to everything in `folder' starting with `b'...

    Note, this is not a network problem, it is strictly with finder. Using the command line to view the files is not noticably slower than the local filesystem.

    --
    Sticking feathers up your butt does not make you a chicken - Tyler Durden
  60. Re:Full Mirror by Anonymous Coward · · Score: 2, Interesting

    google has permissions to cache content? proxy runners have permissions to cache content? mostly, no.

  61. BeOS? Is that you? by CableModemSniper · · Score: 1

    Live search folders? Arbitrary file-system meta-data? Come back to me Be!

    --
    Why not fork?
  62. Re:a better finder? by dbrutus · · Score: 1

    If you've been writing portable code, it shouldn't be that hard. The dev environment's included for free and for simple ports you don't need top of the line hardware. What kind of software are you porting over?

  63. you're so right by sweatyboatman · · Score: 1

    good point.

    and me without my mod points. oh well, guess you'll have to be satisfied with this little reply.

    I wanted to read that article. Something about the Spacial Interface. Incredibly less convincing when it's such a pain to read at all.

    --
    It breaks my pluginses, my precious!
  64. easy to use eh? by Anonymous Coward · · Score: 0

    Duplo blocks are much easier to use than, say, technic building toys, spatially speaking:

    Duplo fit the hands of the children using them, they are brightly colored, and they are simple shapes yielding a simple building experience.

    Technic has parts that aren't even blocks. They are difficult to handle by the hands of the kids that use them because the parts can be much smaller than fingers (springs, bands, gears). The parts available for building are complex and frequently unintuitive.

    So which is better, Duplo or Technic? I think Technic since you can't really do anything remotely creative or useful with Duplo unless you are a toddler.

    But there aren't any characters in technic with happy smiles, that make you feel warm and fuzzy inside, like in Duplo. Yeah, sadly, there are no stupid smiley faces on non-mac computers to let you know that the computer feels warm and fuzzy inside either.

    Grow up and start using the big boy toys.

  65. finally, someone who knows! by kraksmoka · · Score: 1
    but you left out the most wonderful thing about using Mac OS. it worked this way in classic and does it in X with a vengence.

    the Drag and Drop. yes, drag and drop is an art in Mac OS and in X you can drag any file onto any app running or not, to launch said file. it works like a champ. grab ten jpegs and drop them onto Photoshop, boom! grab a file with no extension and a blank icon, drag onto stuffit expander and that .tgzipped doc from some solaris developer's package magically unzips.

    --
    "You never want a serious crisis to go to waste." - Rahm Emanuel
    1. Re:finally, someone who knows! by drsmithy · · Score: 1

      Except for the rather nasty limitation (in Classic at least, OS X has a shortcut to circumvent it) that most apps refuse to open a file they don't recognise.

  66. Re:Full Mirror by remusrm · · Score: 1

    Not a real mac fan anymore, used to, heck I started on a Mac 6116CD, and it was fun. In 2001 after a long time into pcs decided to get another iMac was nice, just not as functional as I presumed. Mac OS x was on, tried it and liked it. The problem is that is kinda slow, also the finder is in need of speed, and some usability. I think they are like 2 years away from that, hopefully. I still use my IBM iSerrie 117-4MU and some old emachines, and I rather like them then the iMac.

  67. Low end/high end divide by IamTheRealMike · · Score: 3, Informative
    It's an interesting article, although most of the points related to OO (spatial) vs navigational browsing have already been hashed out on the Nautilus list, which I read sometimes - I think if you want a view of both sides of the argument, that might be a good place to go now, especially as the issue isn't as clear cut as this article makes it out to be.

    In particular, the navigational model has a few things going for it. Firstly, people have already been forced into it by the spread of the web. One of the most, if not THE most popular apps in usage today is the web browser. The web is clearly a navigational model, the browser is a viewport onto a small segment of the whole, with links between them. Clicking a link does not open a new window, and there is no enforced relationship between the website and the window. The concept of the "path" is forced onto the user via URLs, and the current path is constantly shown in a prominant place.

    In the OO model of course, you are only allowed to have one window showing a folder at any point - opening it from somewhere else simply raises the window to the top.

    Nonetheless, I have yet to find people who consider web browsers to be seriously confusing. The "spatial" model ties in with the physical world, but we deal just as much with the navigational model in the the real world as well, think TV/radio channels for instance.

    I think he also misses the fact that mental modelling is not an absolute - it can and must fit in with other considerations. The OO model may well be more spatial and perhaps more natural, but it has other problems as well, like the fact that you can easily end up with many small windows open at once. In the absence of any equivalent to the taskbar, such a thing always irritated me in MacOS 9. When you do have a taskbar of course, OO browsing simply fills it up very quickly making it useless.

    Not even virtual desktops can solve that problem. Virtual desktops of course have questionable usability in the first place, but in fact I've NEVER met anybody who disliked them, not even really green newbies. Virtual desktops make OO browsing even harder, because you can only have 1 window open at once for any given folder, if you open one, windows start jumping around from different desktops (unless you want to lock them together or place the window on multiple desktops at once - yuck!).

    As an example of where breaking reality might be faster than sticking religiously to an OO model, imagine for a moment you have X-Men style super powers. You want to retrieve a piece of paper, that is in a box, in drawer, in a cupboard. Which is faster, opening the cupboard, pulling out the drawer, taking out and opening the box, getting the piece of paper and then putting it all away again, or using X-Ray vision to find the paper with the power of your mind, then kinetically pull it through the walls of the cupboard to sit in front of you?

    A poor analogy, I'll admit, but what usability reviews often miss is that in return for some breakage of the mental model, you can get large increases in efficiency. Virtual desktops might well be unnatural, but once you get used to them you don't want to go back, no matter what your skill level is - perhaps people who'd never seen them before would get confused, but for everybody else the usability is enhanced, not decreased.

    I guess I should qualify that this doesn't mean I'm in the "lots of crack preferences" camp a la Mosfet and the gang, I mean each feature should be weighed carefully for its cost in usability loss to newbies vs the increase in usability once you have understood the system.

    1. Re:Low end/high end divide by Doctor+O · · Score: 1
      Nonetheless, I have yet to find people who consider web browsers to be seriously confusing.

      Look no further. We have hundreds of those on the phone every day. We have a web application which allows companies with dealer networks (like supermarkets, car vendors, travel agencies) to build ads and brochures online, completely conforming to the corporate identity during the whole process. All people need is an online connection and a webbrowser.

      And yes, there are thousands of dealers of a huge Japanese car vendor which call because they don't get how their browser work.

      I started this reply thinking this was funny, but I just realized that this instead is sad.

      --
      Who is General Failure and why is he reading my hard disk?
    2. Re:Low end/high end divide by northstarlarry · · Score: 1
      I think there's a pretty big difference between looking at websites and working with files on your computer.

      To continue to use the spatial metaphor (because I think it makes things clear), it seems to me that web browsing is like reading a magazine (you are jumping from content to content, whether it's pictures or words or movies), and navigating files is like going through your desk drawers. When you're browsing the web, you don't care too much about where the content is actually located relative to other content. But on your home computer, that's essentially all you care about. You're not so worried about the content until you're accessing it in an application. The TV/Radio channels you mention are the same -- content for which you're not totally concerned about the location relative to other content. Channel 31 appears in the same place as 65, but you don't need the two to interact at all. Picture-in-picture is about as far as simultaneity goes there.

      (I have to disagree with you about the prominence of the current path. Who cares what http://www.amazon.com/exec/obidos/ASIN/0674920015/ qid=1049329928/sr=2-1/ref=sr_2_1/104-0639604-93959 17 means? The point is that it's the book I've been looking for. That's what is taking up all the space in the window. I think the path is there as a convenience to those of us who can remember them.)

      If I want to move a piece of paper from one drawer of my desk to another, I open both drawers and move the paper (or open one, pull out the paper, and while holding it in my hand, open the other drawer and put the paper in). Is it simpler in navigational-style file manager/browser?

      You're absolutely right about going straight to the paper in the box with telekinesis. (I almost missed that you added X-ray vision -- you're talking about something like column view!) I don't think that has to break the model, though -- as long as you distinguish the column view ("X-ray vision") from the regular ("real-world") method. This is as simple as column view having a brushed-metal look (or something similar), and gives us the advantages of both worlds. . .I can find and grab a pice of paper quickly from the cupboard with my special powers, and then drop it into one of my desk drawers.

      There are a lot of things missing (windowshading, for god's sake!!!) and strange (what the hell is "Computer" window and why do all my drives show up there?) to me in OS X's Finder, having used Mac OS since I was about six, but there are new, navigational-style things that I _really_ like. The best example is Go To. . . with tab completion. I'm willing to go along with Apple for the ride on OS X (what am I gonna do. . .switch to Windows, or Linux that looks like Windows?), but I hope they read articles and discussions like this and give them some thought.

      I think the most important point from the article is that Apple needs to have a clear and coherent vision for their file management. If they had totally rewritten the Finder and it totally smoked, I would be there in an instant. But there's just enough left from OS 9, mixed with just enough new (to Mac OS) stuff to make long-time users feel a little funny (and I think that stuff probably affects newbies too, though I won't swear to it).

    3. Re:Low end/high end divide by drsmithy · · Score: 1
      And yes, there are thousands of dealers of a huge Japanese car vendor which call because they don't get how their browser work.

      Perhaps the problem lies in the web page they are accessing and not the browser. There is no shortage of web-based "interfaces" that break the fundamental ways that a web browser works.

    4. Re:Low end/high end divide by Drakonian · · Score: 1
      In particular, the navigational model has a few things going for it. Firstly, people have already been forced into it by the spread of the web. One of the most, if not THE most popular apps in usage today is the web browser. The web is clearly a navigational model, the browser is a viewport onto a small segment of the whole, with links between them.

      What about the rest of the article? After saying the basic finder should be completely spatial, he suggests a somehwat web-browser-like model to sit on top of the Spatial Finder. (Hence the name Finder Browser - but your term navigational is a good one. They should call it a Navigator instead.) Anyway, I think he is suggesting the best of both worlds.

      --
      Random is the New Order.
    5. Re:Low end/high end divide by Doctor+O · · Score: 1
      Perhaps the problem lies in the web page they are accessing and not the browser. There is no shortage of web-based "interfaces" that break the fundamental ways that a web browser works.

      I admit that I saw this reply coming, but I was too lazy to address the issue. *g*

      The interface is valid HTML designed using the KISS principle (knowing that the users to come are among the most stupid people on Earth). It's a handful of easy questions like "which kind of ad do you want" (leasing, special price, current campaign ads), how many colors should the ad have, which headline do you want, one question at a time and with only a handful of text links to click on. There's no huge chrome, no fancy effects, nothing which could confuse even the most stupid person. You click some text links and you are done. I had my six years old cousin do it just fine, and he had never surfed the web before as his dad won't let him (he doesn't get the web either, but that's another sad story).

      Yet it's too difficult even to enter an URL or press a back button. I can't go on about this without getting *really* insulting. Yesterday I had a call from someone who couldn't connect to the Internet because he had (intentionally!) unplugged his modem cable (of course he told me only after 10 minutes of insulting me). Needless to say, he had complained to the management of the Japanese company before, stating at length how much he was pissed off by our incompetence, so I had just another call from there later that day.

      Sorry for the rant, but I'm really sick and tired of things like this. Fortunately, this is only a very small portion of my job and I do phone support only occasionally.

      --
      Who is General Failure and why is he reading my hard disk?
  68. Re:Live search folders are amazing-vFolders by Anonymous Coward · · Score: 0

    You will also note that Evolution has vFolders. And yes, combining this capability with a database-like filesystem (ReiserFS) and Enlightenment 17, and Linux will go a long way toward usability.

  69. Re:Full Mirror by ydnar · · Score: 1

    When AOL's proxy servers go down, they take the internet with it, making the typical Slashdot effect seem like a mild inconvenience.

    I'm positive Ars has a large readership on AO...

    er, nevermind.

    y

  70. Subtractive vs Additive sources by Sosarian · · Score: 1

    A few things to remember.

    Monitors work by Additive colour sources (RGB).
    Paper works by Subtractive colour sources (CMYK).

    The contrast ratio on monitors is higher than on regular newsprint. This is one of the reasons that I find black text on a white background hard to read. In fact at small font sizes I find white on black easier to read.

    Redhat's man pages are coloured for black on white now making my man pages impossible to read with my default black backgrounds, side note anyone know how to turn this off?

  71. Much ado about nothing by BigBir3d · · Score: 1

    This is a very long-winded article with many rants, and little substance.

    In essence:

    1. Macs rule
    2. OS X sucks
    3. OS 9 is the shiznit

    The author describes what he/she wants. Which is fine. But a little organization on the users part goes a long way towards making things easier. UNIX is very particular in how it wants things placed. There is good reason for this; it makes things run faster and more reliably. Mac people understand this when talking about a visual interface (continuity) yet are absolutely against it when it comes to organizing files/folders. Why? Just because you have always done something one way, does not make it the best way to do it. Nor is changing it somthing else always the best way to do it. UNIX was designed by people who demand organization and intelligence; in short, it was designed by engineers. Not the 'software engineers' of today, but good old fashioned classicly trained pencil and paper engineers. They don't employ hacks, they do it the right way. The only way. The best way. Maybe not _all_ that, but they try. The people that make the decisions at Apple have seen the simplistic beauty of all of this. What worked in 1987 with 20-80MB of data is not the best way to do things in 2003 with 60-120GB of data that many people have to try to manipulate. Apple noticed that. Most of their "old school" users have not. If people can't make the jump from OS 9 to OS X, then keep using 9. Just don't bitch that Apple is no longer going to sell new hardware that supports OS 9. If OS X _needs_ to be fixed, than fix it yourself. If you can't, then learn. If you don't want to learn, and you want to bitch, then fine. Just don't expect compassion from the community for much longer. You can always try to get a job with Quark. ;)

    As to all the spatial stuff... geez! You want Safari to be your hard disk browser with a few flashy additions. Akin to Konqueror on KDE (hard disk and internet browser). To the author I say; "start coding."

    1. Re:Much ado about nothing by axxackall · · Score: 1
      In essence:
      1. Macs rule
      2. OS X sucks
      3. OS 9 is the shiznit

      Add here:

      4. Gentoo Linux rocks

      And you've got a very natural conclusion:

      5. Gentoo/PPC rocks and rules

      --

      Less is more !
    2. Re:Much ado about nothing by bnenning · · Score: 1

      Siracusa's comments are a bit unfocused, but I agree with much of what he said. I don't share his belief that spatial views are the One True Way (I'd be happy if Apple fixed the obvious bugs in the Finder and added a shelf), but he's absolutely right on metadata. His most insightful comment was that about half of iTunes and iPhoto is metadata management. This functionality belongs in the OS and filesystem, rather than being reimplemented in each app.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    3. Re:Much ado about nothing by cpt+kangarooski · · Score: 1

      UNIX is very particular in how it wants things placed. There is good reason for this; it makes things run faster and more reliably. Mac people understand this when talking about a visual interface (continuity) yet are absolutely against it when it comes to organizing files/folders. ... UNIX was designed by people who demand organization and intelligence; in short, it was designed by engineers. Not the 'software engineers' of today, but good old fashioned classicly trained pencil and paper engineers. They don't employ hacks, they do it the right way. The only way. The best way.

      Ah, no. The metric for usability is what the user finds best -- not the computer or the developers. If it's important for the computer to have things arranged in a particular fashion, then let it do that in a way that doesn't impede the user from arranging things in any way he wants. This is certainly not difficult, since the computer likely doesn't care about much above the inode level. Paths and filenames are all human conveniences. As an example, note the File ID Numbers that MacOS used. Rather than try to use a path and filename as a GUID, a real GUID was just assigned to each file. Users could name the file anything they liked, since the computer wasn't paying attention to that.

      Personally I can't stand the Unix directory structure. It slows down how well I can use the computer and it offends me. A default structure that is the most comfortable and efficient for users, but which can be trivially replaced by any kind of structure a user chooses to create for themselves is infinitely superior.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    4. Re:Much ado about nothing by BigBir3d · · Score: 1

      A hammer is a tool. There is a proper way to use it, and all the other ways. A computer is a tool.

    5. Re:Much ado about nothing by cpt+kangarooski · · Score: 1

      I agree. And when I want a doorstop, and a hammer is handy, it is a great tool for keeping my door propped open.

      The proper way to use it is whatever you need at the time.

      And a computer is great, because it is a tool that can act like a virtually limitless number of other tools, each different. Depending on user need.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    6. Re:Much ado about nothing by BigBir3d · · Score: 1
      And a computer is great, because it is a tool that can act like a virtually limitless number of other tools, each different. Depending on user need.


      I thought we were talking about the system layer, not the application layer. ie: "The stuff that makes it work..." Not the work itself.

      The point is to get away from a system that has 12 pointers to get at something. The shorter the list is for searching for a library that is needed, the faster that program can make its calls and get its work done. In Windows they call it "defrag" in OS 9 there was Disk Warrior (I think that's the name... defrag for macs basically). In UNIX, this is not necessary, if things are done properly, and the same way every time (think Slackware).

      The best way to do something is usally the simplest, right? I always think of driving a car, sure you can turn right 90deg 3 times and get the same effect as turning left 90deg one time (assuming equally spaced grid of 2-way streets), but what's the point? Use the system to your advantage...
    7. Re:Much ado about nothing by cpt+kangarooski · · Score: 1

      I thought we were talking about the arrangement of files and folders into particular directories, with particular names, of the contents of the hard disk.

      At at any rate, your point ignores something I was pointing out before. If a library's true GUID is 12345, a program calling on it need not search through directories more than the single first time it wants to find it. It just jumps straight to that GUID, regardles of where it is located.

      As for the purpose of defragging, I'd be amazed if it isn't needed on Unix systems, at least where people are creating and deleting, deleting and creating, files all the time. For defragging ensures that each file is a single block of space on the disk, and not spread about on the actual _sectors_.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  72. It's fun to violate DMCA... or not. by yerricde · · Score: 2, Informative

    Did you happen to get permission to host that article from Ars?

    Yes, from the U.S. government. A rider to the DMCA permits caching online content without the permission of the copyright owner in some cases.

    --
    Will I retire or break 10K?
    1. Re:It's fun to violate DMCA... or not. by Anonymous Coward · · Score: 0

      BAM! Yo go brotha!

      -Alex

    2. Re:It's fun to violate DMCA... or not. by cpt+kangarooski · · Score: 2, Interesting

      But probably not in this case. Read the safe harbor provisions more carefully, and in full.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  73. A better finder... by no+reason+to+be+here · · Score: 1

    would be the Tracker from BeOS.

    Well, maybe not in overall UI terms, but in terms of file management, it rocks. it's really nice to be able to search my hard drives for all mp3's from 1980-1989 excluding any from the Genre hair metal.

    of course, that has more to do with the underlying filesystem than with the trakcer itself. hopefully finder will be able to do those kinds of filesystem acrobatics when dominic giampaolo is done hacking on hfs+.

    1. Re:A better finder... by Mikey-San · · Score: 1

      So that leaves you with what, Cyndi Lauper?

      -/-
      Mikey-San

      --
      Mikey-San
      Karma: +Eleventy billion (mostly affected by watching Celebrity Jeopardy)
    2. Re:A better finder... by cpt+kangarooski · · Score: 1

      You dare forget about New Wave?

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    3. Re:A better finder... by Mikey-San · · Score: 1

      I try to, yes. ;-)

      -/-
      Mikey-San
      This signature was designed to increase your load time by 0.001 seconds. Enjoy.

      --
      Mikey-San
      Karma: +Eleventy billion (mostly affected by watching Celebrity Jeopardy)
  74. Why so mad at Cut and Paste in Finder? by EricHsu · · Score: 2, Interesting
    From the article:

    Furthermore, as astute readers have already figured out, the shelf eliminates any need for the perversion of interface metaphors that is the use of copy and paste for files. The "Edit -> Copy File" command now becomes "File -> Place on Shelf", and the "Edit -> Paste File" command now splits into two commands, "File -> Copy from Shelf" and "File -> Move from Shelf", making it more powerful that copy/paste (since "cut" is not an option) in addition to being more sane and consistent with the rest of the UI.

    Why the hostility? The "Cut" feature is practically the only thing from Windows that I miss in OS X. It's annoying to not be able to move files in OS X without dragging. Often you know you want to move some files, but say you get to the destination and want to make a new folder for them. This is incredibly annoying to do with OS X, but would be way easier with keyboard Cut as well as Copy/Paste.

    What is the down side to having a "Cut"? I assume there's some usability study that shows users messing up more with Cut around. But I find this hard to believe. Cut and Paste to a hidden clipboard is so ingrained in computer users that introducing an explicit "shelf" makes things more, not less complicated. In fact, OS X is going in the opposite direction... nowadays you can cut and paste almost everything to a hidden clipboard and it tries to sort out what you meant (e.g. copy a file and paste it into a text editor, or drag a file onto a terminal window).

    You can get an OS X version of the shelf mentioned (a kind of visible clipboard) at XShelf today. I have it around as a kludge for moving files more easily. But it would all be solved by having a "Cut" option as well as Copy and Paste.

    - Eric

    1. Re:Why so mad at Cut and Paste in Finder? by cpt+kangarooski · · Score: 1

      Well, I'd at least like some consistancy.

      If it is called Cut/Copy/Paste, then let it work within documents as well. If it's not going to do that, then call it something else, dammit.

      After all, who would want to drive cross-country, but have to adjust their speed with the windshield wiper control when they're in Ohio? Pretty similar thing going on here.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  75. Re:a better finder? by Anonymous Coward · · Score: 0

    This sounds like a statement from an Apple developers guide... "Why should YOU develop software for the Macintosh platform?"

    The sad thing is that people have come up with this argument because they've basically accepted defeat. Apple will never gain a larger market share if the developers decide they're doing it for the non-existant competition!! Competition is generally a good thing because it keeps you on your toes and makes your products better. Why else do you think that many Apple software titles are often subpar compared to the PC offerings?

  76. Re:Full Mirror by Karma+Star · · Score: 1
    quote from FAQ:

    " You've cached my web page. I don't want it cached. How do I get it removed?

    Caches are automatically deleted after 24 hours. If you want it done sooner, send an email to: redjar (at) redjar d0t org and I'll delete it as quickly as possible."


    They should consider keeping ads intact, though...
    --
    Me email iz skyewalkerluke at microsoft's free email service.
  77. What about readability? by kongjie · · Score: 1
    Someone already commented on the longwindedness of the article, and someone else objected to the color choices.

    I went to the article to find out what exactly these wonderful modest proposals for the finder were...and I gave up after four pages. I've got a to-do list that doesn't spare me enough time to read such exhausting prose.

    Why not put the new wonderful ideas for the finder FIRST, then spend the rest of the dictionary defending/supporting them?

    1. Re:What about readability? by Anonymous Coward · · Score: 0

      Because he doesn't have any "new wonderful ideas."

      He simply is all "This isn't Mac OS 9. I don't like this. It should be exactly like Mac OS 9."

      I came out of that article wondering why in the heck he doesn't want the same file showing up twice in two different windows. Believe it or not, I wished for that kind of thing sometimes in Mac OS 9. Glad to see it in X.

      I'm still trying to find out exactly what he meant other than "This isn't what I'm used to! Give me back the old way!" Someone correct me if I am wrong, but that is all there is to the article. If there is more to it, than he is a crappy writer and shouldn't be writing anyway.

  78. What apple is missing by azav · · Score: 1

    Apple in the beginning was obsessed with the details. And this matters because the structure behind the details was right.

    So what is wrong? Finder windows.
    In OS 10, the finder windows could be open in the background and they would update live and pretty damn soon! you could organize them so that the most recently added or updated windows listed their files at the top of the window, a godsend if you had a window you (or someone else) were saving files to.

    What happens now? If the window is open, you must click on the/a file to see the contents update and reorder themselves. Damn useless if you ask me.

    What is equally as bad is the new columnar windows with support for long filenames. You can not individually drag the columns to make long filenames fit AND you can not sort the contents be "most recently" modified.

    Also, finder window contents are not remembered unless the window is closed, so setting a window to list view and then opening another folder within that window FORGETS the settings you just gave it. Infuriating to have this happen with every window. Makes you want to use the old finder window system since that actually remembered what you told it!

    Sure, OS X doesn't crash like the Mac OSes before it but usability of several areas has taken a SERIOUS hit.

    What is worse is support for samba (windows) shares. If the contents of a window have changed on the share you have visible, you must remount the volume and repoen the window to see the new contents!

    I'm a mac user since 1985 and my g3 266 booted to OS 8.5 seems to act crisper than my 1G Ti with regards to UI responsiveness.

    In some ways, it feels like OS X is a user hostile unix command like with a sluggish gui tacked on.

    It's hard to like a new IU like this when whenever asked to comment about it, your comments turn into a bitch session. Makes you wonder if apple's engineers are really wondering about the details.

    I am sad.

    --
    - Zav - Imagine a Beowulf cluster of insensitive clods...
    1. Re:What apple is missing by prockcore · · Score: 1

      What happens now? If the window is open, you must click on the/a file to see the contents update and reorder themselves. Damn useless if you ask me.

      YES! I have an iMac sitting on my desk that I use from time to time, and this is the one thing about OSX that I absolutely HATE. I save a file from a webpage and I don't see it on the desktop, and it confuses me.

      The fact that finder windows (and the fucking desktop) don't update unless they have the focus proves that Apple no longer does usability tests.

    2. Re:What apple is missing by Anonymous Coward · · Score: 0

      What is equally as bad is the new columnar windows with support for long filenames. You can not individually drag the columns to make long filenames fit

      Hold down the option key while you resize the column.

  79. Integrating Finder with Terminal by Fermata · · Score: 2, Interesting

    One of my half-baked ideas for a Finder enhancement (that may or may not be able to survive the transition to fully baked), would be to somehow integrate the Finder and Terminal applications into a single user interface.

    When accomplishing a task, it is sometimes more convenient to use the Finder's graphical user interface. Other, generally more complicated, tasks require the use of the Terminal's CLI. To perfrom a sequence of tasks, I often find myself switching back and forth between one or more Finder and Terminal instances to get the job done. If the two applications were combined into one, the transition between GUI-oriented work and CLI-oriented work would not be as mentally disconcerting. In addition, the strengths of both approaches could be combined to offset their weaknesses.

    The Terminal would be embedded in the Finder as a splitter pane above or below the graphical view of the file system (according to user preference). The working directory of the Terminal could either be linked to automatically update during point-and-click navigation through folders or decoupled with a sync-to-current location button provided to update the Terminal's working directory. Special "pipeable" objects would be provided to redirect the results of Terminal commands to the current GUI view.

    Here is a simple example to illustrate this:
    1.) The user opens a new Finder window and navigates to a folder using the GUI.
    2.) The user types a command in the embedded Terminal: ls *.log | FinderView.
    3.) The results of the command are piped to the Finder's current view and presented graphically.

    Obviously, there are many issues that would have to be resolved to make all of this work properly, but I think it would be worth the effort to create a hybrid CLI/GUI Finder-like application.

    1. Re:Integrating Finder with Terminal by hey · · Score: 1

      There is something like that -- based one Mozilla.
      Called XMLTERM

    2. Re:Integrating Finder with Terminal by spitzak · · Score: 1

      Drag & drop from the finder into the terminal types the full path name into the terminal. This is quite uesful for "integrating" them.

    3. Re:Integrating Finder with Terminal by cpt+kangarooski · · Score: 1

      Yeah, I've been saying this for a long time. The commands would all need to be renamed for consistency -- rm doesn't square with the Trash, or the absolute need for undo in every situation possible, for example. mkdir doesn't gibe with New Folder either. You get the idea.

      But I'd integrate them entirely, rather than use pipelines. And then build in better mouse support. In fact it still boggles the mind that you cannot do a click on a command in a shell to get a menu or dialog of options for it, clearly explained, or contextual help, or anything.

      Then it stops being surprising when you remember that no one has bothered to improve CLIs seriously since scrollback was fixed. I say 'fixed' because the old terminals that printed stuff out instead of displaying it on screen had scrollback -- you looked at an earlier point on the printout!

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    4. Re:Integrating Finder with Terminal by torpor · · Score: 1

      You might find Launchbar handy ... check Versiontracker.

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    5. Re:Integrating Finder with Terminal by sharl · · Score: 1

      Looking at this from a slightly different perspective, I think we should be able to create finder windows and log them in as different users. If I need to be log in as a different user to access part of the filesystem, I'm not sure if there's a good reason for not being able to do it directly in a window. Close that window and it's logged out.

      --
      Clearly I have too much time on my hands.
    6. Re:Integrating Finder with Terminal by andrewski · · Score: 1

      In fact it still boggles the mind that you cannot do a click on a command in a shell to get a menu or dialog of options for it, clearly explained, or contextual help, or anything.

      Huh? The shell is there for you to use if you know what it is, and how to use it. It would be a neat hack to be able to click on a command*, but it probably wouldn't end there. I really can't stand feature creep, except in KDE. Not only would this lead to other features, but might encourage bad habits. Instead of using whatis, apropos, and man to find out about a file, you will be dependant on using the mouse.

      The rest could be done with a local "applications" folder which is just soft links to normal executables.

      * - What the hell? You are assuming that one would know to type
      ls /usr/bin
      and then use scrollback, (and click on something probably not even on the screen, as far as the tty cares) but wouldn't be able to to a simple
      apropos partition
      man fdisk

    7. Re:Integrating Finder with Terminal by cpt+kangarooski · · Score: 1

      That's the most asinine post I've seen in a while.

      Computers are here to make the lives of their users easier. There is absolutely no good cause for a computer to be designed in a way to be deliberately difficult to use. Nor for it to be designed in a way that happens to be difficult to use if it can be more approachable without impairing function.

      Your bad attitude has been something that has been outdated and worth eradicating since microcomputers first started appearing, giving ordinary people resources that previously hadn't been extended to them by smug, superior acolytes of mainframes and minis. (Though to be fair the developers of timesharing minis were nothing like you, wanting to also make computers available to more people)

      And if you don't like feature creep, I suggest you abandon shells altogether. Real men toggle switches on the front panel, you asshole. Actual alphanumerics are a luxury.

      I really don't see much point in a complete shell -- at best it's a last resort option when there's not enough bandwidth available for a remote GUI. But textual commands do have their uses, particularly with regards to certain types of selection for other commands to act upon. (Though note that GUIs are superior in other types of selection)

      But the CLI that ideally would be present would have to be as full-featured as the rest of the OS's UI.

      Commands should be named and used consistantly regardless of how they're accessed. They should take full advantage of GUI resources -- for example, hovering the mouse cursor over a CLI command should spawn a tooltip or some other useful contextual help, just as it would if you did the same over a GUI button or menu entry.

      Unlike the abyssmal help provided in most shells -- such as the awful, awful man pages -- help should be provided in parallel and not in series. A user that wants to refer to the help while in the middle of a command should not have to lose it, nor execute it in a half-baked state, nor jump through hoops with 'saving' it to the clipboard or to a file. A really good help system (see the AppleGuide from MacOS circa v7.5) will walk a user through particular functions, rather than simply referring to them and counting on the user to remember what to do for each step.

      And output would typically be through the GUI. The CLI I imagine is merely a single input line. Perhaps similar to an address field in a browser window. There's certainly not much in the way of purely textual output that I can see a shell being good for. The superior formatting of a display that can show graphics and non-monospaced type makes that perfectly clear right away.

      As for the mouse, so what? Mice are here to stay, at least until a better pointing device comes along. And if you're such a bonehead that you insist on not using a mouse, I'm sure that keyboard shortcuts can be implemented.

      At any rate, this is a totally new CLI I'm looking for here. Bash, or tcsh, or all that other crap that couldn't find usability with both hands and a flashlight need not apply.

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
    8. Re:Integrating Finder with Terminal by andrewski · · Score: 0

      Computers are here to make the lives of their users easier. There is absolutely no good cause for a computer to be designed in a way to be deliberately difficult to use. Nor for it to be designed in a way that happens to be difficult to use if it can be more approachable without impairing function.

      Computers are actually here to accomplish a myriad of tasks, not just to make users lives easier. I don't think that the shell was created to be deliberately easy to use. And, I think that GUI-ifying the shell would impair function.

      How did you decide that I was against usability? I am just saying that tacking a bunch of shit onto the shell until it becomes like the Finder (only more confusing) is a pointless endeavor - we ALREADY have the Finder.

      And if you don't like feature creep, I suggest you abandon shells altogether. Real men toggle switches on the front panel, you asshole. Actual alphanumerics are a luxury.

      Nice attempt at levity, prick.

      I really don't see much point in a complete shell -- at best it's a last resort option when there's not enough bandwidth available for a remote GUI.

      Are you retarded? Yeah, every time I fire up a Terminal, I think to myself "Well, this is it. The last resort." - Wait! No, I don't! The GUI can be superior for certain tasks - taking the redeye off the picture of Grandma or video editing. But when it comes down to renaming 10000 files from all caps into small caps, the gui falls flat on its ass.

      Unlike the abyssmal help provided in most shells -- such as the awful, awful man pages

      If you con't read a manual page now, why do you think that making it clickable would suddenly expand your obviously small attention span?

      And output would typically be through the GUI.

      Breaking the pipe forever.

      As for the mouse, so what? Mice are here to stay, at least until a better pointing device comes along. And if you're such a bonehead that you insist on not using a mouse, I'm sure that keyboard shortcuts can be implemented.

      The mouse almost worthless in the shell. It works for selecting / pasting text. Unless there is a bunch of text to copy, or it is uniquely formatted, it doesn't get touched.

      Why even bother with the CLI? Why not just drop files onto icons like you already do?

      It seems that your main complaints are
      1) You can't seem to be motivated to read the manual.
      2) You want to click on your help (again assuming that you can find the /bin directory)
      3) You can't seem to find any legitimate use for the CLI except as a GUI replacement.

    9. Re:Integrating Finder with Terminal by cpt+kangarooski · · Score: 1

      Computers are actually here to accomplish a myriad of tasks, not just to make users lives easier.

      You want to name one that doesn't make some users' life easier? I certainly cannot think of a single example. Certainly not, when you consider that you essentially just said that computers do tasks that humans are wholly incapable of doing themselves or through other means, or that while computers don't do anything new, that they make it harder than it would be otherwise.

      If a computer made something harder for you than it would be if you did it yourself, why would you use the computer? I mean, I guess a masochist might find that appealing, but that's hardly the typical case.

      I am just saying that tacking a bunch of shit onto the shell until it becomes like the Finder (only more confusing) is a pointless endeavor - we ALREADY have the Finder.

      Ah, you persist in thinking of the Finder and the shell as two separate things. What I'm saying is that generally there are times when a GUI is a useful interface to any aspect of the computer and times when a CLI is a useful interface to any aspect of the computer. I'm saying that both should be used in tandem as useful methods of interfacing with the computer where appropriate.

      For example, a number of people desire voice control over computers, even in graphic-heavy applications. Voice interface is very similar to a command line interface, apparently. Thus I see nothing wrong with a user interfacing with Photoshop by means of a GUI or means of a CLI, or better yet, having both options available and then using whichever is best in any given situation.

      Because the determination of which method of interface is superior will tend to vary based on any specific command and not just the overall use to which the computer is to be put, this demands having both available at all times -- i.e. a single interface that uses both GUI and CLI methods, with the choice of which to use at any _instant_ being the user's. As opposed to having a graphical program, or otherwise having to use a shell to get at it.

      The GUI can be superior for certain tasks - taking the redeye off the picture of Grandma or video editing. But when it comes down to renaming 10000 files from all caps into small caps, the gui falls flat on its ass.

      And this is precisely why I've been saying that we need to have both. But the mere fact that accepting textual commands might be superior DOESN'T MEAN that the CLI must forgo the superior DISPLAY of a GUI.

      For example, if you want to enter a command into the CLI to get via ftp all files beginning with the letter 'a', that's fine. But the typical CLI ftp program has crappy-ass output, even with hashes turned on.

      A GUI progress indicator listing queues of successfully retrieved files and files awaiting download, speed of the connection, progress of the download generally and the current file specifically is much better, and can best be achieved graphically.

      I wouldn't be calling for CLIs and GUIs to be integrated if I wasn't well aware of the fact that GUIs are best for some tasks and CLIs best for other tasks.

      Breaking the pipe forever.

      You really think that there's no way to preserve piplines? Feh. I'm confident that it's easy to handle. Particularly since there's nothing that says that the output that human beings want to see is the same as the output that they want sent to other programs.

      The mouse almost worthless in the shell. It works for selecting / pasting text. Unless there is a bunch of text to copy, or it is uniquely formatted, it doesn't get touched.

      It is worthless because it isn't being used. People manage to use mice all the time in word processors, and they involve a lot of typing as well. The trick is that, at least since good word processors started to appear on the Mac back in the 80's (MacWrite, Word, etc.) people used the damn thing instead of relying on various textual control codes, and such.

      Us

      --
      -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  80. Interesting by Phroggy · · Score: 1

    I was surprised to see the request for "live search" folders. This seems to me like an advanced feature that novices won't know how (or want) to use, and most people will have only one of them. And, I think it would complicate the Finder's interface.

    The behavior he describes for search results is pretty much exactly the same as what you already get with the Search Results window. I think the idea of saving search criteria is just fine - I doubt I'd use it much myself, but as he said, some people want this feature, and I can understand that. Fine - add a "Save Criteria" button to a search results window (so you can save the results AFTER searching, to make sure your criteria are what you want before saving). It would be nice to be able to drag something out of the window onto the Desktop or into a Finder window as well, like I can drag the icon to the left of the address bar from my web browser to save a bookmark of the page I'm on. Wouldn't be difficult to do.

    I completely agree with his view of the file browser. There was an old shareware app called Greg's Browser, by the same guy who made Kaleidoscope, which was a column-based file browser exactly like what we're talking about here. It was a seperate application, and the (spatial) Finder was still there, and there could be no confusion between the two. The Mac OS X Finder needs to abandon the notion that any window may be toggled between spatial (icon or list view) and browser (column view). A browser window should be a different kind of window that can only be a browser window. Double-clicking a folder in a browser window should open that folder in the spatial Finder. A contextual menu item, toolbar button and keyboard shortcut in a spacial Finder window should open a new browser window (or with a modifier, reuse an existing browser window) with the current folder or file selected.

    It should not be possible to open the Desktop folder in the spatial Finder, because it's already open on the Desktop. No reason you shouldn't be able to open it in a file browser though.

    I like the shelf idea, and I agree that copy/pasting files needs to go away. Not sure about the implementation though.

    Definitely like the idea of view plugins; Windows XP does some interesting things with views. Again, not entirely sure about the best implementation. I believe XP chooses the view based on the contents it detects. XP also reserves part of the window space to show information about the selected item(s); the Mac uses a column for this in column view.

    Overall, he's got a lot of good points, and interesting ideas. Sadly, I have little faith that Apple will do the right thing. I hope they surprise me.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  81. Re:Full Mirror by Anonymous Coward · · Score: 0

    "We kinda need that info if we?re going to continue to provide free content. "

    selling user information should be a crime

    have a shit fit y don't you

  82. Where OS X "Finding" really falls down... by frenchgates · · Score: 3, Insightful

    The Open/Save dialogs.

    Under Win2K I can do the following in the open/save dialogs:

    * Customize my view style (icon, list, etc)
    * Filter visible files by my own criteria
    * Directly manipulate (move, rename, delete, etc)
    * Right click to do things like compress the file before choosing it
    * Sort by other than name
    * type first letter to jump to file
    * quickly see where in the hierarchy I am all at once

    These are not trivial features but they would be trivial for Apple to implement.

    Too confusing for the neophyte? Give us an expert mode, please.

    --
    Syntax error: loose != lose, affect != effect, then!=than
    1. Re:Where OS X "Finding" really falls down... by tuxedobob · · Score: 1

      Under Win2K I can do the following in the open/save dialogs:

      * Customize my view style (icon, list, etc)

      Um, with all due respect, I don't think that's necessary for open/save dialogs

      * Filter visible files by my own criteria

      That's something that's always pissed me off about Windows. I'm in a folder; I want to see the folder. All of it. Especially if I want to open something and the application's default filter doesn't think I even want to see it.

      * Directly manipulate (move, rename, delete, etc)

      In other words, the Finder should be in each dialog box? No.

      * Right click to do things like compress the file before choosing it

      Uh, compress the file before opening it or before saving it? That doesn't make any sense.

      * Sort by other than name

      For saving, that's unnecessary. For opening, that's what the Finder's for.

      * type first letter to jump to file

      Actually, you can. Just make sure you're dealing in the list view and not in the "Go to:" box. And you're not limited to only the first character.

      * quickly see where in the hierarchy I am all at once

      Well, you could scroll left.

      Actually, what I want back are open/save dialogs that work exactly as they did in 9, but with the extra Cmd-Shift shortcuts. I could swear I used one recently, but I forget which application I was in. I think it was one that implemented them as sheets (as apps are supposed to).

  83. panties-wad-no reason by Anonymous Coward · · Score: 0

    Mostly you are complaining about an adobe problem specifically, not a mac problem. And if the older app is working, not a lot of reasons to switch, is there? There's some reasons, but you can still run the older apps on newer faster equipment. The RAM part is real, macs have always needed maxed out ram to be efficient, or "more" efficient, makes all the difference in the world, and then tweaking your memory management, ie "learning more than the basics". You'll still have problems, so what? All computers, operating systems, applications have problems, ALL of them.

    And sure, it had negative aspects to the classic OS, I'd admit that readily, but so what? It had and has both, overall all things considered it was a decent OS. Like I said, years and years on the net, no nothing but running the stock OS, never got owned, watched my friends deal with broken computers, broken this, viruses, getting owned and trojaned, getting this or that,and setting irqs to get something to work? huh? I used to think what the heck is that and why do you need to set it? My windows friends were always complaining about that and some "corrupt registry" and what not I never even knew or cared much about. oh, but they saved a hundred dollars or two hundred, well, so they did, then they spent hours every week fixing busted stuff. And stuff like that there. Me, nada, never happened. Buy a printer, stick it on, it worked, buy a cam, stick it on, it worked, buy a modem, stick it on it worked, yada, yada, yada, do this or that, worked. Once in a while a bomb, sure, MOSTLY with netscape that I recall. That's just personal anecdotal but it's true, too.

    I've found people with lots of problems (any computer) tend to not really learn their system, just a few applications. big mistake, IMO. Some computer users are like that, and it doesn't matter what OS they are using. You can't compare geeks or near geeks, the step above a raw user, with "application drivers", on any platform or machine. "Application drivers" are classed as low level users, nothing much more than that, even if they sit in front of a screen all day at work with a computer,do it for years, and they rarely learn to do anything different or really make an effort to get the most out of their machines. Just is reality, it's not a put down or anything like that to anyone, and it'sd always applied to all OSes and still does today.

    I also see the parent post was a troll, oh well, thought I'd drop a few tips, I run linux and mac classic, I like both for different reasons, and NO way do I get rid of old mac hardware, whereas any generic peecee running anything I have no problems with selling/giving away, getting new. With macs, I save them, buy a newer one once in awhile. It's because.... I dunno, just like them way more than any normal gadget you might buy.

    And so many other mac people are like that there's something to it. If you don't get it, or don't agree, it doesn't mean anything, it's no biggee to anyone else.

  84. Only because Apple no longer sells Mac OS 9 by yerricde · · Score: 1

    OS X has (IMHO) the quickest, simplest, and most elegant 'finder' [aka GUI] available today.

    The point of the article is that your statement is true only because Mac OS 9 is no longer available.

    --
    Will I retire or break 10K?
  85. you are a bitch by Anonymous Coward · · Score: 0

    fuck you

  86. Simple Finder by buckhead_buddy · · Score: 1

    I admit that I found Mac OS X's finder very confusing when I switched to it. Two things that drove me crazy were:

    1) Having my documents folder 4-5 levels deep.
    In OS 9 my documents were only two to three levels deep at most.

    2) The whole "group" system of domain organization.
    Fonts, applications, documents, and settings can be set up to be used just by certain people. This is a fantastic improvement over Mac OS 9 where everyone had universal access to the disk. Sure there are ways to break this security but the organization this provides on a multi-user box was badly needed. Unfortunately, it's a major shift from the way things were done in Mac OS 9 and it's not the easiest thing to learn. I've heard more than a few users ask "Where do I put my fonts? there are four different font folders!" But having different domains is pretty simple once you get the hang of it. Apple tried to implement domains in previous Mac systems with products like At Ease and Simple Finder but had horrible problems because Mac OS was single-user system.

    The Simple Finder in Mac OS 9 got a horrible reputation because it used "behind the scenes" trickery to force apps to save, open, and navigate just to the special areas that it was showing the user. It was slow and it often caused an app to break because it expected to be operating on a single-user system with universal disk access.

    In Mac OS X, the Simple Finder is much friendlier and more permissive in what it allows you and your apps to do (since Mac OS X is a multiuser system). It does some of the things that John wants his "spatial finder" and even though it uses "behind the scenes" trickery to give a different view to the user. It doesn't have the same problems that older Mac OS's did because the system and applications already know how to deal with multiple users on a controlled access file system.

    My mom might think it odd that ls in terminal is different from the folder organization she sees in the Simple Finder, but as long as it doesn't confuse the shell scripts and apps she uses she probably doesn't care.

    For the power-users, I think there current Finder is about 70% there. For novice users, I think the Simple Finder is about 90% there.

    While I think it might be a cool idea for Apple or a third party to come out with a Less Simple Finder, I think what John is really advocating is the chucking of the user / group system for the simplicity and consistency of the Finder of old.

    Personally, I'll gladly trade labels and popup folders and some of that simplicity for the nifty organizational advances of the new finder (and column view :-)

    1. Re:Simple Finder by foo12 · · Score: 1

      But your documents are only a couple levels deep --- from your home directory

    2. Re:Simple Finder by Anonymous Coward · · Score: 0

      A very basic problem with the OS X Finder is that it shows the "root" harddrive icon on the desktop, where it also should show an icon for your home dir.

  87. Open foot.... by WegianWarrior · · Score: 1

    ...insert mouth.

    Burn me at the stake if you wish, but much of what he describes as improvements on the Finder (which I recon is akin to the Explorer in Windows - I've used some Macs in the past but not picked up the lingo) are already present in the OS we all love to hate; Windows. Been there from 9x too - along with what he seems to dislike; pathnames. Whats so wrong about knowing where you put your file?
    I guess much or most of what he yearns for are present in the various flavours of Linux / FreeBDS / other open operatingsystem of choice (I'll admidt it, I don't have that much experience in those either) as well. maybe the Mac isn't as great as the Mac-fanatics tries to make us believe?

    --
    Everything in the world is controlled by a small, evil group to which, unfortunately, no one you know belongs.
    1. Re:Open foot.... by squiggleslash · · Score: 1
      The bit that amused me was that most of what he yearns for is actually in Mac OS X's Finder, it's just they're not switched on by default.

      Selecting Finder->Preferences and checking "Always open folders in a new window" (misleadingly labeled, as it will merely raise to the front windows for folders already open rather than open a new version), followed by a swift running around turning off toolbars, will generally turn the thing into a traditional Finder. Icon and window positions will be saved, just as expected. There are minor annoyances - clicking on the Finder in the dock when no Finder windows are open will cause the Finder equivalent of "My Computer" to appear - the same happens if you reboot and had open network folders, each window will be replaced by the "My Computer" default.

      But is it spacial? Of course it is. It probably isn't as up to date as Mac OS 9.2, but I can't recall a feature I was using in System 6 (the last I used before going on a Mac hiatus) that isn't in Mac OS X.

      --
      You are not alone. This is not normal. None of this is normal.
  88. Re:Full Mirror by Caesar · · Score: 2, Informative

    Nope, but then they didn't modify the source to our copyrighted pages, either. Slashcache surely didn't do it on purpose, but the caching process broke the ad code. For all I know, maybe our code isn't all that portable, who knows.

    In any case, I've talked to Jared, the man behind Slashcache, and he was exceedingly cool about the whole thing.

  89. Re:a better finder? by Anonymous Coward · · Score: 0

    He said VENDORS not customers you jackoff. Why don't you go kill yourself now?

  90. Spatial Finder, etc. by thatguywhoiam · · Score: 5, Interesting
    The article is pretty good at explaining the idea of a Spatial Finder, but I think that a lot of people give this idea too much credit.

    My impression is that, when Mr. Siracusa speaks of spatial orientation, many times he is actually referring to basic consistency.

    First points: labels and pop-up windows are a bit of a moot point, as they are coming in Panther. (Yes, I've seen builds.) So don't sweat it.

    Spatial qualities are useful; however they are just that, qualities. The original Finder was very much in the vein the author describes; a window was a folder which contained icons that were your files. The current iteration of OS X, I might point out, pretty much sticks to this as long as you have the toolbar collapsed (that underused widget in the right side of the toolbar). Collapsing this toolbar will give you something very very similar to what we had before. Furthermore OS X takes it even futher with the use of packages - I'm surprised he didn't mention this - which allows whole applications to keep their guts in one place. Therefore the icon is the application now, as well. I could see Apple taking this further: imagine being able to install a Photoshop plug-in by just dragging it onto the single Photoshop icon.

    Now, as far as spatially oriented interfaces being insufficient for the task of managing many thousands of files... there is something to that. The old Finder would have absolutely choked on certain computing situations common now (giant nested MP3/photo folders, for instance). It just doesn't scale to that many files cleanly.

    Having said that, it shouldn't have to. A user generally has far fewer abstractions they are mentally adhering to than what is presented in your interface. I think this is where half-baked implementations like favourites really fall down. Favourites is a great idea. When you save something, or move something, you are generally thinking about the project you are working on. Odds are you have one master folder for this project, with several sub-folders divided the way you like. The data contained within these folders takes various forms (text, code, media). Depending on what kind of work you are doing, one 'view' that is entirely appropriate for say, code, is not appropriate for graphics previewing. You want to work in the view that is appropriate, and have it 'stick'. You don't want to drill through 'My Computer -> My Documents -> My Whatever' to get to it, if possible. This mixing of standard OS bits and pieces with your actual 'work' files is what causes people to lose their work in some loopy abstraction. While the idea of just having a filename field and a pull-down for a Save dialog is great, people just don't take the time to define Favourites as they are quite used to simply creating folders when they need them, and then navigating each time to that folder. OS X could do a better job by remembering which folder you last saved to, no matter what. I hate it when Flash constantly thinks I want to save Flash projects in the Flash application directory. If you could tell the OS, when you create a folder, that is is a project folder, and have it automatically add it to your Favourites (I like 'Projects', can you tell?), that would be spiffy.

    So Mr. Siracuse's idea of Finder plug-ins is sound. I might just add that you only really need one plug-in, QuickTime, which can handle damn near anything you throw at it. What QuickTime can't catch, Quartz sure can (i.e. previews of PDFs and other vector artwork). The idea that the Finder should be an end-all to every kind of work is somewhat mad. The author's ideas about metadata are great, and I also think Apple is working on this (that Be guy they hired). I'm not sure about abstracting the Finder to a true 'browser' even more, I can't make up my mind on that. What I don't want to see is a schizo metaphor like Windows, where you have two distinct ways of browsing and no preference given to either (i.e. re

    --
    If Jesus wants me it knows where to find me.
    1. Re:Spatial Finder, etc. by Apotsy · · Score: 1
      Now, as far as spatially oriented interfaces being insufficient for the task of managing many thousands of files... there is something to that. The old Finder would have absolutely choked on certain computing situations common now (giant nested MP3/photo folders, for instance). It just doesn't scale to that many files cleanly.

      You couldn't be more wrong. I've seen people with thousands of files in a single folder on the classic Mac OS that they were able to navigate just fine. List view and type select made it easy to manage huge numbers of files. It didn't "choke". It scaled.

      Every time I see somebody who thinks they've got the "serious work" situation that breaks the old-style Mac Finder, it turns out they just think it can't be done because they've never seen it done.

    2. Re:Spatial Finder, etc. by thatguywhoiam · · Score: 1
      You couldn't be more wrong... Every time I see somebody who thinks they've got the "serious work" situation that breaks the old-style Mac Finder, it turns out they just think it can't be done because they've never seen it done.

      Ah, but you get me wrong, dude. (and, you're preaching to the choir I might add.) I wasn't refering to Finder Classic's ability to display several thousand files at a go, it's more than up to that; I meant that, considering the very heavily nested nature of your typical iTunes/iPhoto folder structures - which is something that will become increasingly more common under OS X - using Classic Finder would be really cumbersome in these situations. You're gotta pick between a pile of windows (and I mean a pile of windows), or one gigantically long List View, all tree'd-out to hell and back.

      Column View is made to address this very thing. I love Classic Finder as much as anyone but it was not ever designed with the sheer numbers of files in a UNIX. At a quick count I just did (system disks only) , my OS 9 partition weighs in at around 4000 files. OS X is somewhere over 30,000. Kind of a lame example but you see what I mean hopefully.

      --
      If Jesus wants me it knows where to find me.
    3. Re:Spatial Finder, etc. by Anonymous Coward · · Score: 0

      I agree, completely. What you really mean is not the number of files (documents, etc.) but levels. If you have 30000 files in a flat filing system classic finder would be fine (bit of a b*gger to scroll down but usable(...ish)) but if those 30k files are in a tree 20 levels deep then the old classic finder would start to get in the way. Column view, in my experience gets past that, well mostly.

      Nick

    4. Re:Spatial Finder, etc. by cannedbrain · · Score: 1

      command-option-arrow up/down will close the previous window as opening a new sub/parent directory. But I agree, nothing beats column view.

    5. Re:Spatial Finder, etc. by Anonymous Coward · · Score: 0

      yeah, but who goes surfing around the studpidly deep os and itunes folders like that; nerds thats who! real nerds just like me and you who make up 2% of the real world users. most people have more like few hundred files over maybe a couple dozen folders that they really ever need to look at.

      the real thing that pisses me off about the jag finder, is that it almost* saves state. i find myself constantly closing the toolbar, somehow it just doesnt die, and folders are constantly losing thier save state. this is especially true with file server, i use both afp and smb. the mixed browser/spacial finder is a pain in the ass. i dont want to keep telling it how i like to see things. and none of the view options preferences that we currrently have ever really stick, or work in a way that is simple enough to explain on a napkin. its just a pain.

      the only real part i think needs to stay spatial, and constant is the last view mode (list, icon, etc) and the window size. the browser method wastes so much screen space for most folders that have a few files. i want those windows smaller, but then if i make it smaller, in the browsing mode, i'm screwed for a those with a lot of files. thats the major crux for me, one window size doesnt fit all.

  91. quitting the finder by Yesterday · · Score: 1

    "It runs all the time, you cannot quit it."

    actualy in Mac OS X you can quit the finder. using a tool like TinkerTool to put the quit command in the file menu. I can quit the finder and run a terminal window and pretend I'm using BSD.

  92. Re:mac problem by 4iedBandit · · Score: 1

    You've got something else wrong with your system. There is no reason transfering a 17 Meg file should take that long, even on an old machine. I could do a comparison from my 7500, but I reloaded it with NetBSD a couple years ago and don't have a bootable OS 9 disk....

    --
    "The avalanch has already started, it is too late for the pebbles to vote." -Kosh
  93. Re:Full Mirror by Anonymous Coward · · Score: 0

    It's behavior like Slahdot's that (sadly) makes me believe we actually need DRM legislation. Copying and using digital content that you have no rights to is far too easy and more widely abused every day.

    The sad thing is that Ars was never even contacted for permission. It would seem like common courtesy and could have avoided any bad-blood that may now exist between the two.

  94. Fantastic article by extrarice · · Score: 1

    Precicely sums up every complaint I have had with MacOS X's interface.
    Reading the bit on Copland was a trip down memory lane - it had so much potential. It's a shame that the project was canned.
    Though, for what it's worth, BeOS has an implementation of "live search folders", in a fashon. You can save a file query as a document, right-click on it (or double-click it), and get a constantly updating result list. Add to that the ability to search on file metadata, and it was file-searching nirvanna. Pity Be, Inc. is dead now. That OS had real potential.

    --
    "Jesus saves, but everyone else in a 10 foot radius takes full damage from the fireball."
  95. interfaces are personal, make them configurable by Anonymous Coward · · Score: 0

    damn, I must say I've always wanted to press a stop button on explorer and finder a zillion times. I wish web browsers were just a *tad* more responsive to the stop button. Everything should have a forward, back and stop button, and in there a browsable history...

    but I hate the 1 window 1 icon thing, I like an interface made up of panes with panels and controls, tree browsers to delve into the path, though mostly the tree isn't needed, it would be nice if it was easy to access without having to chase it.

    spatial metaphors work well in vr 3d interfaces, but they don't apply to such a non-hand like 'pointer' that a mouse is.

    it is good to see thinking being done on the subject, interfaces are an extremely complex and personal subject, habit and logic are mixed up in everyone's view of them. some things are obvious, but some are habit too - to illustrate in more mundane primitive ways - left to right top to bottom is only a habit, other cultures have right to left and bottom to top to throw into the mix.

    the best way to provide for all people is to have lots of different ways of doing things. This is pretty much the philosophy behind windows UI concepts, though it could go much further IMHO. after living with xp for some time now, I couldn't go back to the mac, the only thing I miss is pop out tabs like the control strip. mint audio is a beautiful example of a smart and compact interface for controls. but everything else on a mac just means so much more clicks and drags and stuff than it is on windows. I could never go back to two three buttons, let alone 1, my scrolly mouse makes life so much easier. The closer the mouse gets to being able to behave like the hands the more powerful it becomes.

    endlessly this subject can be discussed...

  96. A better Finder by alanshitface · · Score: 1

    It's now quicker for me to look up Milton's Sonnet on His Blindness by typing into the Google box in Safari than walking across the room to where I can see Milton's Complete Works on the shelf.

    It's also quicker for me to find a document hosted halfway across the world than a file on my own computer.

    As a *Nix newbie I am starting to get my head around the command line, but it's not yet second nature. So many basic organisational tasks are still far too slow and we get no conceptual help with them.

    For instance. I want to flick through the 4685 photos I took in SE Asia and select some of them to play around with. I want to view them fullscreen and tag the ones I like with a keystroke. I can't do this from the command line. I don't want to guess with an icon view and select holding down command only to lose the list. All the image editors I've seen think that displaying images is a passive affair and that ordering and sorting the files doesn't need you to be able to see them full resolution.

    I can't use folder of images on a network volume for my screensaver reliably.

    I have to think before opening a folder on a network volume whether it has too many files (>1000) for the Finder to cope.

    And yet it's a supercomputer and I'm a big fan.

  97. Re:Full Mirror by j-pimp · · Score: 1

    Well through clever use of expire tags and such proxy servers are non issue. However a full blown mirror takes that away. Google caches are designed so most people only use them then the page is not currently accessible. You only tend to click on the cached version after the rgular version.

    --
    --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
  98. Re:mac problem by Anonymous Coward · · Score: 0

    20+ years experience with Macs?

    I might buy it if the Mac were 20 years old yet.

  99. arstechnica is pathetic by Anonymous Coward · · Score: 0
    Would I listen to someone's ideas about UI if their own web site is absolutely amateurish and made against UI standards, starting with white-on-black text.


    Losers.

  100. Are a genius? by Anonymous Coward · · Score: 0

    Soooo simple. Thanks!

  101. Labels?! C'mon!! by SPYvSPY · · Score: 1

    You don't need labels, although I will admit that they are more convenient.

    Why don't you just go to iconfactory.com or some other place that makes OS X icons, download a set with multicolored folders, select the folder of the color you want, hit apple-I, click on the icon in the information panel, hit apple-C, then select the folder whose color you want to change, click on its icon in the information panel, hit apple-V.

    Even better, make your own icons by creating images in Photoshop. When saved in .psd format, the image document's icon will be the image in the document. Use the same cut and paste routine via the information panel to transfer your new icon from the photoshop file to your target file/directory.

  102. Good for you by Anonymous Coward · · Score: 0

    I like to see OSX held to a higher standard. Im sitting here about ready to kill this crappy NT machine I have to use at work...and while I wish it was an OSX machine I know so much can still be done with OSX to make is so much better than it is today. I can only hope that someone at apple reads articles like this, and that the info gets relayed to the upper crust.

    OSX offers stability that OS9 could only aspire to...now its time to get working on matching that stability with functionality.

  103. [OT] KDE & Scripting by c4Ff3In3+4ddiC+ · · Score: 1
    For example I wrote a script to
    If you don't mind could you point me to some more info about scripting KDE? If you prefer, you can email me at caffeine_addictSPAM@SPAMspeedpost.net (remove SPAM). Thanks.
    --
    *twitch*
    1. Re:[OT] KDE & Scripting by Cyno · · Score: 1

      Hehe... well, what I do is write a script in shell or perl, make it executable and put it in /usr/bin, for example. Then use the rick-click "open with" -> "other..." and tell it to launch my script for that type of file. Then you can use the "Edit file types..." to move your script up to the top of the list or make it automaticly use your script instead of launch an application or perform a default action. Or at least you'll have access to it in the "open with" submenu.

    2. Re:[OT] KDE & Scripting by c4Ff3In3+4ddiC+ · · Score: 1

      Thanks

      --
      *twitch*
  104. Just a nit by jdgeorge · · Score: 1

    You say :wq, I say ZZ. Why can't we all just get along?

    Can't help it picking a nit with your sig, but most vi users know say :x instead of :wq since they both do the same thing except that :x only saves if changes have been made.

  105. Re:Full Mirror by jx100 · · Score: 1

    I doubt any bad blood exists between the 2 right now, as this service isn't sponsored by /. It seems like it's being run by an independent person, who isn't supported by /. The front page of the site says that CmdrTaco doesn't endorse what he's doing.

  106. The purpose of GNU/Linux by jdgeorge · · Score: 1

    for a dude that use linux and gnome your knowleged of computers is less then I exprected.

    I, for one, have been using primarily Linux for the past eight years. For the past twenty years I have used such computers as TRS-80, Commodore64, Apple II, RS/6000, various IBM PC "clones", and on rare occasions Apple Macintosh.

    Until this thread, I never really knew what the Apple "finder" really was, though the name implies that it helps you find files. In the little time I spent on the Mac, I never saw the finder, or knew that I was looking at it.

    To me, knowing about Apple's finder is like knowing about AOL's "chat rooms". Being a frequent user of either seems indicative of a lack of technical knowledge or inclination, rather than the contrary, as you imply.

  107. Too Much Smoke, Not Enough Mirrors by Pingsmoth · · Score: 1

    I appreciate what Siracusa is trying to do, but I think he's missing the forest for the trees. His explanations of a spatial finder is nice, and it's obvious he has the experience to back up his claims about a proper finder being spatially oriented. However, I think his solutions are rather weak. It's easy to complain, but a finder that uses an iTunes-like browser? A middle-man dock-like station for files when moving them? These may be spatially pleasing, but they are certainly not intuitive, and intuitive interface (not a spatial interface, as Siracusa claims) has always been the hallmark of the Mac OS.

    It's true that the OSX Finder does have its share of problems, but it's getting better, and will only improve with time. Does he honestly think Apple forgot about their own inventions like pop-up folders and the ability to change font sizes? I agree, these things are missed (as is my favorite, the application menu. Why, Apple, why?) but I think I see the point that Apple is trying to make in all of this: OSX should be intuitive for the new user, and simple for the new user to operate, while at the same time maintaining an unprecedented level of control and functionality for the power user. It succeeds admirably at both.

    Perhaps new users would understand the Finder better if it were more spatially oriented, but it is still very easy to use in its current form. And the Mac faithful? The millions of fans like who have been loyalists since the days of the 512? We know there's problems but we also see what Apple is trying to do, and that's survive in a very competitive market. Because the OSX Finder is suitable for novices, longtime users, and power users, I'm willing to forgive its inconsistencies and annoyances at the expense of the greater cause, which is to keep Apple alive in the first place.

    --
    http://www.walkingtaco.com
  108. YoU aRe TeH gAy by Anonymous Coward · · Score: 0

    Gaytoo is not a production enviorenment OS. OS X is. Gaytoo is for fan/tbois who like to waste time with their computers

  109. Re:Labels?! C'mon!! by Phroggy · · Score: 1

    Why don't you just...

    Because you can't sort by that in a list view. In Mac OS 9, you can sort by label.

    And because a label can be quickly selected from a menu, instead of 1) going to Get Info, 2) copying the icon, 3) launching a graphics app, 4) pasting the icon, 5) changing the color, 6) copying the new icon, 7) pasting it back, and 8) probably losing the alpha channel along the way.

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  110. Great article, but ... by Anonymous Coward · · Score: 0

    Here's a quote from the article:

    Even the seemingly chaotic and messy act of "drilling down" to a deeply nested file using the Spatial Finder, double-clicking one folder after another and spawning windows like crazy, can be accomplished with comparatively little conscious thought. The user finds his way using visual cues (reinforced by the coherency and stability of the Spatial Finder) rather than by rote memorization of file paths. In the same way that you might drive a familiar route without knowing all the street names or exit numbers, the Spatial Finder user might not know the actual path of the file on disk. But like the driver, the user does not need to know all the names of the places along the way. He only needs to know where he is, and how to get there from here. In a non-spatial system, users must remember "addresses." The Spatial Finder enables users to remember locations.

    Here's the problem. In the Mac OS 9 Finder, this *is* really chaotic and messy. If you go to basically the same folders all the time, it's not so bad, because over time you set the size, settings, and position of all those folder windows and you really do remember how to get everywhere without thinking about it. BUT if you're like me and you go onto network servers and drill down 8 levels constantly, it's a total pain in the ass because every single window opens up in unsorted icon view.

    The column view kicks ass in this scenario because of how quickly you can navigate, especially if you use the keyboard.

    Now, if you set the Finder to open new windows all the time, you can switch between the oh-so-dreamy spatial Finder and the lightning-fast column view easily. You open a column view window, double-click on a folder, and it opens in its own window with whatever settings you used last time. Or you open a folder window in List or Icon view, and switch to Column view to drill down 8 levels easily. Don't get me started on how brain-dead it would be to have two separate apps (spatial Finder and browser Finder). Sometimes I want to get around one way, sometimes the other, and having to do anything more than a mouse-click to switch is just plain stupid.

    So the pure spatial Finder idea is abandoned. You can have the same folder open in two different windows - who cares? How does this make my life harder? So you can open the Desktop folder in a separate window - oh well.

    Apple decided to abandon the lovely ideological purity of the spatial Finder in order to create a (IMHO) much less irritating way to get around the system. In the past, I've often thought the Finder was easier to use and Windows Explorer was faster to get around with - with OS X, Windows is beat easily on both counts.

  111. One small error, one huge error by Steve+Cowan · · Score: 1
    On the finder-4 page Sircusa states that paths were never seen by the user in Classic Mac OS. In fact, the exception to this is in "Get Info" windows. A minor quibble, but "never" is a strong word.

    Also, In the very first (mock?) screen shot, Mr. Sircusa will have to blame something other than his photoshop skills for this omission! That "Library" folder icon's appearance hasn't changed in any way to indicate that it is open in another window elsewhere on the screen. To me, that's a very big deal, especially in the context of his article, which emphasises the importance of a "connection" between a folder and its Finder window.

    Apart from that, I agree with most of the article, and I think John puts into words what so many Mac users have difficulty explaining.

    I know I should probably be posting this on Ars, but I don't have an account there, and historically John S. has always checked the /. responses to his articles. John if you're reading I'd like to know what you think.

    1. Re:One small error, one huge error by John+Siracusa · · Score: 2, Informative
      In the very first (mock?) screen shot, Mr. Sircusa will have to blame something other than his photoshop skills for this omission! That "Library" folder icon's appearance hasn't changed in any way to indicate that it is open in another window elsewhere on the screen. To me, that's a very big deal, especially in the context of his article, which emphasises the importance of a "connection" between a folder and its Finder window.

      ...in which case you should have concluded that the front-most window is simply another folder named "Library", and not the one shown in the background window! :) Anyway, I knew of the omission before the article was published by was too lazy to fix it due to the previously stated rationalization. It's fixed now, however.

  112. Readable colours by John+Bayko · · Score: 1
    Ctrl-A helps - generally inverts all the text on the page. Also helps for dumb pages that have a blue background, so blue links look like gaps in the text.

    As for "most readable" yet "least straining" colours, doesn't anyone remember word processors, terminal programs, and so on before the "paper" metaphore took over? With complete configurability of colours, both users and companies seemed to settle down on yellow or white on blue as the best choice. I still use a text-mode computer at home set to yellow on blue - I still think that's the best colour combination, if you don't have to worry about making the appearance of GUI junk on the screen look pretty.

    Historical note - that's why the Blue Screen of Death is, in fact, blue, with white text. It simply was the universal standard colour scheme for presenting text at the time.

  113. Best Finder Addition -- "Launchbar" by ErnstKompressor · · Score: 1

    The single greatest enhancement to OS X is Launchbar--

    Find, manipulate, launch anything anywhere on your computer...applications or files. You will not understand how you lived without it.

    --
    We apologise for the fault in this post. Those responsible have been sacked. -- Signed RICHARD M. NIXON
  114. Re:mac problem by tuxedobob · · Score: 1

    Yes. Yes you did. Not as common as Father O'Day or the reply to Father O'Day, but this one shows up from time to time. (BTW, my kudos to whomever thought about trolling responses to trolls. To bad it's out of order now and then.)

  115. It was me? by LynXmaN · · Score: 1

    Or I was the only one to read:
    Apple: A better finger?

    Oh man... April's fool got me paranoic

    --
    May the source be with you!
  116. Couldn't finish the article by goodchef · · Score: 1
    I couldn't finish reading the article. I stopped after the first few paragraphs. Nothing personal, I just have a hard time believing this will be a rational, well-thought out, and fair article when it starts out
    "It's no secret that I don't like the Mac OS X Finder. Almost every article I've written about Mac OS X has included a litany of criticisms, from small annoyances to fundamental philosophical differences."

    The conclusion of this post is left as an exercise for the troll^H^H^H^H^Hreader.

    --

    "Inflammable means flammable? What a strange country!" -Dr. Nick, The Simpsons

  117. Re:a better finder? by hobbit · · Score: 1

    MacBU at Microsoft is one of the most profitable centers for MS because... they face so much competition for Office on Windows? I hardly think so.

    --
    "Wise men talk because they have something to say; fools, because they have to say something" - Plato
  118. As someone not in the IT industry.... by Pettifogger · · Score: 1
    This really puts the finger on why I'm not all that comfortable using OS X. My field is pretty far away from tech, but computers are my hobby and I have several to fool with.

    Though it's great fun to pick around with Linux and newer Mac OSes, when I want to get some serious work done and not worry about a damn thing, I turn to my old Mac IIfx, running System 6.0.8. Reliable,stable, and absolutely mindless ease of use. Not to mention the fact that it it runs System 6 blindingly fast- faster than any of my newer machines running newer OSes.

    Personally, I'd very much like to see a return to the simplpicity and mindless ease of use found in the earlier Systems. It's not necessarily a bad thing. I see the endless customization of Linux and the quirks of newer systems as a hobby. It really is fun to plpay with, and yes, you can get some work done. This is in the same sense that you might keep one car around to tinker with, fix, upgrade, and so on. But anyone who does that almost always keeps a "beater" on hand that will keep running as long as there's gas in the tank. System 6 is my beater, and I'm not giving it up any time soon.

    --

    IAAL

  119. Re:Interesting-Look through thy eyes. by Anonymous Coward · · Score: 0

    Actually why should people be dealing with files anyway? There's two things that people do with their computers. Create something, or manipulate something they've already created[1]. Maybe a more app-centric POV is needed. Pick the app you want to use, then "select" brings up all the things that that app can deal with, with the capability to filter further down (time,subject) in a fuzzy manner. Maybe Natural Language Interfac sensitive to FS Metadata.

    [1] Divide that into playing, or changing (adding, subtracting).

  120. Re:Full Mirror by Rob_Bryerton · · Score: 1

    That's great and all Caesar, but perhaps you should email the mods instead of airing your business in a public forum?

    Maybe it's just me, but in my business, when a supplier, vendor, competitor, or business partner steps out of line, I contact them directly.

    I seem to get better results that way than opposed to, say, posting to a public forum on a global network.

  121. Terminology / feature description by sidb · · Score: 1

    Beacause of the similar names, people confuse "spring-loaded folders" with "pop-up folders", but the two terms are used to refer to different things in the Mac world.

    "Spring-loaded" means that when the user drags something over a folder's icon, that folder's window will open after a short delay, allowing the user to continue dragging. This allows the user to drag into a nested folder several layers deep wthout opening it first.

    "Pop-up" windows, (also called drawers by some), exist only in the classic Mac OS (although there are rumors of a comeback in OS X Panther in June). These are windows that have been attached to an edge of the screen such that they normally display only as a small tab with the window's name. When the tab is clicked or dragged onto, the window slides open onto the screen, automaticaly closing into a tab again when it loses focus.

    1. Re:Terminology / feature description by Chmarr · · Score: 1

      Thanks for the clarification. Yes, that does sound like it would be neat.

  122. Apples really annoy me.` by Anonymous Coward · · Score: 0

    Apple did one thing right a few years ago. They used FreeBSD as their core API and provided the FreeBSD userland. But then they insisted on tacking on lots and lots of GUI bells and whistles that slow the system down to the point that interactivity is totally screwed. I really resent that, especially since I'm forced to work with the damn boxes and don't have the time or access to turn off all the fluff.

  123. OSX good. Finder bad. by trouser · · Score: 1

    Finder mostly works but it's a little less stable than pretty much any other app installed by default on a fresh OSX install.

    It doesn't quite understand file permissions / ownership. I mount my home directory via NFS from a Linux server and often can't create, copy or move files in the Finder because of spurious permission errors that don't seem to apply if I do it manually from the Terminal.

    Also, try disconnecting the ethernet cable while you have remote volumes mounted. The Finder becomes steadily less responsive and pretty soon you can't do anything. I often put my laptop to sleep, go home, open the laptop and find that I need to reboot because I forgot to unmount something before I left the office.

    I've heard it's a Carbon app. The Carbon libraries are very OS9 centric and might be useful for porting old apps to OSX but are hardly suitable for the app which is the front end of the whole GUI.

    --
    Now wash your hands.
    1. Re:OSX good. Finder bad. by berniecase · · Score: 1

      Also, try disconnecting the ethernet cable while you have remote volumes mounted. The Finder becomes steadily less responsive and pretty soon you can't do anything. I often put my laptop to sleep, go home, open the laptop and find that I need to reboot because I forgot to unmount something before I left the office.

      This is exactly what happens to me, too, and it's incredibly annoying to have to reboot the computer forceably. Sometimes the Finder gets so hung (blocking I/O bad, Apple, very bad!) that I have to actually give my Mac a 3-fingered salute (or the ol' press power button until it shuts off; then turn it back on) to get it to reboot.

      AFP services within the Finder need to be multithreaded, or their own separate app. It's annoying to have the Connect to Server window up, and then not be able to click anywhere else in the Finder because of it.

      And yes, a truly Cocoa Finder would be most appreciated. It's about time to get rid of the Carbon version.

  124. Path Finder! by ennerseed · · Score: 1

    An excelent Mac OS X Finder replacement is Path Finder by cocoatech.
    http://www.cocoatech.com/
    This doesn't relate to some of the problems that Ars talked about, but surely solves alot of the shortcommings in the Apple Finder.

    --
    "If we knew what it was we were doing, it would not be called research, would it?" - Albert Einstein
  125. BlahdaBlahdaBlahdaBlah by mgbaron · · Score: 0

    This guys a quack. I cant believe I wasted my time reading this. These HCI guys really get to me when they start overanalyzing like this. Face it, there is little to no "mental juggling" involved with using a back button. Think of it spatially as a stack of papers in which you can only see the top. The reduction of desktop clutter is far worth this sacrifice.

    You can tell this is the type of guy that really loves to hear his own voice.

  126. This is NOT an article about metadata! by wealthychef · · Score: 2, Insightful

    I just wanted to point out that the article is not about metadata. The author carefully separates that as a separate issue. The article is about the concept of a "Spatial Finder" and the current lack of emphasis by Apple on the Finder vs. their old metaphor that the Finder IS the computer. Read the article! Very interesting.

    --
    Currently hooked on AMP
  127. Unknot your panties, dear... by Anonymous Coward · · Score: 0

    The spatial finder is not a bad idea, but I think the author's insistence on its superiority is based on some narrow and dogmatic assertions about human psychology. While it's certainly the case that large chunks of the human brain are devoted to spatial thinking and that people deal well with spatial interfaces, it's also the case that large chunks of the human brain are devoted to verbal, sequential, and auditory thinking, and that people can deal with non-spatial environments very competently also.

    The idea of the back-button, for example, is based on sequential thinking, and most people who are not living in homes for the retarded can think sequentially with ease. Likewise, the verbal skills required to navigate a command-line or address-bar are deeply ingrained in the human consciousness, which in fact depends on words to define many complex concepts.

    In short, people think in a multitude of ways, and it is senseless to limit an interface to only one way of thinking. While many of Apple's users are indeed visual thinkers (graphic artists, photographers, etc.), most of these people are capable of speaking in complete sentences, reading books that do not have pictures in them, and finding periodicals in a library or large stack. As the history of UI design has shown, humans can use numerous different interface paradigms, as well as cross-paradigm hybrids like the current crop of graphical UIs. The best sort of UI is one that can be adapted to different types of thinkers, but even so there are few people so stupid they cannot master a file browser.

  128. Re:mac problem by Anonymous Coward · · Score: 0

    I've been sitting here at my freelance gig in front of a Mac (a 8600/300 w/64 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this Mac, the same operation would take about 2 minutes. If that.

    Err WTF?

    I have just tried it on a 7200/200.

    *Time to duplicate a 17.4 Mb file about 8 secs
    *Time to move a 17.4 mb to another folder on the same Hard Drive about 0.2 secs
    *Time to copy a 17.4 Mb file to an external Hard Drive about 12 secs

    I think you need a new watch...

  129. How about... by jode_sanders · · Score: 2, Interesting

    a finder with 1+ windows with TABS a la safari/camino? I am suprised no-one as seen fit to mention this. This would be perfect for me, any others??

    1. Re:How about... by Anonymous Coward · · Score: 0

      No.

  130. Re:Labels?! C'mon!! by andrewski · · Score: 1

    I have always thought that labels are extraneous. What do they do that a different Icon can't do, even in 9?

  131. Re:mac problem by drgroove · · Score: 1

    Sorry - meant to say 'apple & pc'. My first computers were an apple iic, then later a commodore64, then a pc/386 ... trust me, i've seen 'em all!

  132. Re:Labels?! C'mon!! by cpt+kangarooski · · Score: 1

    They allow you to sort by label.

    Back when I was writing a lot of web pages at my old job, I used labels to indicate which files needed to be edited or had already been edited. I couldn't change the filenames -- web links (stupidly at times) rely on them. And I couldn't keep things in different directories, because then I'd lose the basic structure of the site, and could not step through it, and inspect it. (or have linked files work, such as inline graphics, stylesheets, or scripts)

    Furthermore, with regards to the icon, you're flat out wrong there too. It is faster and easier to set a label than it is to find an icon, copy the icon, and paste it onto the new file. Particularly since I don't want to change the basic shape of the icon -- just tint it. And tint it to a particular user-selected color, rather than one that might be supplied by a vendor.

    Lots, and I mean LOTS of people use labels constantly. Presently I'm using Windows. Rarely does a day pass when I don't wish that it had labels -- a lovely feature that the Mac had since the late 80's IIRC.

    --
    -- This and all my posts are in the public domain. I am a lawyer. I am not your lawyer, and this is not legal advice.
  133. Offer the alternative after that article, please by giaguara · · Score: 1

    Criticism is ok when you can offer an alternative - at least as good, or a really different one.

    This article was split to 25 pages, that is 100-150 banner views later you have read the article and then? I don't like "philosophical" comments about the programs. If you know how you wanted Finder to be, just _CODE ONE YOURSELF_ and offer at least an alfa version of it! Code that spatial finder, and give it to download.

    I could rant about some features of terminal and console - or I could simply get other programs that satisfy me more, or hack the core of the programs and make them behave as I want.

    And if you can't do what you bothered to describe with 25 pages (= about 2 split to give 100-150 banners to be seen) then just post in on a philosphy board.

  134. Gobbledegook by Anonymous Coward · · Score: 0

    Gobbledegook. Hot air. Rhetoric by one who deserves not to breathe.

    What is important is how Apple have gutted the old NS code and left the underpinnings of the Finder wide open. Today, the OS X "shell" is so vulnerable it isn't funny. Sanity checks in file operations are not at file system level, but in the Finder itself.

    Remember that first Safari download of build 48? Remember how people got their entire systems hosed by a bad call?

    That was a call to NSWorkspace. The dumb thing has no sanity checks today. The original NextStep version had tons of sanity checks, but Apple have taken the code out. They have code for sanity checks in the Finder, but that didn't help Safari, or the poor users who got their systems trashed.

  135. SID or Directory Opus (both from Amiga OS) by snolan · · Score: 1
    I really miss Timm Martin's shareware program SID and a commercial product called Directory Opus. Both were file/directory utilities on the Amiga OS - and neither would replace the finder outright - but both offered interesting alternatives.

    I used SID extensively for quickly sorting very large numbers of old text files. SID was so useful at this, that I would routinely use tar archive entire directory structures to QIC 150MB tapes, cart the tapes home, extract the archives on my trusty old Amiga, use SID to sort out and clean up the files, and re-organize them into more meaningful directory structures, then tar the results onto a tape to take back to my UNIX boxes at work. Back then (1988 - 1992) I routinely wished for SID for UNIX.

    Today I still wish I had SID on Mac OSX. I no longer fire up the old Amiga - finder's detailed list view - with side by side finder windows showing different directories is pretty close to what SID looked like, so I no longer tar things off to the Amiga for SID sorting... but I wish SID were available for Mac OSX, because it was much more useful than two finder windows are. Much faster at many operations too.