Finding my way around Finder (continued)

The folder structure under OS X is probably the one thing that has taken me the longest to get used to - mostly because I've been such a heavy DOS/Windows user that I still feel too foreign with anything other than C:\Windows or Program Files. It's a shame, and even after years of using *nix boxes at school, it's still something with which I'm not totally comfortable. Because of that, I continue to feel that the folder structure under OS X is quite disorganized, but there is also another reason why I don't feel as in touch with the location of all the files under OS X as I'd like to be - and it comes down to how applications are installed.



Installing (and conversely, uninstalling) applications under OS X is quite possibly the most disconnected feeling that the OS gave me, while at the same time, it was pleasantly easy. How could installing an application possibly be made any easier than it already is? Well, to install an application, you simply drag the application's installer to any folder on your hard drive and it's "installed". Doing so actually triggers a number of files to be copied to various places on your drive, but the fact that you are separated from that process, it really made me feel like I wasn't in control of my system. On the flip side, installing and uninstalling applications couldn't be easier. There are no full screen installers to deal with; just drag and drop, and get back to work while the application installs. The fact that I don't know where everything is being copied contributes to my feelings of file system disconnect. Then again, maybe I'm being a bit too philosophical about my OSes. Update: A number of people have written to provide some clarity to this statement. It is not the actual installation that copies files everywhere, in fact the installation is quite contained with all files remaining in a single folder. It's the process of running an application that will copy preferences over to your Preferences folder. The paragraph above as it stands does apply to Microsoft Office 2004 but not the vast majority of OS X applications, this isn't the only way in which Office 2004 differs from the rest of the applications for OS X. I apologize for the confusion.

The information about files and folders is also a bit more customizable under OS X. Highlight the file or folder on which you want details and hit Command-I, or you can just right click and go to "Get Info". From here, you can change everything from file permissions to what program opens the file or files of that type. You can add comments to any file or folder as well. As is the case with most other OS X dialog boxes, everything occurs in real time. Just hit Command-W or click the red button to close the window.



One thing that may take some getting used to is the positioning of the close button on all windows in OS X - it's at the top left corner instead of the top right. The minimize button is next to it, followed by something other than the maximize button. In fact, there's no way to maximize a window quickly in OS X (I'll get to why in a bit); instead, the green button to the right of the minimize button is sort of a fit-to-content button. Clicking the green button will resize the window both horizontally and vertically to fit the contents of the window the best, which is especially useful when browsing web pages or really viewing any content where you're trying to maximize screen real estate.

The fundamental difference between OS X and Windows is how applications and windows are handled. What OS X has going for it is uniformity between applications and windows; for example, the keyboard shortcut for the preferences dialog in any OS X application is Command and the "," key. So, regardless of what application you're in, the same keystroke combination will have the same expected effect - pretty useful.

The uniformity really extends far beyond keyboard shortcuts as I was alluding to before - a menubar always exists at the top of your screen in OS X, regardless of what application you're in. Thus, you always have a File, Edit, View, Window and Help menu regardless of what you're doing. It looks like Apple's reasoning behind this is to avoid confusing users, but to a Windows native, it can be very foreign.
The biggest complaint that I both had and levied against was that it always seemed like you had more applications opened than what you wanted. In Windows, once all of the windows of an application were closed, the application itself was usually exited. Under OS X, until you actually quit the application, regardless of how many or how few windows of it that are still open, the application remains running. Thanks to an extremely aggressive caching engine and an extremely robust/stable OS core, I ended up actually preferring it when I had the majority of my frequently used applications open. This approach ends up using quite a bit of memory, but I found that there's no slowdown if you have the memory to handle the open applications. If not, you can always close the applications that you don't want running - Command-Q is the keyboard shortcut; it's the same in any OS X application (Command-W just closes the foreground window).

The benefit of leaving applications running even when you're not using them is that when you do need to use them or open a file with one of them, the response time is instantaneous - as opposed to waiting for an application to load. Of course, you can do the same thing in Windows, but for some reason stability and performance seemed to remain unchanged under OS X, whereas I almost always ran into an issue with Windows - whether it was having too many windows open or too many programs running.

Finding my way around Finder Multi-tasking
Comments Locked

215 Comments

View All Comments

  • brichpmr - Friday, October 8, 2004 - link

    #53, I can't prove or disprove your statements; but the bottom line for me as a dual platform user, is that OSX is a very cool computing environment that gets better with every point release; it's very stable, malware free (so far) and lets a bunch of us earn a handsome income, even in a Windows-dominated enterprise....as a workhorse machine, the numbers become secondary to a user's productivity...the Mac is very productivity-friendly. I won't even mention how much fun it is to run F1 Championship Season in 1280 by 1024 with a nice Logitech force-feed wheel...whoever thinks the Mac can't play good games needs to re-think!
  • gherald - Friday, October 8, 2004 - link

    To #48 who says: "If a lot of PC users would open their minds and try using a Mac for 30 days: they would appreciate what us mac users like about the platform."

    My answer is: The usefulness of this article is that we don't HAVE to spend time and money doing that. We get to read about someone else doing it -- someone who's opinion we trust.

    This is the most fair minded Mac review I have ever seen. Kudos to Anand for giving us insights on a platform that is too expensive for most of us to afford to try out on our own.

    The $3000 price tag is interesting. I recently built 2 AMD64 machines for somewhat less money: A 3400 for windows, and a 3200 for Linux. There is no doubt in my mind that this was the best value, especially since I play a number of windows-only games but prefer Linux for everything else. I don't think the Mac even comes close to beating the power, compatibility, and flexibility of such an approach, at least for my purposes.
  • skiboysteve - Friday, October 8, 2004 - link

    cindy are you kidding me?

    ALl it takes is one air cooled 2.4ghz Athlon64 to match a DUAL WATER COOLED 2.5ghz G5.

    Not to mention a single air cooled 2.4 A64 is cheaper.

    And that barefeats article is so laughable, one of the shadiest configurations of hardware i've ever seen... not trustable at all.

    I dont have the info in front of me, but there was a G5 bench mark from an actual hardware website worth something and the G5 got smoked on single proc. and only matched with dual.

    And where the hell did you pull the PPC970 does more ops per clcok than an Athlon64 info? It has a 16 stage integer pipe, gee, hmm, thats 25% more than an athlon64. Now I know your going to say it can have 200 operations in flight, but... "So while the 970 may be theoretically able to accommodate a whopping 200 instructions in varying stages of fetch, decode, execution and completion, the reality is probably that under most circumstances a decent number of its valuable execution slots will be empty on any given cycle due to dispatch, scheduling, and completion limitations."
    (http://arstechnica.com/cpu/02q2/ppc970/ppc970-5.ht...

    The problem with the PPC970 is its long pipe wide execution scheme would be good but it doesnt have enough resources to fill the wide ass pipe and all the execution units, which is exactly as expected becasue its a cut power4 chip. "The 970's integer hardware was designed to deliver 64-bit integer performance, and it was also designed with the ridiculously large caches of the Power4 in mind. When it you decrease the cache sizes to desktop computing levels and run 32-bit code on it, it starts to look less impressive next to the P4."

    Your "facts" are terribly flawed and I just had to post about this because somehow no one else did.

    The PPC970 is the best chip the Mac has ever had, but its clock is not high enough, its too hot, and its operations per clock are no where near the G4, and behind the A64.

    (http://arstechnica.com/cpu/03q1/ppc970/ppc970-1.ht...


    I realize this probably comes off as a massive PC-bias attack on you, but honestly, get your facts straight before you start praising the great PPC970 chip on a HARDWARE website, where people KNOW whats up.
  • Sakamura - Friday, October 8, 2004 - link

    1st post. Mac user. Reader of AnandTech for a long time for PC needs and other cross-platform niceness.

    For the few answers I can provide that aren't already addressed in the 5x messages prior to mine:

    - Applications are "packages" like explained. Some do use the Library to install ... And some ask for a admin password to add their kext in the system library. It all depends on the app.
    - Caching is indeed very optimized. Still no Ext4 but very optimized. Thanks to BSD base.
    - Search engine is not cached. It's a system service that allows you to sort and classify any sort of data. That's the same sorting algorithm that determines if a mail is spam or not. This is also used in file search, text search, dictionary and whatnot.
    - User interface is not meant to be snappy. Strangely enough, I have almost the same user interface speed on my G3/400 than on a G5. But then, the actual work does slow down to a crawl when doing processor intensive tasks. Alas, today, this means Mail, Safari, Quicktime. But nonetheless other than the actual "work" being done on something, the interface remains decently fast all the time.

    Great article, nice points.
    Have a nice day
    Mike
  • CU - Friday, October 8, 2004 - link

    You can run X11 and all the open source stuff on Windows to. You just install cygwin. Don't some dist. offer running linux inside windows also.
  • jecastej - Friday, October 8, 2004 - link

    44 - "price to performance" is perfect if you need to justify a purchase to your office or IT department. Which maybe is the 98% of the cases.

    It may look like luxury but sometimes is necessary to value other human needs. Business creative environments benefit from aesthetics. Apple's software/hardware provides an alternative at a reasonable price to performance ratio. Won't kill to have this option.
  • punko - Friday, October 8, 2004 - link

    Wow.

    And I thought Coke vs. Pepsi was bad.

    All I can say is that as a computer user from way back (punch cards and PDP-11's anyone?) I have never owned or used a Mac (other than to print false birth certificates in high school to go to bars) but I have occasionally wondered what it would be like to have one.

    Anand has a better understanding of the total breadth of the PC environment, and so is a perfect lens with which to view the Mac world from a PC user perspective.

    All the bile and venom swishing around here in the comment trenches isn't worth worrying about.

    Great article Anand. I know more is coming down the pipeline concerning the Macs; and even though I am dreaming of a AMD64 upgrade, I will read and consider the informed opinion of a knowledgable computer user.

    Cheers.

  • rvirmani - Friday, October 8, 2004 - link

    About as objective an article as you can expect from a hard core PC user (who makes most of his income from the PC World).

    I switched to the Mac 2 years ago, and went through the adjustment.

    I think the key thing I want to point out is:
    1) less irritation on a day to day basis
    2) My system has never crashed ( although I do fix the "permissions" on a weekly basis using the built in disk utility

    3) The other benefits of the mac are the iapps (Which Anand did not get around to looking at)

    4) I use a Power Mac G4 with 2 Gig of Ram and it is plenty fast for day to day things like MS Office and Web research.

    I think the "performance" mentality of many PC enthusiasts is really the biggest barrier (I like not worrying or thinking about the hardware too much).

    5) OSX is much better at multi-tasking - even on a single processor machine.

    If a lot of PC users would open their minds and try using a Mac for 30 days: they would appreciate what us mac users like about the platform.

    A good start for Anand, and I look forward to more explorations of the Mac platform.

  • sprockkets - Friday, October 8, 2004 - link

    err... that was 256MB of memory with 233MB used due to a shared SiS740 chipset in my Shuttle system and 165MB in swap, was running transcode and a few other smiple apps, such as Konqueror.
  • sprockkets - Friday, October 8, 2004 - link

    I find that browsing is fastest with Opera on any platform, yet it was almost as fast with IE and Firefox on a new install of Windows XP home. I only put 256MB of RAM in it yet it boots and runs applications quite nicely. I notice the delays in web pages when using FireFox in Linux, though I could care less (has 256MB too with.

    The bottom line is, you shouldn't have to use 1GB to 2 or even 4 GB of ram just to get a nice response time. That and dual 2.0GHZ is still available. That and browsing and multitasking shouldn't require DUAL 3.0GHZ PPC processors.

    Another point, if Mac OSX was made for an X86 processor, I would buy it. But since it isn't, and SuSE 9.1 is free anyhow, with just as customizeable KDE or GNOME desktops, not to mention light and fast IceWM desktop, why bother.

    Off topic, but doesn't Windows NT5 varients shut down after 45 days of uptime?

Log in

Don't have an account? Sign up now