Killexams.com 9L0-060 real questions | Pass4sure 9L0-060 real questions |

Pass4sure 9L0-060 dumps | Killexams.com 9L0-060 existent questions | http://heckeronline.de/

9L0-060 Mac OS X 10.4 Service and Support

Study pilot Prepared by Killexams.com Apple Dumps Experts

Exam Questions Updated On :



Killexams.com 9L0-060 Dumps and existent Questions

100% existent Questions - Exam Pass Guarantee with tall Marks - Just Memorize the Answers



9L0-060 exam Dumps Source : Mac OS X 10.4 Service and Support

Test Code : 9L0-060
Test title : Mac OS X 10.4 Service and Support
Vendor title : Apple
real questions : 50 existent Questions

forget about the gross thing! just forcus on the ones 9L0-060 questions.
preparing for 9L0-060 books may breathe a tough system and nine out of ten possibilities are that youll fail in case you consequence it with notathing suitable guidance. Thats in which satisfactory 9L0-060 ebook is available in! It offers you with green and groovy records that now not handiest complements your steerage but additionally offers you a effortless reduce hazard of passing your 9L0-060 download and entering into any university with notathing despair. I organized through this excellent software program and that iscored forty two marks out of fifty. I can guarantee you that its going to never can waiton you down!


i discovered a wonderful region for 9L0-060 dumps
im Aggarwal and that i labor for ingenious Corp. I had carried out to appear for the 9L0-060 exam and became very worried approximately it because it contained arduous case research and so forth. I then implemented for your questions and answers. My many doubts got cleared because of the explainations supplied for the answers. I too got the case research in my electronic mail which had been well solved. I seemed for the exam and am joyful to mention that I got 73.seventy five% and i forward up with the gross credit score. further I congratulate you and appearance further to limpid more exams with the assist of your site.


I am very joyful with this 9L0-060 study guide.
Knowing very well about my time constraint, started searching for an effortless passage out before the 9L0-060 exam. After a long searh, create the question and answers by killexams.com which really made my day. Presenting totality probable questions with their short and pointed answers helped grasp topics in a short time and felt joyful to secure capable marks in the exam. The materials are too effortless to memorise. I am impressed and satiated with my results.


it is terrific ideal to prepare 9L0-060 exam with dumps.
subsequently it used to breathe difficult for me to center upon 9L0-060 exam. I used killexams.com Questions & answersfor a time of two weeks and create out a passage to solved ninety five% questions within the exam. these days im an teacher within the instruction business and totality credits is going to killexams.com. making plans for the 9L0-060 exam for me was not less than a tainted dream. coping with my research along low maintenance employment used to enervate almost totality my time. lots favored killexams.


9L0-060 question bank that works!
I though that if I may want to limpid their 9L0-060 test and certain that is once I got here to know with my ancient fine buddy that killexams.com is the one that could breathe the boon for me as it were given me my intelligence eventually again which I had misplaced for a while and that i wish that this will in no passage recoup from for me getting my 9L0-060 test cleared after all.


Did you attempted this top notch supply modern-day dumps.
Mysteriously I answerered totality questions in this exam. Lots obliged killexams.com its far a extraordinary asset for passing test. I pose actually everyone to without a doubt expend killexams.com. I test numerous books but not notedto derive it. Anyhow in the wake of using killexams.com Questions & solutions, i discovered the immediately forwardness in planning query and solutions for the 9L0-060 exam. I observed totality the issues well.


proper location to derive 9L0-060 existent select a notice at question paper.
I occupy been the usage of the killexams.com for a while to totality my tests. Closing week, I passed with a outstanding marks in the9L0-060 exam through manner of using the existent questions examine sources. I had a few doubts on topics, however the material cleared totality my doubts. i occupy with out troubles determined the acknowledge for totality my doubts and troubles. Thank you for imparting me the stable and trustworthy material. Its miles the nice product as I understand.


am i able to find dumps Q & A modern 9L0-060 examination?
if you want to trade your future and beget inescapable that happiness is your destiny, you want to labor difficult. working arduous lonely isnt always enough to derive to destiny, you want a few path with a purpose to lead you closer to the course. It became destiny that i create this killexams.com in the course of my test as it lead me towards my fate. My destiny turned into getting birthright grades and this killexams.com and its instructors made it feasible my teaching they so rightly that I couldnt in totality likelihood fail by giving me the material for my 9L0-060 exam.


I am very joyful with this 9L0-060 study guide.
It ended up being a frail branch of expertise to devise. I required a ebook that can nation query and solution and i actually allude it. killexams.com Questions & answers are singularly in charge of every final one among credit. A gross lot obliged killexams.com for giving nice end. I had endeavored the exam 9L0-060 exam for 3 years constantly however couldnt beget it to passing score. I understood my pocket in records the challenge of making a session room.


It is distinguished to occupy 9L0-060 rehearse Questions.
killexams.com question bank was really good. I cleared my 9L0-060 exam with 68.25% marks. The questions were really good. They support updating the database with new questions. And guys, fade for it - they never disappoint you. Thank you so much for this.


Apple Mac OS X 10.4

Unquestionably it is arduous assignment to pick dependable certification questions/answers assets regarding review, reputation and validity since individuals derive sham because of picking incorrectly benefit. Killexams.com ensure to serve its customers best to its assets concerning exam dumps update and validity. The vast majority of other's sham report dissension customers forward to us for the brain dumps and pass their exams joyfully and effortlessly. They never trade off on their review, reputation and trait on the grounds that killexams review, killexams reputation and killexams customer certitude is imperative to us. Uniquely they deal with killexams.com review, killexams.com reputation, killexams.com sham report objection, killexams.com trust, killexams.com validity, killexams.com report and killexams.com scam. On the off casual that you espy any erroneous report posted by their rivals with the title killexams sham report grievance web, killexams.com sham report, killexams.com scam, killexams.com protest or something dote this, simply bethink there are constantly dreadful individuals harming reputation of capable administrations because of their advantages. There are a huge number of fulfilled clients that pass their exams utilizing killexams.com brain dumps, killexams PDF questions, killexams hone questions, killexams exam simulator. Visit Killexams.com, their specimen questions and test brain dumps, their exam simulator and you will realize that killexams.com is the best brain dumps site.

Back to Brain dumps Menu


ASC-094 dumps | 700-038 free pdf | H11-851 braindumps | HP3-025 existent questions | PDDM braindumps | C9020-971 free pdf | CSSBB existent questions | HP0-J64 free pdf download | 1Z0-441 rehearse questions | JN0-530 questions and answers | COG-135 study guide | 70-543-VB rehearse exam | HP0-X01 cheat sheets | FCNSP.V5 sample test | COG-615 braindumps | NS0-140 rehearse Test | SC0-402 rehearse questions | HP0-781 exam questions | C2010-504 brain dumps | HP0-782 cram |


Free killexams.com 9L0-060 question bank
killexams.com Apple Certification study guides are setup by IT experts. Bunches of understudies occupy been whining that there are an immoderate number of questions in such a significant number of training exams and study aid, and they are recently can not afford to manage the cost of any more. Seeing killexams.com specialists labor out this far reaching rendition while still assurance that totality the learning is secured after profound research and exam.

Is it capable that you are searching for Apple 9L0-060 Dumps containing existent exams questions and answers for the Mac OS X 10.4 Service and champion Exam prep? killexams.com is here to give you one most updated and trait wellspring of 9L0-060 Dumps that is http://killexams.com/pass4sure/exam-detail/9L0-060. They occupy aggregated a database of 9L0-060 Dumps questions from existent exams with a specific terminate goal to give you a casual to derive ready and pass 9L0-060 exam on the very first attempt. killexams.com Huge Discount Coupons and Promo Codes are as under;
WC2017 : 60% Discount Coupon for totality exams on website
PROF17 : 10% Discount Coupon for Orders greater than $69
DEAL17 : 15% Discount Coupon for Orders greater than $99
DECSPECIAL : 10% Special Discount Coupon for totality Orders

We occupy their specialists working persistently for the gathering of existent exam questions of 9L0-060. totality the pass4sure questions and answers of 9L0-060 gathered by their group are inspected and updated by their 9L0-060 ensured group. They linger associated with the competitors showed up in the 9L0-060 test to derive their reviews about the 9L0-060 test, they congregate 9L0-060 exam tips and traps, their suffer about the strategies utilized as a share of the existent 9L0-060 exam, the mix-ups they done in the existent test and after that enhance their material appropriately. When you suffer their pass4sure questions and answers, you will feel certain about every one of the subjects of test and feel that your scholarship has been enormously progressed. These pass4sure questions and answers are not simply hone questions, these are existent exam questions and answers that are enough to pass the 9L0-060 exam at first attempt.

Apple certifications are very required crosswise over IT associations. HR administrators spare toward applicants who occupy a comprehension of the theme, as well as having finished certification exams in the subject. totality the Apple certification waiton provided on killexams.com are acknowledged around the world.

It is capable to affirm that you are searching for existent exams questions and answers for the Mac OS X 10.4 Service and champion exam? They are here to give you one most updated and trait sources that is killexams.com, They occupy gathered a database of questions from existent exams so as to give you a casual to arrangement and pass 9L0-060 exam on the very first attempt. totality preparation materials on the killexams.com site are progressive and checked by industry specialists.

Why killexams.com is the Ultimate decision for confirmation planning?

1. A trait particular that waiton You Prepare for Your Exam:

killexams.com is a definitive planning hotspot for passing the Apple 9L0-060 exam. They occupy deliberately consented and collected existent exam questions and answers, which are updated with an indistinguishable recurrence from existent exam is updated, and investigated by industry specialists. Their Apple certified specialists from numerous associations are capable and qualified/confirmed people who occupy investigated each probe and acknowledge and explanation segment keeping in reason the terminate goal to enable you to comprehend the view and pass the Apple exam. The most ideal approach to arrangement 9L0-060 exam isnt perusing a course reading, however taking rehearse existent questions and understanding the birthright answers. rehearse questions waiton set you up for the ideas, as well as the strategy in which questions and acknowledge choices are introduced amid the existent exam.

2. effortless to understand Mobile Device Access:

killexams give to a distinguished qualification effortless to expend access to killexams.com items. The concentration of the site is to give exact, updated, and to the direct material toward enable you to study and pass the 9L0-060 exam. You can rapidly find the existent questions and solution database. The webpage is all-around amicable to permit believe about anyplace, as long as you occupy web association. You can simply stack the PDF in portable and concentrate anyplace.

3. Access the Most Recent Mac OS X 10.4 Service and champion existent Questions and Answers:

Our Exam databases are frequently updated during the time to incorporate the most recent existent questions and answers from the Apple 9L0-060 exam. Having Accurate, existent and current existent exam questions, you will pass your exam on the main attempt!

4. Their Materials is Verified by killexams.com Industry Experts:

We are doing battle to giving you actual Mac OS X 10.4 Service and champion exam questions and answers, alongside explanations. Each existent questions on killexams.com has been confirmed by Apple certified specialists. They are exceptionally qualified and confirmed people, who occupy numerous times of expert suffer identified with the Apple exams.

5. They Provide totality killexams.com Exam Questions and comprise particular Answers with Explanations:

Not at totality dote numerous other exam prep sites, killexams.com gives updated existent Apple 9L0-060 exam questions, as well as nitty gritty answers, explanations and charts. This is vital to waiton the hopeful comprehend the birthright answer, as well as knowledges about the alternatives that were wrong.

killexams.com Huge Discount Coupons and Promo Codes are as under;
WC2017 : 60% Discount Coupon for totality exams on website
PROF17 : 10% Discount Coupon for Orders greater than $69
DEAL17 : 15% Discount Coupon for Orders greater than $99
DECSPECIAL : 10% Special Discount Coupon for totality Orders


9L0-060 Practice Test | 9L0-060 examcollection | 9L0-060 VCE | 9L0-060 study guide | 9L0-060 practice exam | 9L0-060 cram


Killexams HP0-J38 rehearse test | Killexams 642-165 existent questions | Killexams 000-026 existent questions | Killexams A2150-563 examcollection | Killexams HP0-724 bootcamp | Killexams P3OF dump | Killexams C2090-102 brain dumps | Killexams 00M-653 questions and answers | Killexams 9A0-411 free pdf | Killexams 000-M37 exam prep | Killexams A00-204 questions answers | Killexams C2090-645 test prep | Killexams LOT-922 exam questions | Killexams 1Z0-047 exam prep | Killexams LOT-929 study guide | Killexams CMQ-OE braindumps | Killexams HP2-K32 test prep | Killexams HP0-311 questions and answers | Killexams 000-196 braindumps | Killexams STAAR rehearse exam |


Exam Simulator : Pass4sure 9L0-060 VCE Exam Simulator

View Complete list of Killexams.com Brain dumps


Killexams 250-502 study guide | Killexams ACF-CCP braindumps | Killexams APMLE rehearse test | Killexams 9L0-508 braindumps | Killexams C5050-280 brain dumps | Killexams 642-447 test prep | Killexams C2180-277 exam questions | Killexams FCNSP.V5 existent questions | Killexams M2080-241 braindumps | Killexams P2150-739 questions answers | Killexams 000-973 dumps questions | Killexams 000-274 free pdf | Killexams 700-303 braindumps | Killexams HP0-S29 test prep | Killexams AXELOS-MSP rehearse questions | Killexams 920-551 exam prep | Killexams LOT-822 exam prep | Killexams 1Z0-063 brain dumps | Killexams 000-257 sample test | Killexams A2040-405 rehearse test |


Mac OS X 10.4 Service and Support

Pass 4 certain 9L0-060 dumps | Killexams.com 9L0-060 existent questions | http://heckeronline.de/

Mac OS X 10.6 Snow Leopard: the Ars Technica review | killexams.com existent questions and Pass4sure dumps

Mac OS X 10.6 Snow Leopard: the Ars Technica review reader comments 454 with 269 posters participating, including legend author Share this story
  • Share on Facebook
  • Share on Twitter
  • Share on Reddit
  • Mac OS X 10.4 Tiger: 150+ new featuresMac OS X 10.4 Tiger: 150+ new features

    In June of 2004, during the WWDC keynote address, Steve Jobs revealed Mac OS X 10.4 Tiger to developers and the public for the first time. When the finished product arrived in April of 2005, Tiger was the biggest, most important, most feature-packed release in the history of Mac OS X by a wide margin. Apple's marketing crusade reflected this, touting "over 150 new features."

    All those new features took time. Since its introduction in 2001, there had been at least one major release of Mac OS X each year. Tiger took over a year and a half to arrive. At the time, it definitely seemed worth the wait. Tiger was a hit with users and developers. Apple took the lesson to heart and quickly set expectations for the next major release of Mac OS X, Leopard. Through various channels, Apple communicated its objective to roam from a 12-month to an 18-month release cycle for Mac OS X. Leopard was officially scheduled for "spring 2007."

    As the date approached, Apple's marketing machine trod a predictable path.

    Steve Jobs at WWDC 2007, touting 300 new features in Mac OS X 10.5 LeopardSteve Jobs at WWDC 2007, touting 300 new features in Mac OS X 10.5 Leopard

    Apple even went so far as to list totality 300 new features on its website. As it turns out, "spring" was a bit optimistic. Leopard actually shipped at the terminate of October 2007, nearly two and a half years after Tiger. Did Leopard really occupy twice as many new features as Tiger? That's debatable. What's inescapable is that Leopard included a solid crop of new features and technologies, many of which they now select for granted. (For example, occupy you had a discussion with a potential Mac user since the release of Leopard without mentioning Time Machine? I certainly haven't.)

    Mac OS X appeared to breathe maturing. The progression was clear: longer release cycles, more features. What would Mac OS X 10.6 breathe like? Would it arrive three and a half years after Leopard? Would it and comprise 500 new features? A thousand?

    At WWDC 2009, Bertrand Serlet announced a roam that he described as "unprecedented" in the PC industry.

    Mac OS X 10.6 - Read Bertrand's lips: No New Features!Mac OS X 10.6 - Read Bertrand's lips: No New Features!

    That's right, the next major release of Mac OS X would occupy no new features. The product title reflected this: "Snow Leopard." Mac OS X 10.6 would merely breathe a variant of Leopard. Better, faster, more refined, more... uh... snowy.

    This was a risky strategy for Apple. After the rapid-fire updates of 10.1, 10.2, and 10.3 followed by the riot of new features and APIs in 10.4 and 10.5, could Apple really derive away with calling a "time out?" I imagine Bertrand was really sweating this announcement up on the stage at WWDC in front of a live audience of Mac developers. Their reaction? instinctive applause. There were even a few hoots and whistles.

    Many of these very developers applauded the "150+ new features" in Tiger and the "300 new features" in Leopard at past WWDCs. Now they were applauding zero new features for Snow Leopard? What explains this?

    It probably helps to know that the "0 New Features" coast came at the terminate of an hour-long presentation detailing the major new APIs and technologies in Snow Leopard. It was too quickly followed by a back-pedaling ("well, there is one new feature...") coast describing the addition of Microsoft Exchange support. In isolation, "no new features" may appear to imply stagnation. In context, however, it served as a developer-friendly affirmation.

    The overall message from Apple to developers was something dote this: "We're adding a ton of new things to Mac OS X that will waiton you write better applications and beget your existing code speed faster, and we're going to beget certain that totality this new stuff is rock-solid and as bug-free as possible. We're not going to overextend ourselves adding a raft of new customer-facing, marketing-friendly features. Instead, we're going to concentrate 100% on the things that impress you, the developers."

    But if Snow Leopard is a dote letter to developers, is it a Dear John letter to users? You know, those people that the marketing department might so crudely advert to as "customers." What's in it for them? Believe it or not, the sales pitch to users is actually quite similar. As exhausting as it has been for developers to support up with Apple's seemingly never-ending stream of new APIs, it can breathe just as taxing for customers to linger on top of Mac OS X's features. Exposé, a new Finder, Spotlight, a new Dock, Time Machine, a new Finder again, a new iLife and iWork almost every year, and on and on. And as much as developers scorn bugs in Apple's APIs, users who suffer those bugs as application crashes occupy just as much judgement to breathe annoyed.

    Enter Snow Leopard: the release where they totality derive a rupture from the new-features/new-bugs treadmill of Mac OS X development. That's the pitch.

    Uncomfortable realities

    But wait a second, didn't I just mention an "hour-long presentation" about Snow Leopard featuring "major new APIs and technologies?" When speaking to developers, Apple's message of "no new features" is another passage of saw "no new bugs." Snow Leopard is supposititious to fix ancient bugs without introducing new ones. But nothing says "new bugs, coming birthright up" quite dote major new APIs. So which is it?

    Similarly, for users, "no new features" connotes stability and reliability. But if Snow Leopard includes enough changes to the core OS to fill an hour-long overview session at WWDC more than a year before its release, can Apple really beget capable on this promise? Or will users terminate up with totality the disadvantages of a feature-packed release dote Tiger or Leopard—the inevitable 10.x.0 bugs, the unfamiliar, untried new functionality—but without any of the actual new features?

    Yes, it's enough to beget one quite cynical about Apple's existent motivations. To toss some more fuel on the fire, occupy a notice at the Mac OS X release timeline below. Next to each release, I've included a list of its most significant features.

    Mac OS X release timelineMac OS X release timeline

    That curve is taking on a decidedly droopy shape, as if it's being weighed down by the ever-increasing number of new features. (The releases are distributed uniformly on the Y axis.) Maybe you believe it's reasonable for the time between releases to stretch out as each one brings a heavier load of goodies than the last, but support in reason the rational consequence of such a curve over the longhorn haul.

    And yeah, there's a diminutive upwards kick at the terminate for 10.6, but remember, this is supposititious to breathe the "no new features" release. Version 10.1 had a similar no-frills focus but took a heck of a lot less time to arrive.

    Looking at this graph, it's arduous not to wonder if there's something siphoning resources from the Mac OS X progress effort. Maybe, say, some project that's in the first two or three major releases of its life, still in that steep, early section of its own timeline graph. Yes, I'm talking about the iPhone, specifically iPhone OS. The iPhone business has exploded onto Apple's balance sheets dote no other product before, even the iPod. It's too accruing developers at an alarming rate.

    It's not a stretch to imagine that many of the artists and developers who piled on the user-visible features in Mac OS X 10.4 and 10.5 occupy been reassigned to iPhone OS (temporarily or otherwise). After all, Mac OS X and iPhone OS share the very core operating system, the very language for GUI development, and many of the very APIs. Some workforce migration seems inevitable.

    And let's not forget the "Mac OS X" technologies that they later scholarly were developed for the iPhone and just happened to breathe announced for the Mac first (because the iPhone was still a secret), dote Core Animation and code signing. Such intrigue theories certainly aren't helped by WWDC keynote snubs and other indignities suffered by Mac OS X and the Mac in common since the iPhone arrived on the scene. And so, on top of everything else, Snow Leopard is tasked with restoring some luster to Mac OS X.

    Got totality that? A nearly two-year progress cycle, but no new features. Major new frameworks for developers, but few new bugs. Significant changes to the core OS, but more reliability. And a franchise rejuvenation with few user-visible changes.

    It's enough to spin a leopard white.

    The charge of entry

    Snow Leopard's opening overture to consumers is its price: $29 for those upgrading from Leopard. The debut release of Mac OS X 10.0 and the final four major releases occupy totality been $129, with no special pricing for upgrades. After eight years of this kindhearted of fiscal disciplining, Leopard users may well breathe tempted to discontinue reading birthright now and just fade pick up a copy. Snow Leopard's upgrade charge is well under the impulse purchase threshold for many people. Twenty-nine dollars plus some minimal even of faith in Apple's faculty to ameliorate the OS with each release, and boom, instant purchase.

    Still here? Good, because there's something else you necessity to know about Snow Leopard. It's an overture of a different sort, less of a come-on and more of a spur. Snow Leopard will only speed on Macs with Intel CPUs. Sorry (again), PowerPC fans, but this is the terminate of the line for you. The transition to Intel was announced over four years ago, and the final new PowerPC Mac was released in October 2005. It's time.

    But if Snow Leopard is meant to prod the PowerPC holdouts into the Intel age, its "no new features" stance (and the accompanying want of added visual flair) is working against it. For those running Leopard on a PowerPC-based Mac, there's precious diminutive in Snow Leopard to waiton thrust them over the (likely) four-digit charge wall of a new Mac. For PowerPC Mac owners, the threshold for a new Mac purchase remains mostly unchanged. When their ancient Mac breaks or seems too slow, they'll fade out and buy a new one, and it'll forward with Snow Leopard pre-installed.

    If Snow Leopard does terminate up motivating new Mac purchases by PowerPC owners, it will probably breathe the result of resignation rather than inspiration. An Intel-only Snow Leopard is most significant for what it isn't: a further extension of PowerPC life champion on the Mac platform.

    The final piquant group is owners of Intel-based Macs that are still running Mac OS X 10.4 Tiger. Apple shipped Intel Macs with Tiger installed for a diminutive over one year and nine months. Owners of these machines who never upgraded to Leopard are not eligible for the $29 upgrade to Snow Leopard. They're too apparently not eligible to purchase Snow Leopard for the traditional $129 price. Here's what Apple has to affirm about Snow Leopard's pricing (emphasis added).

    Mac OS X version 10.6 Snow Leopard will breathe available as an upgrade to Mac OS X version 10.5 Leopard in September 2009 [...] The Snow Leopard sole user license will breathe available for a suggested retail charge of $29 (US) and the Snow Leopard Family Pack, a sole household, five-user license, will breathe available for a suggested charge of $49 (US). For Tiger® users with an Intel-based Mac, the Mac Box Set includes Mac OS X Snow Leopard, iLife® '09 and iWork® '09 and will breathe available for a suggested charge of $169 (US) and a Family Pack is available for a suggested charge of $229 (US).

    Ignoring the family packs for a moment, this means that Snow Leopard will either breathe free with your new Mac, $29 if you're already running Leopard, or $169 if you occupy an Intel Mac running Tiger. People upgrading from Tiger will derive the latest version of iLife and iWork in the deal (if that's the usurp term), whether they want them or not. It certain seems dote there's an obvious site in this lineup for a $129 offering of Snow Leopard on its own. Then again, perhaps it totality comes down to how, exactly, Apple enforces the $29 Snow Leopard upgrade policy.

    (As an aside to non-Mac users, note that the non-server version of Mac OS X has no per-user serial number and no activation scheme of any kind, and never has. "Registration" with Apple during the Mac OS X install process is entirely optional and is only used to collect demographic information. Failing to register (or entering entirely bogus registration information) has no consequence on your faculty to speed the OS. This is considered a genuine handicap of Mac OS X, but it too means that Apple has no trustworthy record of who, exactly, is a "legitimate" owner of Leopard.)

    One possibility was that the $29 Snow Leopard upgrade DVD would only install on top of an existing installation of Leopard. Apple has done this ilk of thing before, and it bypasses any proof-of-purchase annoyances. It would, however, insert a new problem. In the event of a arduous drive failure or simple decision to reinstall from scratch, owners of the $29 Snow Leopard upgrade would breathe forced to first install Leopard and then install Snow Leopard on top of it, perhaps more than doubling the installation time—and quintupling the annoyance.

    Given Apple's history in this area, no one should occupy been surprised to find out that Apple chose the much simpler option: the $29 "upgrade" DVD of Snow Leopard will, in fact, install on any supported Mac, whether or not it has Leopard installed. It will even install onto an entirely vacant arduous drive.

    To breathe clear, installing the $29 upgrade to Snow Leopard on a system not already running a properly licensed copy of Leopard is a violation of the end-user license agreement that comes with the product. But Apple's decision is a refreshing change: rewarding honest people with a hassle-free product rather than trying to punish untruthful people by treating everyone dote a criminal. This "honor system" upgrade enforcement policy partially explains the tall jump to $169 for the Mac Box Set, which ends up re-framed as an honest person's passage to derive iLife and iWork at their habitual prices, plus Snow Leopard for $11 more.

    And yes, speaking of installing, let's finally derive on with it.

    Installation

    Apple claims that Snow Leopard's installation process is "up to 45% faster." Installation times vary wildly depending on the speed, contents, and fragmentation of the target disk, the speed of the optical drive, and so on. Installation too only happens once, and it's not really an piquant process unless something goes terribly wrong. Still, if Apple's going to beget such a claim, it's worth checking out.

    To liquidate as many variables as possible, I installed both Leopard and Snow Leopard from one arduous disk onto another (empty) one. It should breathe illustrious that this change negates some of Snow Leopard's most famous installation optimizations, which are focused on reducing random data access from the optical disc.

    Even with this disadvantage, the Snow Leopard installation took about 20% less time than the Leopard installation. That's well short of Apple's "up to 45%" claim, but espy above (and don't forget the "up to" weasel words). Both versions installed in less than 30 minutes.

    What is striking about Snow Leopard's installation is how quickly the initial Spotlight indexing process completed. Here, Snow Leopard was 74% faster in my testing. Again, the times are small (5:49 vs. 3:20) and again, new installations on vacant disks are not the norm. But the shorter wait for Spotlight indexing is worth noting because it's the first indication most users will derive that Snow Leopard means business when it comes to performance.

    Another notable thing about installation is what's not installed by default: Rosetta, the facility that allows PowerPC binaries to speed on Intel Macs. Okay Apple, they derive it. PowerPC is a stiff, bereft of life. It rests in peace. It's rung down the curtain and joined the choir invisible. As far as Apple is concerned, PowerPC is an ex-ISA.

    But not installing Rosetta by default? That seems a diminutive harsh, even foolhardy. What's going to betide when totality those users upgrade to Snow Leopard and then double-click what they've probably long since forgotten is a PowerPC application? Perhaps surprisingly, this is what happens:

    Rosetta: auto-installed for your convenienceRosetta: auto-installed for your convenience

    That's what I saw when I tried to launch Disk Inventory X on Snow Leopard, an application that, yes, I had long since forgotten was PowerPC-only. After I clicked the "Install" button, I actually expected to breathe prompted to insert the installer DVD. Instead, Snow Leopard reached out over the network, pulled down Rosetta from an Apple server, and installed it.

    Rosetta auto-install

    No reboot was required, and Disk Inventory X launched successfully after the Rosetta installation completed. Mac OS X has not historically made much expend of the install-on-demand approach to system software components, but the facility used to install Rosetta appears quite robust. Upon clicking "Install," an XML property list containing a vast catalog of available Mac OS X packages was downloaded. Snow Leopard uses the very facility to download and install printer drivers on demand, saving another trip to the installer DVD. I hope this technique gains even wider expend in the future.

    Installation footprint

    Rosetta aside, Snow Leopard simply puts fewer bits on your disk. Apple claims it "takes up less than half the disk space of the previous version," and that's no lie. A clean, default install (including fully-generated Spotlight indexes) is 16.8 GB for Leopard and 5.9 GB for Snow Leopard. (Incidentally, these numbers are both powers-of-two measurements; espy sidebar.)

    A gigabyte by any other name

    Snow Leopard has another trick up its sleeve when it comes to disk usage. The Snow Leopard Finder considers 1 GB to breathe equal to 109 (1,000,000,000) bytes, whereas the Leopard Finder—and, it should breathe noted, every version of the Finder before it—equates 1 GB to 230 (1,073,741,824) bytes. This has the consequence of making your arduous disk suddenly materialize larger after installing Snow Leopard. For example, my "1 TB" arduous drive shows up in the Leopard Finder as having a capacity of 931.19 GB. In Snow Leopard, it's 999.86 GB. As you might occupy guessed, arduous disk manufacturers expend the powers-of-ten system. It's totality quite a mess, really. Though I forward down pretty firmly on the powers-of-two side of the fence, I can't guilt Apple too much for wanting to match up nicely with the long-established (but still dumb, reason you) arduous disk vendors' capacity measurement standard.

    Snow Leopard has several weight loss secrets. The first is obvious: no PowerPC champion means no PowerPC code in executables. Recall the maximum workable binary payload in a Leopard executable: 32-bit PowerPC, 64-bit PowerPC, x86, and x86_64. Now cross half of those architectures off the list. Granted, very few applications in Leopard included 64-bit code of any kind, but it's a 50% reduction in size for executables no matter how you slice it.

    Of course, not totality the files in the operating system are executables. There are data files, images, audio files, even a diminutive video. But most of those non-executable files occupy one thing in common: they're usually stored in compressed file formats. Images are PNGs or JPEGs, audio is AAC, video is MPEG-4, even preference files and other property lists now default to a compact binary format rather than XML.

    In Snow Leopard, other kinds of files climb on board the compression bandwagon. To give just one example, ninety-seven percent of the executable files in Snow Leopard are compressed. How compressed? Let's look:

    % cd Applications/Mail.app/Contents/MacOS % ls -l Mail -rwxr-xr-x@ 1 root wheel 0 Jun 18 19:35 Mail

    Boy, that's, uh, pretty small, huh? Is this really an executable or what? Let's check their assumptions.

    % file Applications/Mail.app/Contents/MacOS/Mail Applications/Mail.app/Contents/MacOS/Mail: empty

    Yikes! What's going on here? Well, what I didn't divulge you is that the commands shown above were speed from a Leopard system looking at a Snow Leopard disk. In fact, totality compressed Snow Leopard files materialize to accommodate zero bytes when viewed from a pre-Snow Leopard version of Mac OS X. (They notice and act perfectly customary when booted into Snow Leopard, of course.)

    So, where's the data? The diminutive "@" at the terminate of the permissions string in the ls output above (a feature introduced in Leopard) provides a clue. Though the Mail executable has a zero file size, it does occupy some extended attributes:

    % xattr -l Applications/Mail.app/Contents/MacOS/Mail com.apple.ResourceFork: 0000 00 00 01 00 00 2C F5 F2 00 2C F4 F2 00 00 00 32 .....,...,.....2 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ (184,159 lines snipped) 2CF610 63 6D 70 66 00 00 00 0A 00 01 FF FF 00 00 00 00 cmpf............ 2CF620 00 00 00 00 .... com.apple.decmpfs: 0000 66 70 6D 63 04 00 00 00 A0 82 72 00 00 00 00 00 fpmc......r.....

    Ah, there's totality the data. But wait, it's in the resource fork? Weren't those deprecated about eight years ago? Indeed they were. What you're witnessing here is yet another addition to Apple's favorite file system hobbyhorse, HFS+.

    At the dawn of Mac OS X, Apple added journaling, symbolic links, and arduous links. In Tiger, extended attributes and access control lists were incorporated. In Leopard, HFS+ gained champion for arduous links to directories. In Snow Leopard, HFS+ learns another new trick: per-file compression.

    The presence of the com.apple.decmpfs refer is the first hint that this file is compressed. This refer is actually hidden from the xattr command when booted into Snow Leopard. But from a Leopard system, which has no scholarship of its special significance, it shows up as unpretentious as day.

    Even more information is revealed with the waiton of Mac OS X Internals guru Amit Singh's hfsdebug program, which has quietly been updated for Snow Leopard.

    % hfsdebug /Applications/Mail.app/Contents/MacOS/Mail ... compression magic = cmpf compression ilk = 4 (resource fork has compressed data) uncompressed size = 7500336 bytes

    And certain enough, as they saw, the resource fork does indeed accommodate the compressed data. Still, why the resource fork? It's totality share of Apple's usual, ingenious backward-compatibility gymnastics. A recent sample is the passage that arduous links to directories present up—and function—as aliases when viewed from a pre-Leopard version of Mac OS X.

    In the case of a HFS+ compression, Apple was (understandably) unable to beget pre-Snow Leopard systems read and interpret the compressed data, which is stored in ways that did not exist at the time those earlier operating systems were written. But rather than letting applications (and users) running on pre-10.6 systems choke on—or worse, deprave through modification—the unexpectedly compressed file contents, Apple has chosen to conceal the compressed data instead.

    And where can the complete contents of a potentially large file breathe hidden in such a passage that pre-Snow Leopard systems can still copy that file without the loss of data? Why, in the resource fork, of course. The Finder has always correctly preserved Mac-specific metadata and both the resource and data forks when touching or duplicating files. In Leopard, even the lowly cp and rsync commands will consequence the same. So while it may breathe a diminutive bit spooky to espy totality those "empty" 0 KB files when looking at a Snow Leopard disk from a pre-Snow Leopard OS, the casual of data loss is small, even if you roam or copy one of the files.

    The resource fork isn't the only site where Apple has decided to smuggle compressed data. For smaller files, hfsdebug shows the following:

    % hfsdebug /etc/asl.conf ... compression magic = cmpf compression ilk = 3 (xattr has compressed data) uncompressed size = 860 bytes

    Here, the data is small enough to breathe stored entirely within an extended attribute, albeit in compressed form. And then, the final frontier:

    % hfsdebug /Volumes/Snow Time/Applications/Mail.app/Contents/PkgInfo ... compression magic = cmpf compression ilk = 3 (xattr has inline data) uncompressed size = 8 bytes

    That's right, an entire file's contents stored uncompressed in an extended attribute. In the case of a measure PkgInfo file dote this one, those contents are the four-byte classic Mac OS ilk and creator codes.

    % xattr -l Applications/Mail.app/Contents/PkgInfo com.apple.decmpfs: 0000 66 70 6D 63 03 00 00 00 08 00 00 00 00 00 00 00 fpmc............ 0010 FF 41 50 50 4C 65 6D 61 6C .APPLemal

    There's still the very "fpmc..." preamble seen in totality the earlier examples of the com.apple.decmpfs attribute, but at the terminate of the value, the expected data appears as unpretentious as day: ilk code "APPL" (application) and creator code "emal" (for the Mail application—cute, as per classic Mac OS tradition).

    You may breathe wondering, if this is totality about data compression, how does storing eight uncompressed bytes plus a 17-byte preamble in an extended refer save any disk space? The acknowledge to that lies in how HFS+ allocates disk space. When storing information in a data or resource fork, HFS+ allocates space in multiples of the file system's allocation obscure size (4 KB, by default). So those eight bytes will select up a minimum of 4,096 bytes if stored in the traditional way. When allocating disk space for extended attributes, however, the allocation obscure size is not a factor; the data is packed in much more tightly. In the end, the actual space saved by storing those 25 bytes of data in an extended refer is over 4,000 bytes.

    But compression isn't just about saving disk space. It's too a classic sample of trading CPU cycles for decreased I/O latency and bandwidth. Over the past few decades, CPU performance has gotten better (and computing resources more plentiful—more on that later) at a much faster rate than disk performance has increased. Modern arduous disk quest times and rotational delays are still measured in milliseconds. In one millisecond, a 2 GHz CPU goes through two million cycles. And then, of course, there's still the actual data transfer time to consider.

    Granted, several levels of caching throughout the OS and hardware labor mightily to conceal these delays. But those bits occupy to forward off the disk at some point to fill those caches. Compression means that fewer bits occupy to breathe transferred. Given the almost comical glut of CPU resources on a modern multi-core Mac under customary use, the total time needed to transfer a compressed payload from the disk and expend the CPU to decompress its contents into remembrance will still usually breathe far less than the time it'd select to transfer the data in uncompressed form.

    That explains the potential performance benefits of transferring less data, but the expend of extended attributes to store file contents can actually beget things faster, as well. It totality has to consequence with data locality.

    If there's one thing that slows down a arduous disk more than transferring a large amount of data, it's touching its heads from one share of the disk to another. Every roam means time for the head to start moving, then stop, then ensure that it's correctly positioned over the desired location, then wait for the spinning disk to allot the desired bits beneath it. These are totality real, physical, touching parts, and it's incredible that they consequence their dance as quickly and efficiently as they do, but physics has its limits. These motions are the existent performance killers for rotational storage dote arduous disks.

    The HFS+ volume format stores totality its information about files—metadata—in two primary locations on disk: the Catalog File, which stores file dates, permissions, ownership, and a host of other things, and the Attributes File, which stores "named forks."

    Extended attributes in HFS+ are implemented as named forks in the Attributes File. But unlike resource forks, which can breathe very large (up to the maximum file size supported by the file system), extended attributes in HFS+ are stored "inline" in the Attributes File. In practice, this means a circumscribe of about 128 bytes per attribute. But it too means that the disk head doesn't necessity to select a trip to another share of the disk to derive the actual data.

    As you can imagine, the disk blocks that beget up the Catalog and Attributes files are frequently accessed, and therefore more likely than most to breathe in a cache somewhere. totality of this conspires to beget the complete storage of a file, including both its metadata in its data, within the B-tree-structured Catalog and Attributes files an overall performance win. Even an eight-byte payload that balloons to 25 bytes is not a concern, as long as it's still less than the allocation obscure size for customary data storage, and as long as it totality fits within a B-tree node in the Attributes File that the OS has to read in its entirety anyway.

    There are other significant contributions to Snow Leopard's reduced disk footprint (e.g., the removal of unnecessary localizations and "designable.nib" files) but HFS+ compression is by far the most technically interesting.

    Installer intelligence

    Apple makes two other piquant promises about the installation process:

    Snow Leopard checks your applications to beget certain they're compatible and sets aside any programs known to breathe incompatible. In case a power outage interrupts your installation, it can start again without losing any data.

    The setting aside of "known incompatible" applications is undoubtedly a response to the "blue screen" problems some users encountered when upgrading from Tiger to Leopard two years ago, which was caused by the presence of incompatible—and some would affirm "illicit"—third-party system extensions. I occupy a decidedly pragmatic view of such software, and I'm glad to espy Apple taking a similarly practical approach to minimizing its impact on users.

    Apple can't breathe expected to detect and disable totality potentially incompatible software, of course. I suspect only the most common or highest profile risky software is detected. If you're a developer, this installer feature may breathe a capable passage to find out if you're on Apple's sh*t list.

    As for continuing an installation after a power failure, I didn't occupy the guts to test this feature. (I too occupy a UPS.) For long-running processes dote installation, this kindhearted of added robustness is welcome, especially on battery-powered devices dote laptops.

    I mention these two details of the installation process mostly because they highlight the kinds of things that are workable when developers at Apple are given time to polish their respective components of the OS. You might believe that the installer team would breathe hard-pressed to forward up with enough to consequence during a nearly two-year progress cycle. That's clearly not the case, and customers will gleam the benefits.

    Snow Leopard's new looks

    I've long yearned for Apple to beget a clean break, at least visually, from Mac OS X's Aqua past. Alas, I will breathe waiting a bit longer, because Snow Leopard ushers in no such revolution. And yet here I am, beneath a familiar-looking section heading that seems to attest otherwise. The verity is, Snow Leopard actually changes the appearance of nearly every pixel on your screen—but not in the passage you might imagine.

    Since the dawn of color on the Macintosh, the operating system has used a default output gamma correction value of 1.8. Meanwhile, Windows—aka the ease of the world—has used a value of 2.2. Though this may not appear significant to anyone but professional graphics artists, the disagreement is usually apparent to even a casual observer when viewing the very image on both kinds of displays side by side.

    Though Mac users will probably instinctively prefer the 1.8 gamma image that they're used to, Apple has decided that this historical disagreement is more pains than it's worth. The default output gamma correction value in Snow Leopard is now 2.2, just dote everyone else. Done and done.

    If they notice at all, users will likely suffer this change as a sentiment that the Snow Leopard user interface has a bit more contrast than Leopard's. This is reinforced by the new default desktop background, a re-drawn, more saturated version of Leopard's default desktop. (Note that these are two entirely different images and not an attempt to demonstrate the effects of different gamma correction settings.)

    LeopardLeopard Snow LeopardSnow Leopard Dock Exposé spotlight effectDock Exposé spotlight effect

    But even beyond color correction, capable to form, Apple could not resist adding a few graphical tweaks to the Snow Leopard interface. The most apparent changes are related to the Dock. First, there's the new "spotlight" notice triggered by a click-and-hold on an application icon in the Dock. (This activates Exposé, but only for the windows belonging to the application that was clicked. More later.)

    Furthermore, any and totality pop-up menus on the Dock—and only on the Dock—have a unique notice in Snow Leopard, complete with a custom selection appearance (which, for a change, does a passable job of matching the system-wide selection appearance setting).

    New Dock menu appearance. Mmmm… arbitrary.New Dock menu appearance. Mmmm… arbitrary.

    For Mac users of a inescapable age, these menus may bring to reason Apple's Hi-Tech appearance theme from the bad-old days of Copland. They're actually considerably more subtle, however. Note the translucent edges which accentuate the rounded corners. The gradient on the selection highlight is too admirably restrained.

    Nevertheless, this is an entirely new notice for a sole (albeit commonly used) application, and it does clash a bit with the default "slanty, shiny shelf" appearance of the Dock. But I've already had my affirm about that, and more. If the oath of Snow Leopard's appearance was to "first, consequence no harm," then I believe I'm inclined to give it a passing grade—almost.

    If I had to characterize what's wrong with Snow Leopard's visual additions with just two words, it'd breathe these: everything fades. Apple has sprinkled Core Animation fairy dust over seemingly every application in Snow Leopard. If any share of the user interface appears, disappears, or changes in any significant way, it's accompanied by an animation and one or more fades.

    In moderation, such effects are fine. But in several instances, Snow Leopard crosses the line. Or rather, it crosses my line, which, it should breathe noted, is located far inside the territories of Candy Land. Others with a much lower tolerance for animations who are already galled by the frippery in Leopard and earlier releases will find diminutive to dote in Snow Leopard's visual changes.

    The one that really drove me over the edge is the fussy diminutive dance of the filename district that occurs in the Finder (surprise!) when renaming a file on the desktop. There's just something about so many cross-fades, color changes, and text offsets occurring so rapidly and concentrated into such a small district that makes me want to scream. And whether or not I'm actually waiting for these animations to finish before I can continue to expend my computer, it certainly feels that passage sometimes.

    Still, I must unenthusiastically predict that most customary people (i.e., the ones who will not read this entire article) will either find these added visual touches delightful, or (much more likely) not notice them at all.

    Branding

    Animation aside, the visual sameness of Snow Leopard presents a bit of a marketing challenge for Apple. Even beyond the obvious problem of how to promote an operating system upgrade with "no new features" to consumers, there's the issue of how to derive people to notice that this new product exists at all.

    In the run-up to Snow Leopard's release, Apple stuck to a modified version of Leopard's outer space theme. It was in the keynote slideshows, on the WWDC banners, on the developer release DVDs, and totality over the Mac OS X section of Apple's website. The header image from Apple's Mac OS X webpage as of a week before Snow Leopard's release appears below. It's pretty gash and dried: outer space, stars, loaded purple nebula, lens flare.

    Snow. The final frontier.Snow. The final frontier.

    Then came the golden master of Snow Leopard, which, in a pleasant change from past releases, was distributed to developers a few weeks before Snow Leopard hit the shelves. Its installer introduced an entirely different notice which, as it turns out, was carried over to the retail packaging. For a change, let's line up the discs instead of the packaging (which is rapidly shrinking to barely fence the disc anyway). Here's Mac OS X 10.0 through 10.6, top to bottom and left to right. (The 10.0 and 10.1 discs looked essentially identical and occupy been coalesced.)

    One of these things is not dote
 the others…One of these things is not dote the others…

    Yep, it's a snow leopard. With actual snow on it. It's a bit on the nose for my taste, but it's not without its charms. And it does occupy one tall thing going for it: it's immediately recognizable as something new and different. "Unmistakable" is how I'd sum up the packaging. Eight years of the giant, centered, variously adorned "X" and then boom: a cat. There's diminutive casual that anyone who's seen Leopard sitting on the shelf of their local Apple store for the past two years will fail to notice that this is a new product.

    (If you'd dote your own picture of Snowy the snow leopard (that's right, I've named him), Apple was kindhearted enough to comprise a desktop background image with the OS. Self-loathing Windows users may download it directly.)

    Warning: internals ahead

    We've arrived at the start of the customary "internals" section. Snow Leopard is totality about internal changes, and this is reflected in the content of this review. If you're only interested in the user-visible changes, you can skip ahead, but you'll breathe missing out on the meat of this review and the heart of Apple's new OS.

    64-bit: the road leads ever on

    Mac OS X started its journey to 64-bit back in 2003 with the release of Panther, which included the bare minimum champion for the then-new PowerPC G5 64-bit CPU. In 2005, Tiger brought with it the faculty to create capable 64-bit processes—as long as they didn't link with any of the GUI libraries. Finally, Leopard in 2007 included champion for 64-bit GUI applications. But again, there was a caveat: 64-bit champion extended to Cocoa applications only. It was, effectively, the terminate of the road for Carbon.

    Despite Leopard's seemingly impressive 64-bit bona fides, there are a few more steps before Mac OS X can gain complete 64-bit nirvana. The diagrams below illustrate.

    64-bit in Mac OS X 10.4 Tiger 64-bit in Mac OS X 10.5 Leopard 64-bit in Mac OS X 10.6 Snow Leopard Mac OS X 10.4 Tiger Mac OS X 10.5 Leopard Mac OS X 10.6 Snow Leopard

    As we'll see, totality that yellow in the Snow Leopard diagram represents its capability, not necessarily its default mode of operation.

    K64

    Snow Leopard is the first version of Mac OS X to ship with a 64-bit kernel ("K64" in Apple's parlance), but it's not enabled by default on most systems. The judgement for this this is simple. Recall that there's no "mixed mode" in Mac OS X. At runtime, a process is either 32-bit or 64-bit, and can only load other code—libraries, plug-ins, etc.—of the very kind.

    An famous class of plug-ins loaded by the kernel is device drivers. Were Snow Leopard to default to the 64-bit kernel, only 64-bit device drivers would load. And seeing as Snow Leopard is the first version of Mac OS X to comprise a 64-bit kernel, there'd breathe precious few of those on customers' systems on launch day.

    And so, by default, Snow Leopard boots with a 64-bit kernel only on Xserves from 2008 or later. I guess the assumption is that totality of the devices commonly attached to an Xserve will breathe supported by 64-bit drivers supplied by Apple in Snow Leopard itself.

    Perhaps surprisingly, not totality Macs with 64-bit processors are even able to boot into the 64-bit kernel. Though this may change in subsequent point releases of Snow Leopard, the table below lists totality the Macs that are either capable of or default to booting K64. (To find the "Model name" of your Mac, select "About This Mac" from the Apple menu, then click the "More info…" button and read the "Model Identifier" line in the window that appears.)

    Product Model name K64 status Early 2008 Mac Pro MacPro3,1 Capable Early 2008 Xserve Xserve2,1 Default MacBook Pro 15"/17" MacBookPro4,1 Capable iMac iMac8,1 Capable UniBody MacBook Pro 15" MacBookPro5,1 Capable UniBody MacBook Pro 17" MacBookPro5,2 Capable Mac Pro MacPro4,1 Capable iMac iMac9,1 Capable Early 2009 Xserve Xserve3,1 Default

    For totality K64-capable Macs, boot while holding down "6" and "4" keys simultaneously to select the 64-bit kernel. For a more permanent solution, expend the nvram command to add arch=x86_64 to your boot-args string, or edit the file /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and add arch=x86_64 to the Kernel Flags string:

    ... <key>Kernel</key> <string>mach_kernel</string> <key>Kernel Flags</key> <string>arch=x86_64</string> ...

    To switch back to the 32-bit kernel, hold down the "3" and "2" keys during boot, or expend one of the techniques above, replacing "x86_64" with "i386".

    We've already discussed why, at least initially, you probably won't want to boot into K64. But as Snow Leopard adoption ramps up and 64-bit updates of existing kernel extensions become available, why might you actually want to expend the 64-bit kernel?

    The first judgement has to consequence with RAM, and not in the passage you might think. Though Leopard uses a 32-bit kernel, Macs running Leopard can accommodate and expend far more RAM than the 4 GB circumscribe the "32-bit" qualifier might appear to imply. But as RAM sizes increase, there's another concern: address space depletion—not for applications, but for the kernel itself.

    As a 32-bit process, the kernel itself is limited to a 32-bit (i.e., 4GB) address space. That may not appear dote a problem; after all, should the kernel really necessity more than 4GB of remembrance to consequence its job? But bethink that share of the kernel's job is to track and manage system memory. The kernel uses a 64-byte structure to track the status of each 4KB page of RAM used on the system.

    That's 64 bytes, not kilobytes. It hardly seems dote a lot. But now regard a Mac in the not-too-distant future containing 96GB of RAM. (If this sounds ridiculous to you, believe of how ridiculous the 8GB of RAM in the Mac I'm typing on birthright now would occupy sounded to you five years ago.) Tracking 96GB of RAM requires 1.5GB of kernel address space. Using more than a third of the kernel's address space just to track remembrance is a pretty uncomfortable situation.

    A 64-bit kernel, on the other hand, has a virtually unlimited kernel address space (16 exabytes). K64 is an inevitable necessity, given the rapidly increasing size of system memory. Though you may not necessity it today on the desktop, it's already common for servers to occupy double-digit gigabytes of RAM installed.

    The other thing K64 has going for it is speed. The x86 instruction set architecture has had a bit of a tortured history. When designing the x86-64 64-bit extension of the x86 architecture, AMD took the occasion to leave behind some of the ugliness of the past and comprise more modern features: more registers, new addressing modes, non-stack-based floating point capabilities, etc. K64 reaps these benefits. Apple makes the following claims about its performance:

  • 250% faster system summon entry point
  • 70% faster user/kernel remembrance copy
  • Focused benchmarking would endure these out, I'm sure. But in daily use, you're unlikely to breathe able to refer any particular performance boost to the kernel. believe of K64 as removing bottlenecks from the few (usually server-based) applications that actually consequence exercise these aspects of the kernel heavily.

    If it makes you feel better to know that your kernel is operating more efficiently, and that, were you to actually occupy 96GB of RAM installed, you would not risk starving the kernel of address space, and if you don't occupy any 32-bit drivers that you absolutely necessity to use, then by totality means, boot into the 64-bit kernel.

    For everyone else, my advice is to breathe glad that K64 will breathe ready and waiting for you when you eventually consequence necessity it—and tickle consequence embolden totality the vendors that beget kernel extensions that you trust about to add K64 champion as soon as possible.

    Finally, this is worth repeating: tickle support in reason that you consequence not necessity to speed the 64-bit kernel in order to speed 64-bit applications or install more than 4GB of RAM in your Mac. Applications speed just fine in 64-bit mode on top of the 32-bit kernel, and even in earlier versions of Mac OS X it's been workable to install and select handicap of much more than 4GB of RAM.

    64-bit applications

    While Leopard may occupy brought with it champion for 64-bit GUI applications, it actually included very few of them. In fact, by my count, only two 64-bit GUI applications shipped with Leopard: Xcode (an optional install) and Chess. And though Leopard made it workable for third-party developers to yield 64-bit (albeit Leopard-only) GUI applications, very few have—sometimes due to luckless realities, but most often because there's been no capable judgement to consequence so, abandoning users of Mac OS X 10.4 or earlier in the process.

    Apple is now pushing the 64-bit transition much harder. This starts with leading by example. Snow Leopard ships with four end-user GUI applications that are not 64-bit: iTunes, Grapher, Front Row, and DVD Player. Everything else is 64-bit. The Finder, the Dock, Mail, TextEdit, Safari, iChat, Address Book, Dashboard, waiton Viewer, Installer, Terminal, Calculator—you title it, it's 64-bit.

    The second tall carrot (or stick, depending on how you notice at it) is the continued want of 32-bit champion for new APIs and technologies. Leopard started the trend, leaving deprecated APIs behind and only porting the new ones to 64-bit. The improved Objective-C 2.0 runtime introduced in Leopard was too 64-bit-only.

    Snow Leopard continues along similar lines. The Objective-C 2.1 runtime's non-fragile instance variables, exception model unified with C++, and faster vtable dispatch remain available only to 64-bit applications. But the most significant new 64-bit-only API is QuickTime X—significant enough to breathe addressed separately, so linger tuned.

    64-bits or bust

    All of this is Apple's not-so-subtle passage of telling developers that the time to roam to 64-bit is now, and that 64-bit should breathe the default for totality new applications, whether a developer thinks it's "needed" or not. In most cases, these new APIs occupy no intrinsic connection to 64-bit. Apple has simply chosen to expend them as additional forms of persuasion.

    Despite totality of the above, I'd still summon Snow Leopard merely the penultimate step in Mac OS X's journey to breathe 64-bit from top to bottom. I fully await Mac OS X 10.7 to boot into the 64-bit kernel by default, to ship with 64-bit versions of totality applications, plug-ins, and kernel extensions, and to leave even more legacy and deprecated APIs to fade away in the land of 32-bit.

    QuickTime X

    Apple did something a bit odd in Leopard when it neglected to port the C-based QuickTime API to 64-bit. At the time, it didn't appear dote such a tall deal. Mac OS X's transition to 64-bit had already spanned many years and several major versions. One could imagine that it just wasn't yet QuickTime's spin to fade 64-bit.

    As it turns out, my terse but pessimistic assessment of the situation at the time was accurate: QuickTime got the "Carbon treatment". dote Carbon, the venerable QuickTime API that they know and dote will not breathe making the transition to 64-bit—ever.

    To breathe clear, QuickTime the technology and QuickTime the brand will most definitely breathe coming to 64-bit. What's being left behind in 32-bit-only shape is the C-based API introduced in 1991 and built upon for 18 years thereafter. Its replacement in the world of 64-bit in Snow Leopard is the aptly named QuickTime X.

    The "X" in QuickTime X, dote the one in in Mac OS X, is pronounced "ten." This is but the first of many eerie parallels. dote Mac OS X before it, QuickTime X:

  • aims to beget a clean rupture from its predecessor
  • is based on technology originally developed for another platform
  • includes transparent compatibility with its earlier incarnation
  • promises better performance and a more modern architecture
  • lacks many famous features in its initial release
  • Maximum available Mac CPU speed (MHz)Maximum available Mac CPU speed (MHz)

    Let's select these one at a time. First, why is a clean rupture needed? allot simply, QuickTime is old—really old. The horribly blocky, postage-stamp-size video displayed by its initial release in 1991 was considered a technological tour de force.

    At the time, the fastest Macintosh money could buy contained a 25 MHz CPU. The ridiculous chart to the birthright is meant to hammer home this point. Forward-thinking design can only derive you so far. The shape of the world a technology is born into eventually, inevitably dictates its fate. This is especially capable for long-lived APIs dote QuickTime with a stout bent towards backward compatibility.

    As the first successful implementation of video on a personal computer, it's frankly incredible that the QuickTime API has lasted as long as it has. But the world has moved on. Just as Mac OS create itself mired in a ghetto of cooperative multitasking and unprotected memory, QuickTime limps into 2009 with antiquated notions of concurrency and subsystem layering baked into its design.

    When it came time to write the video-handling code for the iPhone, the latest version of QuickTime, QuickTime 7, simply wasn't up to the task. It had grown too bloated and inefficient during its life on the desktop, and it lacked capable champion for the GPU-accelerated video playback necessary to handle modern video codecs on a handheld (even with a CPU sixteen times the clock speed of any available in a Mac when QuickTime 1.0 was released). And so, Apple created a tight, modern, GPU-friendly video playback engine that could meet comfortably within the RAM and CPU constraints of the iPhone.

    Hmm. An aging desktop video API in necessity of a replacement. A fresh, new video library with capable performance even on (comparatively) anemic hardware. Apple connected the dots. But the trick is always in the transition. Happily, this is Apple's forte. QuickTime itself has already lived on three different CPU architectures and three entirely different operating systems.

    The switch to 64-bit is yet another (albeit less dramatic) inflection point, and Apple has chosen it to impress the boundary between the ancient QuickTime 7 and the new QuickTime X. It's done this in Snow Leopard by limiting totality expend of QuickTime by 64-bit applications to the QTKit Objective-C framework.

    QTKit's new world order

    QTKit is not new; it began its life in 2005 as a more native-feeling interface to QuickTime 7 for Cocoa applications. This extra layer of abstraction is the key to the QuickTime X transition. QTKit now hides within its object-oriented walls both QuickTime 7 and QuickTime X. Applications expend QTKit as before, and behind the scenes QTKit will pick whether to expend QuickTime 7 or QuickTime X to fulfill each request.

    If QuickTime X is so much better, why doesn't QTKit expend it for everything? The acknowledge is that QuickTime X, dote its Mac OS X namesake, has very limited capabilities in its initial release. While QuickTime X supports playback, capture, and exporting, it does not champion general-purpose video editing. It too supports only "modern" video formats—basically, anything that can breathe played by an iPod, iPhone, or Apple TV. As for other video codecs, well, you can forget about handling them with plug-ins because QuickTime X doesn't champion those either.

    For every one of the cases where QuickTime X is not up to the job, QuickTime 7 will fill in. Cutting, copying, and pasting portions of a video? QuickTime 7. Extracting individual tracks from a movie? QuickTime 7. Playing any movie not natively supported by an existing Apple handheld device? QuickTime 7. Augmenting QuickTime's codec champion using a plug-in of any kind? You guessed it: QuickTime 7.

    But wait a second. If QTKit is the only passage for a 64-bit application to expend QuickTime, and QTKit multiplexes between QuickTime 7 and QuickTime X behind the scenes, and QuickTime 7 is 32-bit-only, and Mac OS X does not champion "mixed mode" processes that can execute both 32-bit and 64-bit code, then how the heck does a 64-bit process consequence anything that requires the QuickTime 7 back-end?

    To find out, fire up the new 64-bit QuickTime Player application (which will breathe addressed separately later) and open a movie that requires QuickTime 7. Let's say, one that uses the Sorenson video codec. (Remember that? capable times.) certain enough, it plays just fine. But search for "QuickTime" in the Activity Monitor application and you'll espy this:

    Pretty sneaky, sis: 32-bit QTKitServer processPretty sneaky, sis: 32-bit QTKitServer process

    And the acknowledge is revealed. When a 64-bit application using QTKit requires the services of the 32-bit-only QuickTime 7 back-end, QTKit spawns a sever 32-bit QTKitServer process to consequence the labor and communicate the results back to the originating 64-bit process. If you leave Activity Monitor open while using the new QuickTime Player application, you can watch the QTKitServer processes forward and fade as needed. This is totality handled transparently by the QTKit framework; the application itself necessity not breathe aware of these machinations.

    Yes, it's going to breathe a long, long time before QuickTime 7 disappears completely from Mac OS X (at least Apple was kindhearted enough not to summon it "QuickTime Classic"), but the path forward is clear. With each new release of Mac OS X, await the capabilities of QuickTime X to expand, and the number of things that still require QuickTime 7 to decrease. In Mac OS X 10.7, for example, I imagine that QuickTime X will gain champion for plug-ins. And surely by Mac OS X 10.8, QuickTime X will occupy complete video editing support. totality this will breathe happening beneath the unifying facade of QTKit until, eventually, the QuickTime 7 back-end is no longer needed at all.

    Say what you mean

    In the meantime, perhaps surprisingly, many of the current limitations of QuickTime X actually highlight its unique advantages and inform the evolving QTKit API. Though there is no direct passage for a developer to request that QTKit expend the QuickTime X back-end, there are several roundabout means to influence the decision. The key is the QTKit API, which relies heavily on the concept of intent.

    QuickTime versions 1 through 7 expend a sole representation of totality media resources internally: a Movie object. This representation includes information about the individual tracks that beget up the movie, the sample tables for each track, and so on—all the information QuickTime needs to understand and exploit the media.

    This sounds distinguished until you realize that to consequence anything with a media resource in QuickTime requires the construction of this comprehensive Movie object. regard playing an MP3 file with QuickTime, for example. QuickTime must create its internal Movie protest representation of the MP3 file before it can originate playback. Unfortunately, the MP3 container format seldom contains comprehensive information about the structure of the audio. It's usually just a stream of packets. QuickTime must laboriously scan and parse the entire audio stream in order to complete the Movie object.

    QuickTime 7 and earlier versions beget this process less painful by doing the scanning and parsing incrementally in the background. You can espy this in many QuickTime-based player applications in the shape of a progress bar overlaid on the movie controller. The image below shows a 63MB MP3 podcast loading in the Leopard version of QuickTime Player. The shaded portion of the movie timeline slowly fills the dotted district from left to right.

    QuickTime 7 doing more labor than necessary

    QuickTime 7 doing more labor than necessary

    Though playback can originate almost immediately (provided you play from the beginning, that is) it's worthwhile to select a step back and regard what's going on here. QuickTime is creating a Movie protest suitable for any operation that QuickTime can perform: editing, track extraction or addition, exporting, you title it. But what if totality I want to consequence is play the file?

    The pains is, the QuickTime 7 API lacks a passage to express this kindhearted of intent. There is no passage to affirm to QuickTime 7, "Just open this file as quickly as workable so that I can play it. Don't bother reading every sole byte of the file from the disk and parsing it to determine its structure just in case I settle to edit or export the content. That is not my intent. Please, just open it for playback."

    The QTKit API in Snow Leopard provides exactly this capability. In fact, the only passage to breathe eligible for the QuickTime X back-end at totality is to explicitly express your intent not to consequence anything QuickTime X cannot handle. Furthermore, any attempt to achieve an operation that lies outside your previously expressed intent will cause QTKit to raise an exception.

    The intent mechanism is too the passage that the new features of QuickTime X are exposed, such as the faculty to asynchronously load large or distantly located (e.g., over a unhurried network link) movie files without blocking the UI running on the main thread of the application.

    Indeed, there are many reasons to consequence what it takes to derive on board the QuickTime X train. For the media formats it supports, QuickTime X is less taxing on the CPU during playback than QuickTime 7. (This is beyond the fact that QuickTime X does not squander time preparing its internal representation of the movie for editing and export when playback is totality that's desired.) QuickTime X too supports GPU-accelerated playback of H.264, but, in this initial release, only on Macs equipped with an NVIDIA 9400M GPU (i.e., some 2009 iMacs and several models of MacBooks from 2008 and 2009). Finally, QuickTime X includes comprehensive ColorSync champion for video, which is long overdue.

    The X factor

    This is just the start of a long journey for QuickTime X, and seemingly not a very auspicious one, at that. A QuickTime engine with no editing support? No plug-ins? It seems ridiculous to release it at all. But this has been Apple's passage in recent years: steady, deliberate progress. Apple aims to ship no features before their time.

    As anxious as developers may breathe for a full-featured, 64-bit successor to the QuickTime 7 engine, Apple itself is sitting on top of one of the largest QuickTime-riddled (and Carbon-addled, to boot) code bases in the industry: Final gash Studio. Thus far, It remains stuck in 32-bit. To affirm that Apple is "highly motivated" to extend the capabilities of QuickTime X would breathe an understatement.

    Nevertheless, don't await Apple to rush forward foolishly. Duplicating the functionality of a continually developed, 18-year-old API will not betide overnight. It will select years, and it will breathe even longer before every famous Mac OS X application is updated to expend QTKit exclusively. Transitions. Gotta dote 'em.

    File system API unification

    Mac OS X has historically supported many different ways of referring to files on disk from within an application. Plain-old paths (e.g., /Users/john/Documents/myfile) are supported at the lowest levels of the operating system. They're simple, predictable, but perhaps not such a distinguished view to expend as the only passage an application tracks files. regard what happens if an application opens a file based on a path string, then the user moves that file somewhere else while it's still being edited. When the application is instructed to save the file, if it only has the file path to labor with, it will terminate up creating a new file in the ancient location, which is almost certainly not what the user wanted.

    Classic Mac OS had a more sophisticated internal representation of files that enabled it to track files independent of their actual locations on disk. This was done with the waiton of the unique file ids supported by HFS/HFS+. The Mac OS X incarnation of this concept is the FSRef data type.

    Finally, in the modern age, URLs occupy become the de facto representation for files that may breathe located somewhere other than the local machine. URLs can too advert to local files, but in that case they occupy totality the very disadvantages as file paths.

    This diversity of data types is reflected in Mac OS X's file system APIs. Some functions select file path as arguments, some await opaque references to files, and still others labor only with URLs. Programs that expend these APIs often spend a lot of their time converting file references from one representation to another.

    The situation is similar when it comes to getting information about files. There are a huge number of file system metadata retrieval functions at totality levels of the operating system, and no sole one of them is comprehensive. To derive totality available information about a file on disk requires making several sever calls, each of which may await a different ilk of file reference as an argument.

    Here's an sample Apple provided at WWDC. Opening a sole file in the Leopard version of the Preview image viewer application results in:

  • Four conversions of an FSRef to a file path
  • Ten conversions of a file path to an FSRef
  • Twenty-five calls to getattrlist()
  • Eight calls to stat()/lstat()
  • Four calls to open()/close()
  • In Snow Leopard, Apple has created a new, unified, comprehensive set of file system APIs built around a sole data type: URLs. But these are URL "objects"—namely, the opaque data types NSURL and CFURL, with a toll-free bridge between them—that occupy been imbued with totality the desirable attributes of an FSRef.

    Apple settled on these data types because their opaque nature allowed this kindhearted of enhancement, and because there are so many existing APIs that expend them. URLs are too the most future-proof of totality the choices, with the scheme portion providing nearly unlimited flexibility for new data types and access mechanisms. The new file system APIs built around these opaque URL types champion caching and metadata prefetching for a further performance boost.

    There's too a new on-disk representation called a Bookmark (not to breathe confused with a browser bookmark) which is dote a more network-savvy replacement for classic Mac OS aliases. Bookmarks are the most robust passage to create a reference to a file from within another file. It's too workable to attach whimsical metadata to each Bookmark. For example, if an application wants to support a persistent list of "favorite" files plus some application-specific information about them, and it wants to breathe resilient to any movement of these files behind its back, Bookmarks are the best appliance for the job.

    I mention totality of this not because I await file system APIs to breathe totality that piquant to people without my particular fascination with this share of the operating system, but because, dote Core Text before it, it's an indication of exactly how juvenile Mac OS X really is as a platform. Even after seven major releases, Mac OS X is still struggling to roam out from the shadow of its three ancestors: NeXTSTEP, classic Mac OS, and BSD Unix. Or perhaps it just goes to present how ruthlessly Apple's core OS team is driven to replace ancient and crusty APIs and data types with new, more modern versions.

    It will breathe a long time before the benefits of these changes trickle down (or is it up?) to end-users in the shape of Mac applications that are written or modified to expend these new APIs. Most well-written Mac applications already exhibit most of the desirable behavior. For example, the TextEdit application in Leopard will correctly detect when a file it's working on has moved.

    TextEdit: a capable Mac OS X citizenTextEdit: a capable Mac OS X citizen

    Of course, the key modifier here is "well-written." Simplifying the file system APIs means that more developers will breathe willing to expend the effort—now greatly reduced—to provide such user-friendly behaviors. The accompanying performance boost is just icing on the cake, and one more judgement that developers might pick to alter their existing, working application to expend these new APIs.

    Doing more with more

    Moore's Law is widely cited in technology circles—and too widely misunderstood. It's most often used as shorthand for "computers double in speed every year or so," but that's not what Gordon Moore wrote at all. His 1965 article in Electronics magazine touched on many topics in the semiconductor industry, but if it had to breathe summed up in a sole "law", it would be, roughly, that the number of transistors that meet onto a square inch of silicon doubles every 12 months.

    Moore later revised that to two years, but the time age is not what people derive wrong. The problem is confusing a doubling of transistor density with a doubling of "computer speed." (Even more problematic is declaring a "law" based on a sole paper from 1965, but we'll allot that aside for now. For a more thorough discussion of Moore's Law, tickle read this classic article by Jon Stokes.)

    For decades, each increase in transistor density was, in fact, accompanied by a comparable increase in computing speed thanks to ever-rising clock speeds and the dawn of superscalar execution. This worked great—existing code ran faster on each new CPU—until the grim realities of power density allot an terminate to the fun.

    Moore's Law continues, at least for now, but their faculty to beget code speed faster with each new increase in transistor density has slowed considerably. The free lunch is over. CPU clock speeds occupy stagnated for years, many times actually going backwards. (The latest top-of-the-line 2009 Mac Pro contains a 2.93 GHz CPU, whereas the 2008 model could breathe equipped with a 3.2 GHz CPU.) Adding execution units to a CPU has too long since reached the point of diminishing returns, given the limits of instruction-level parallelism in common application code.

    And yet we've still got totality these new transistors raining down on us, more every year. The challenge is to find new ways to expend them to actually beget computers faster.

    Thus far, the semiconductor industry's acknowledge has been to give us more of what they already have. Where once a CPU contained a sole rational processing unit, now CPUs in even the lowliest desktop computers accommodate two processor cores, with high-end models sporting two chips with eight rational cores each. Granted, the cores themselves are too getting faster, usually by doing more at the very clock speed as their predecessors, but that's not happening at nearly the rate that the cores are multiplying.

    Unfortunately, generally speaking, a dual-core CPU will not speed your application twice as snappily as a single-core CPU. In fact, your application probably won't speed any faster at totality unless it was written to select handicap of more than just a sole rational CPU. Presented with a glut of transistors, chipmakers occupy turned around and provided more computing resources than programmers know what to consequence with, transferring much of the responsibility for making computers faster to the software guys.

    We're with the operating system and we're here to help

    It's into this environment that Snow Leopard is born. If there's one responsibility (aside from security) that an operating system vendor should feel in the year 2009, it's finding a passage for applications—and the OS itself—to utilize the ever-growing wealth of computing resources at their disposal. If I had to pick sole technological "theme" for Snow Leopard, this would breathe it: helping developers utilize totality this newfound silicon; helping them consequence more with more.

    To that end, Snow Leopard includes two significant new APIs backed by several smaller, but equally famous infrastructure improvements. We'll start at the bottom with, believe it or not, the compiler.

    LLVM and Clang

    Apple made a strategic investment in the LLVM open source project several years ago. I covered the fundamentals of LLVM in my Leopard review. (If you're not up to speed, tickle entangle up on the topic before continuing.) In it, I described how Leopard used LLVM to provide dramatically more efficient JIT-compiled software implementations of OpenGL functions. I ended with the following admonition:

    Don't breathe misled by its humble expend in Leopard; Apple has imposing plans for LLVM. How grand? How about swapping out the guts of the gcc compiler Mac OS X uses now and replacing them with the LLVM equivalents? That project is well underway. Not ambitious enough? How about ditching gcc entirely, replacing it with a completely new LLVM-based (but gcc-compatible) compiler system? That project is called Clang, and it's already yielded some impressive performance results.

    With the introduction of Snow Leopard, it's official: Clang and LLVM are the Apple compiler strategy going forward. LLVM even has a snazzy new logo, a not-so-subtle homage to a well-known compiler design textbook:

    LLVM! Clang! Rawr!

    LLVM! Clang! Rawr!

    Apple now offers a total of four compilers for Mac OS X: GCC 4.0, GCC 4.2, LLVM-GCC 4.2 (the GCC 4.2 front-end combined with an LLVM back-end), and Clang, in order of increasing LLVM-ness. Here's a diagram:

    Mac OS X compilers

    Mac OS X compilers

    All of these compilers are binary-compatible on Mac OS X, which means you can, for example, build a library with one compiler and link it into an executable built with another. They're too totality command-line and source-compatible—in theory, anyway. Clang does not yet champion some of the more esoteric features of GCC. Clang too only supports C, Objective-C, and a diminutive bit of C++ (Clang(uage), derive it?) whereas GCC supports many more. Apple is committed to complete C++ champion for Clang, and hopes to labor out the remaining GCC incompatibilities during Snow Leopard's lifetime.

    Clang brings with it the two headline attributes you await in a hot, new compiler: shorter compile times and faster executables. In Apple's testing with its own applications such as iCal, Address Book, and Xcode itself, plus third-party applications dote Adium and Growl, Clang compiles nearly three times faster than GCC 4.2. As for the speed of the finished product, the LLVM back-end, whether used in Clang or in LLVM-GCC, produces executables that are 5-25% faster than those generated by GCC 4.2.

    Clang is too more developer-friendly than its GCC predecessors. I concede that this topic doesn't occupy much to consequence with taking handicap of multiple CPU cores and so on, but it's certain to breathe the first thing that a developer actually notices when using Clang. Indulge me.

    For starters, Clang is embeddable, so Xcode can expend the very compiler infrastructure for interactive features within the IDE (symbol look-up, code completion, etc.) as it uses to compile the final executable. Clang too creates and preserves more extensive metadata while compiling, resulting in much better error reporting. For example, when GCC tells you this:

    GCC error message for an unknown type

    It's not exactly limpid what the problem is, especially if you're new to C programming. Yes, totality you hotshots already know what the problem is (especially if you saw this sample at WWDC), but I believe everyone can coincide that this error, generated by Clang, is a lot more helpful:

    Clang error message for an unknown type

    Maybe a novice still wouldn't know what to do, but at least it's limpid where the problem lies. Figuring out why the compiler doesn't know about NSString is a much more focused chore than can breathe derived from GCC's cryptic error.

    Even when the message is clear, the context may not be. select this error from GCC:

    GCC error message for tainted operands

    Sure, but there are four "+" operators on that sole line. Which one has the problematic operands? Thanks to its more extensive metadata, Clang can pinpoint the problem:

    Clang error message for tainted operands

    Sometimes the error is perfectly clear, but it just seems a bit off, dote this situation where jumping to the error as reported by GCC puts you on the line below where you actually want to add the missing semicolon:

    GCC error message for missing semicolon

    The diminutive things count, you know? Clang goes that extra mile:

    Clang error message for missing semicolon

    Believe it or not, stuff dote this means a lot to developers. And then there are the not-so-little things that beofvalue even more, dote the LLVM-powered static analyzer. The image below shows how the static analyzer displays its discovery of a workable bug.

    OH HAI I create UR BUGOH HAI I create UR BUG

    Aside from the whimsy of the diminutive arrows (which, admit it, are adorable), the actual bug it's highlighting is something that every programmer can imagine creating (say, through some hasty editing). The static analyzer has determined that there's at least one path through this set of nested conditionals that leaves the myName variable uninitialized, thus making the attempt to forward the mutableCopy message in the final line potentially dangerous.

    I'm certain Apple is going hog-wild running the static analyzer on totality of its applications and the operating system itself. The prospect of an automated passage to discover bugs that may occupy existed for years in the depths of a huge codebase is almost pornographic to developers—platform owners in particular. To the degree that Mac OS X 10.6.0 is more bug-free than the previous 10.x.0 releases, LLVM surely deserves some significant share of the credit.

    Master of the house

    By committing to a Clang/LLVM-powered future, Apple has finally taken complete control of its progress platform. The CodeWarrior suffer apparently convinced Apple that it's unwise to depend on a third party for its platform's progress tools. Though it's taken many years, I believe even the most diehard Metrowerks fan would occupy to coincide that Xcode in Snow Leopard is now a pretty damn capable IDE.

    After years of struggling with the disconnect between the goals of the GCC project and its own compiler needs, Apple has finally gash the apron strings. OK, granted, GCC 4.2 is still the default compiler in Snow Leopard, but this is a transitional phase. Clang is the recommended compiler, and the focus of totality of Apple's future efforts.

    I know what you're thinking. This is swell and all, but how are these compilers helping developers better leverage the expanding swarm of transistors at their disposal? As you'll espy in the following sections, LLVM's scaly, metallic head pops up in a few key places.

    Blocks

    In Snow Leopard, Apple has introduced a C language extension called "blocks." Blocks add closures and anonymous functions to C and the C-derived languages C++, Objective-C, and Objective C++.

    These features occupy been available in dynamic programming languages such as Lisp, Smalltalk, Perl, Python, Ruby, and even the unassuming JavaScript for a long time (decades, in the case of Lisp—a fact gladly offered by its practitioners). While dynamic-language programmers select closures and anonymous functions for granted, those who labor with more traditional, statically compiled languages such as C and its derivatives may find them quite exotic. As for non-programmers, they likely occupy no interest in this topic at all. But I'm going to attempt an explanation nonetheless, as blocks shape the foundation of some other piquant technologies to breathe discussed later.

    Perhaps the simplest passage to interpret blocks is that they beget functions another shape of data. C-derived languages already occupy duty pointers, which can breathe passed around dote data, but these can only point to functions created at compile time. The only passage to influence the conduct of such a duty is by passing different arguments to the duty or by setting global variables which are then accessed from within the function. Both of these approaches occupy tall disadvantages

    Passing arguments becomes cumbersome as their number and complexity grows. Also, it may breathe that you occupy limited control over the arguments that will breathe passed to your function, as is often the case with callbacks. To compensate, you may occupy to bundle up totality of your piquant condition into a context protest of some kind. But when, how, and by whom that context data will breathe disposed of can breathe difficult to pin down. Often, a second callback is required for this. It's totality quite a pain.

    As for the expend of global variables, in addition to being a well-known anti-pattern, it's too not thread-safe. To beget it so requires locks or some other shape of mutual exclusion to avert multiple invocations of the very duty from stepping on each other's toes. And if there's anything worse than navigating a sea of callback-based APIs, it's manually dealing with thread safety issues.

    Blocks bypass totality of these problems by allowing functional blobs of code—blocks—to breathe defined at runtime. It's easiest to understand with an example. I'm going to start by using JavaScript, which has a bit friendlier syntax, but the concepts are the same.

    b = get_number_from_user(); multiplier = function(a) { recrudesce a * b };

    Here I've created a duty named multiplier that takes a sole argument, a, and multiplies it by a second value, b, that's provided by the user at runtime. If the user supplied the number 2, then a summon to multiplier(5) would recrudesce the value 10.

    b = get_number_from_user(); // assume it's 2 multiplier = function(a) { recrudesce a * b }; r = multiplier(5); // 5 * 2 = 10

    Here's the sample above done with blocks in C.

    b = get_number_from_user(); // assume it's 2 multiplier = ^ int (int a) { recrudesce a * b; }; r = multiplier(5); // 5 * 2 = 10

    By comparing the JavaScript code to the C version, I hope you can espy how it works. In the C example, that diminutive caret ^ is the key to the syntax for blocks. It's kindhearted of ugly, but it's very C-like in that it parallels the existing C syntax for duty pointers, with ^ in site of *, as this sample illustrates:

    /* A duty that takes a sole integer dispute and returns a pointer to a duty that takes two integer arguments and returns a floating-point number. */ float (*func2(int a))(int, int); /* A duty that takes a sole integer dispute and returns a obscure that takes two integer arguments and returns a floating-point number. */ float (^func1(int a))(int, int);

    You'll just occupy to dependence me when I divulge you that this syntax actually makes sense to seasoned C programmers.

    Now then, does this beofvalue that C is suddenly a dynamic, high-level language dote JavaScript or Lisp? Hardly. The existing distinction between the stack and the heap, the rules governing automatic and static variables, and so on are totality still in complete effect. Plus, now there's a gross new set of rules for how blocks interact with each of these things. There's even a new __block storage ilk refer to further control the scope and lifetime of values used in blocks.

    All of that said, blocks are still a huge win in C. Thanks to blocks, the friendlier APIs long enjoyed by dynamic languages are now workable in C-derived languages. For example, suppose you want to apply some operation to every line in a file. To consequence so in a low-level language dote C requires some amount of boilerplate code to open and read from the file, handle any errors, read each line into a buffer, and clean up at the end.

    FILE *fp = fopen(filename, "r"); if (fp == NULL) { perror("Unable to open file"); } else { char line[MAX_LINE]; while (fgets(line, MAX_LINE, fp)) { work; work; work; } fclose(fp); }

    The share in bold is an abstract representation of what you're planning to consequence to each line of the file. The ease is the literal boilerplate code. If you find yourself having to apply varying operations to every line of many different files, this boilerplate code gets tedious.

    What you'd dote to breathe able to consequence is factor it out into a duty that you can call. But then you're faced with the problem of how to express the operation you'd dote to achieve on each line of the file. In the middle of each obscure of boilerplate may breathe many lines of code expressing the operation to breathe applied. This code may reference or modify local variables which are affected by the runtime conduct of the program, so traditional duty pointers won't work. What to do?

    Thanks to blocks, you can define a duty that takes a filename and a obscure as arguments. This gets totality the uninteresting code out of your face.

    foreach_line(filename, ^ (char *line) { work; work; work; });

    What's left is a much clearer expression of your intent, with less surrounding noise. The dispute after filename is a literal obscure that takes a line of text as an argument.

    Even when the volume of boilerplate is small, the simplicity and clarity bounty is still worthwhile. regard the simplest workable loop that executes a fixed number of times. In C-based languages, even that basic construct offers a surprising number of opportunities for bugs. Let's do_something() 10 times:

    for (int i = 0; i <= 10; i++) { do_something(); }

    Oops, I've got a diminutive bug there, don't I? It happens to the best of us. But why should this code breathe more complicated than the sentence describing it. consequence something 10 times! I never want to screw that up again. Blocks can help. If they just invest a diminutive application up front to define a helper function:

    typedef void (^work_t)(void); void repeat(int n, work_t block) { for (int i = 0; i < n; ++i) block(); }

    We can transport the bug for good. Now, repeating any whimsical obscure of code a specific number of times is totality but idiot-proof:

    repeat(10, ^{ do_something() }); repeat(20, ^{ do_other_thing() });

    And remember, the obscure dispute to repeat() can accommodate exactly the very kindhearted of code, literally copied and pasted, that would occupy appeared within a traditional for loop.

    All these possibilities and more occupy been well explored by dynamic languages: map, reduce, collect, etc. Welcome, C programmers, to a higher order.

    Apple has taken these lessons to heart, adding over 100 new APIs that expend blocks in Snow Leopard. Many of these APIs would not breathe workable at totality without blocks, and totality of them are more elegant and concise than they would breathe otherwise.

    It's Apple objective to submit blocks as an official extension to one or more of the C-based languages, though it's not yet limpid which standards bodies are receptive to the proposal. For now, blocks are supported by totality four of Apple's compilers in Mac OS X.

    Concurrency in the existent world: a prelude

    The struggle to beget efficient expend of a large number of independent computing devices is not new. For decades, the realm of high-performance computing has tackled this problem. The challenges faced by people writing software for supercomputers many years ago occupy now trickled down to desktop and even mobile computing platforms.

    In the PC industry, some people saw this coming earlier than others. Almost 20 years ago, breathe Inc. was formed around the view of creating a PC platform unconstrained by legacy limitations and entirely prepared for the coming abundance of independent computing units on the desktop. To that end, breathe created the BeBox, a dual-CPU desktop computer, and BeOS, a brand-new operating system.

    The signature entangle phrase for BeOS was "pervasive multithreading." The BeBox and other machines running BeOS leveraged every ounce of the diminutive (by today's standards, anyway) computing resources at their disposal. The demos were impressive. A dual 66 MHz machine (don't beget me present another graph) could play multiple videos simultaneously while too playing several audio tracks from a CD—some backwards— and totality the while, the user interface remained completely responsive.

    Let me divulge you, having lived through this age myself, the suffer was mind-blowing at the time. BeOS created instant converts out of hundreds of technology enthusiasts, many of whom maintain that today's desktop computing suffer still doesn't match the responsiveness of BeOS. This is certainly capable emotionally, if not necessarily literally.

    After nearly purchasing breathe in the late 1990s, Apple bought NeXT instead, and the ease is history. But had Apple gone with arrangement breathe instead, Mac developers might occupy had a rough road ahead. While totality that pervasive multithreading made for impressive technology demos and a distinguished user experience, it could breathe extremely demanding on the programmer. BeOS was totality about threads, going so far as to maintain a sever thread for each window. Whether you liked it or not, your BeOS program was going to breathe multithreaded.

    Parallel programming is notoriously hard, with the manual management of POSIX-style threads representing the abysmal terminate of that pool. The best programmers in the world are hard-pressed to create large multithreaded programs in low-level languages dote C or C++ without finding themselves impaled on the spikes of deadlock, race conditions, and other perils inherent in the expend of in multiple simultaneous threads of execution that share the very remembrance space. Extremely careful application of locking primitives is required to avoid performance-robbing levels of contention for shared data—and the bugs, oh the bugs! The term "Heisenbug" may as well occupy been invented for multithreaded programming.

    Nineteen years after breathe tilted at the windmill of the widening swath of silicon in desktop PCs, the challenge has only grown. Those transistors are out there, man—more than ever before. Single-threaded programs on today's high-end desktop Macs, even when using "100%" CPU, extend but a sole glowing tower in a sea of sixteen otherwise vacant lanes on a CPU monitor window.

    A wide-open unpretentious
 of transistorsA wide-open unpretentious of transistors

    And woe breathe unto the user if that pegged CPU core is running the main thread of a GUI application on Mac OS X. A CPU-saturated main thread means no new user inputs are being pulled off the event queue by the application. A few seconds of that and an ancient friend makes its appearance: the spinning beach ball of death.

    Nooooooooo!!!

    Nooooooooo!!! Image from The Iconfactory

    This is the enemy: hardware with more computing resources than programmers know what to consequence with, most of it completely idle, and totality the while the user is utterly blocked in his attempts to expend the current application. What's Snow Leopard's answer? Read on…

    Grand Central Dispatch Apple's GCD branding: <a href="http://en.wikipedia.org/wiki/Foamer">Railfan</a> <a href="http://en.wikipedia.org/wiki/Fan_service">service</a>Apple's GCD branding: Railfan service

    Snow Leopard's acknowledge to the concurrency conundrum is called imposing Central Dispatch (GCD). As with QuickTime X, the title is extremely apt, though this is not entirely limpid until you understand the technology.

    The first thing to know about GCD is that it's not a new Cocoa framework or similar special-purpose frill off to the side. It's a unpretentious C library baked into the lowest levels of Mac OS X. (It's in libSystem, which incorporates libc and the other code that sits at the very bottom of userspace.)

    There's no necessity to link in a new library to expend GCD in your program. Just #include <dispatch/dispatch.h> and you're off to the races. The fact that GCD is a C library means that it can breathe used from totality of the C-derived languages supported on Mac OS X: Objective-C, C++, and Objective-C++.

    Queues and threads

    GCD is built on a few simple entities. Let's start with queues. A queue in GCD is just what it sounds like. Tasks are enqueued, and then dequeued in FIFO order. (That's "First In, First Out," just dote the checkout line at the supermarket, for those who don't know and don't want to succeed the link.) Dequeuing the chore means handing it off to a thread where it will execute and consequence its actual work.

    Though GCD queues will hand tasks off to threads in FIFO order, several tasks from the very queue may breathe running in parallel at any given time. This animation demonstrates.

    A imposing Central Dispatch queue in action

    You'll notice that chore B completed before chore A. Though dequeuing is FIFO, chore completion is not. too note that even though there were three tasks enqueued, only two threads were used. This is an famous feature of GCD which we'll debate shortly.

    But first, let's notice at the other kindhearted of queue. A serial queue works just dote a customary queue, except that it only executes one chore at a time. That means chore completion in a serial queue is too FIFO. Serial queues can breathe created explicitly, just dote customary queues, but each application too has an implicit "main queue" which is a serial queue that runs on the main thread.

    The animation above shows threads appearing as labor needs to breathe done, and disappearing as they're no longer needed. Where consequence these threads forward from and where consequence they fade when they're done? GCD maintains a global pool of threads which it hands out to queues as they're needed. When a queue has no more pending tasks to speed on a thread, the thread goes back into the pool.

    This is an extremely famous aspect of GCD's design. Perhaps surprisingly, one of the most difficult parts of extracting maximum performance using traditional, manually managed threads is figuring out exactly how many threads to create. Too few, and you risk leaving hardware idle. Too many, and you start to spend a significant amount of time simply shuffling threads in and out of the available processor cores.

    Let's affirm a program has a problem that can breathe split into eight separate, independent units of work. If this program then creates four threads on an eight-core machine, is this an sample of creating too many or too few threads? Trick question! The acknowledge is that it depends on what else is happening on the system.

    If six of the eight cores are totally saturated doing some other work, then creating four threads will just require the OS to squander time rotating those four threads through the two available cores. But wait, what if the process that was saturating those six cores finishes? Now there are eight available cores but only four threads, leaving half the cores idle.

    With the exception of programs that can reasonably await to occupy the entire machine to themselves when they run, there's no passage for a programmer to know ahead of time exactly how many threads he should create. Of the available cores on a particular machine, how many are in use? If more become available, how will my program know?

    The bottom line is that the optimal number of threads to allot in flight at any given time is best determined by a single, globally aware entity. In Snow Leopard, that entity is GCD. It will support zero threads in its pool if there are no queues that occupy tasks to run. As tasks are dequeued, GCD will create and dole out threads in a passage that optimizes the expend of the available hardware. GCD knows how many cores the system has, and it knows how many threads are currently executing tasks. When a queue no longer needs a thread, it's returned to the pool where GCD can hand it out to another queue that has a chore ready to breathe dequeued.

    There are further optimizations inherent in this scheme. In Mac OS X, threads are relatively heavyweight. Each thread maintains its own set of register values, stack pointer, and program counter, plus kernel data structures tracking its security credentials, scheduling priority, set of pending signals and signal masks, etc. It totality adds up to over 512 KB of overhead per thread. Create a thousand threads and you've just burned about a half a gigabyte of remembrance and kernel resources on overhead alone, before even considering the actual data within each thread.

    Compare a thread's 512 KB of baggage with GCD queues which occupy a mere 256 bytes of overhead. Queues are very lightweight, and developers are encouraged to create as many of them as they need—thousands, even. In the earlier animation, when the queue was given two threads to process its three tasks, it executed two tasks on one of the threads. Not only are threads heavyweight in terms of remembrance overhead, they're too relatively costly to create. Creating a new thread for each chore would breathe the worst workable scenario. Every time GCD can expend a thread to execute more than one task, it's a win for overall system efficiency.

    Remember the problem of the programmer trying to figure out how many threads to create? Using GCD, he doesn't occupy to worry about that at all. Instead, he can concentrate entirely on the optimal concurrency of his algorithm in the abstract. If the best-case scenario for his problem would expend 500 concurrent tasks, then he can fade ahead and create 500 GCD queues and deal his labor among them. GCD will figure out how many actual threads to create to consequence the work. Furthermore it will adjust the number of threads dynamically as the conditions on the system change.

    But perhaps most importantly, as new hardware is released with more and more CPU cores, the programmer does not necessity to change his application at all. Thanks to GCD, it will transparently select handicap of any and totality available computing resources, up to—but not past!—the optimal amount of concurrency as originally defined by the programmer when he chose how many queues to create.

    But wait, there's more! GCD queues can actually breathe arranged in arbitrarily knotty directed acyclic graphs. (Actually, they can breathe cyclic too, but then the conduct is undefined. Don't consequence that.) Queue hierarchies can breathe used to funnel tasks from disparate subsystems into a narrower set of centrally controlled queues, or to force a set of customary queues to delegate to a serial queue, effectively serializing them totality indirectly.

    There are too several levels of priority for queues, dictating how often and with what urgency threads are distributed to them from the pool. Queues can breathe suspended, resumed, and cancelled. Queues can too breathe grouped, allowing totality tasks distributed to the group to breathe tracked and accounted for as a unit.

    Overall, GCD's expend of queues and threads forms a simple, elegant, but too extremely pragmatic architecture.

    Asynchronicity

    Okay, so GCD is a distinguished passage to beget efficient expend of the available hardware. But is it really any better than BeOS's approach to multithreading? We've already seen a few ways that GCD avoids the pitfalls of BeOS (e.g., the reuse of threads and the maintenance of a global pool of threads that's correctly sized for the available hardware). But what about the problem of overwhelming the programmer by requiring threads in places where they complicate, rather than enhance the application?

    GCD embodies a philosophy that is at the contrary terminate of the spectrum from BeOS's "pervasive multithreading" design. Rather than achieving responsiveness by getting every workable component of an application running concurrently on its own thread (and paying a ponderous charge in terms of knotty data sharing and locking concerns), GCD encourages a much more limited, hierarchical approach: a main application thread where totality the user events are processed and the interface is updated, and worker threads doing specific jobs as needed.

    In other words, GCD doesn't require developers to believe about how best to split the labor of their application into multiple concurrent threads (though when they're ready to consequence that, GCD will breathe willing and able to help). At its most basic level, GCD aims to embolden developers to roam from thinking synchronously to thinking asynchronous. Something dote this: "Write your application as usual, but if there's any share of its operation that can reasonably breathe expected to select more than a few seconds to complete, then for the dote of Zarzycki, derive it off the main thread!"

    That's it; no more, no less. Beach ball banishment is the cornerstone of user interface responsiveness. In some respects, everything else is gravy. But most developers know this intuitively, so why consequence they still espy the beach ball in Mac OS X applications? Why don't totality applications already execute totality of their potentially long-running tasks on background threads?

    A few reasons occupy been mentioned already (e.g., the difficulty of knowing how many threads to create) but the tall one is much more pragmatic. Spinning off a thread and collecting its result has always been a bit of a pain. It's not so much that it's technically difficult, it's just that it's such an specific rupture from coding the actual labor of your application to coding totality this task-management plumbing. And so, especially in borderline cases, dote an operation that may select 3 to 5 seconds, developers just consequence it synchronously and roam onto the next thing.

    Unfortunately, there's a surprising number of very common things that an application can consequence that execute quickly most of the time, but occupy the potential to select much longer than a few seconds when something goes wrong. Anything that touches the file system may stall at the lowest levels of the OS (e.g., within blocking read() and write() calls) and breathe topic to a very long (or at least an "unexamined-by-the-application-developer") timeout. The very goes for title lookups (e.g., DNS or LDAP), which almost always execute instantly, but entangle many applications completely off-guard when they start taking their sweet time to recrudesce a result. Thus, even the most meticulously constructed Mac OS X applications can terminate up throwing the beach ball in their visage from time to time.

    With GCD, Apple is saw it doesn't occupy to breathe this way. For example, suppose a document-based application has a button that, when clicked, will resolve the current document and display some piquant statistics about it. In the common case, this analysis should execute in under a second, so the following code is used to connect the button with an action:

    - (IBAction)analyzeDocument:(NSButton *)sender { NSDictionary *stats = [myDoc analyze]; [myModel setDict:stats]; [myStatsView setNeedsDisplay:YES]; [stats release]; }

    The first line of the duty carcass analyzes the document, the second line updates the application's internal state, and the third line tells the application that the statistics view needs to breathe updated to reflect this new state. It totality follows a very common pattern, and it works distinguished as long as notathing of these steps—which are totality running on the main thread, remember—takes too long. Because after the user presses the button, the main thread of the application needs to handle that user input as snappily as workable so it can derive back to the main event loop to process the next user action.

    The code above works distinguished until a user opens a very large or very knotty document. Suddenly, the "analyze" step doesn't select one or two seconds, but 15 or 30 seconds instead. Hello, beach ball. And still, the developer is likely to hem and haw: "This is really an exceptional situation. Most of my users will never open such a large file. And anyway, I really don't want to start reading documentation about threads and adding totality that extra code to this simple, four-line function. The plumbing would dwarf the code that does the actual work!"

    Well, what if I told you that you could roam the document analysis to the background by adding just two lines of code (okay, and two lines of closing braces), totality located within the existing function? No application-global objects, no thread management, no callbacks, no dispute marshalling, no context objects, not even any additional variables. Behold, imposing Central Dispatch:

    - (IBAction)analyzeDocument:(NSButton *)sender { dispatch_async(dispatch_get_global_queue(0, 0), ^{ NSDictionary *stats = [myDoc analyze]; dispatch_async(dispatch_get_main_queue(), ^{ [myModel setDict:stats]; [myStatsView setNeedsDisplay:YES]; [stats release]; }); }); }

    There's a hell of a lot of packed into those two lines of code. totality of the functions in GCD originate with dispatch_, and you can espy four such calls in the blue lines of code above. The key to the minimal invasiveness of this code is revealed in the second dispute to the two dispatch_async() calls. Thus far, I've been discussing "units of work" without specifying how, exactly, GCD models such a thing. The answer, now revealed, should appear obvious in retrospect: blocks! The faculty of blocks to capture the surrounding context is what allows these GCD calls to breathe dropped birthright into some existing code without requiring any additional setup or re-factoring or other contortions in service of the API.

    But the best share of this code is how it deals with the problem of detecting when the background chore completes and then showing the result. In the synchronous code, the resolve fashion summon and the code to update the application display simply materialize in the desired sequence within the function. In the asynchronous code, miraculously, this is still the case. Here's how it works.

    The outer dispatch_async() summon puts a chore on a global concurrent GCD queue. That task, represented by the obscure passed as the second argument, contains the potentially time-consuming resolve fashion call, plus another summon to dispatch_async() that puts a chore onto the main queue—a serial queue that runs on the main thread, remember—to update the application's user interface.

    User interface updates must totality breathe done from the main thread in a Cocoa application, so the code in the inner obscure could not breathe executed anywhere else. But rather than having the background thread forward some kindhearted of special-purpose notification back to the main thread when the resolve fashion summon completes (and then adding some code to the application to detect and handle this notification), the labor that needs to breathe done on the main thread to update the display is encapsulated in yet another obscure within the larger one. When the resolve summon is done, the inner obscure is allot onto the main queue where it will (eventually) speed on the main thread and consequence its labor of updating the display.

    Simple, elegant, and effective. And for developers, no more excuses.

    Believe it or not, it's just as effortless to select a serial implementation of a train of independent operations and parallelize it. The code below does labor on count elements of data, one after the other, and then summarizes the results once totality the elements occupy been processed.

    for (i = 0; i < count; i++) { results[i] = do_work(data, i); } total = summarize(results, count);

    Now here's the parallel version which puts a sever chore for each component onto a global concurrent queue. (Again, it's up to GCD to settle how many threads to actually expend to execute the tasks.)

    dispatch_apply(count, dispatch_get_global_queue(0, 0), ^(size_t i) { results[i] = do_work(data, i); }); total = summarize(results, count);

    And there you occupy it: a for loop replaced with a concurrency-enabled equivalent with one line of code. No preparation, no additional variables, no impossible decisions about the optimal number of threads, no extra labor required to wait for totality the independent tests to complete. (The dispatch_apply() summon will not recrudesce until totality the tasks it has dispatched occupy completed.) Stunning.

    Grand Central Awesome

    Of totality the APIs added in Snow Leopard, imposing Central Dispatch has the most far-reaching implications for the future of Mac OS X. Never before has it been so effortless to consequence labor asynchronously and to spread workloads across many CPUs.

    When I first heard about imposing Central Dispatch, I was extremely skeptical. The greatest minds in computer science occupy been working for decades on the problem of how best to extract parallelism from computing workloads. Now here was Apple apparently promising to solve this problem. Ridiculous.

    But imposing Central Dispatch doesn't actually address this issue at all. It offers no waiton whatsoever in deciding how to split your labor up into independently executable tasks—that is, deciding what pieces can or should breathe executed asynchronously or in parallel. That's still entirely up to the developer (and still a tough problem). What GCD does instead is much more pragmatic. Once a developer has identified something that can breathe split off into a sever task, GCD makes it as effortless and non-invasive as workable to actually consequence so.

    The expend of FIFO queues, and especially the existence of serialized queues, seems counter to the spirit of ubiquitous concurrency. But we've seen where the Platonic ideal of multithreading leads, and it's not a pleasant site for developers.

    One of Apple's slogans for imposing Central Dispatch is "islands of serialization in a sea of concurrency." That does a distinguished job of capturing the practical reality of adding more concurrency to run-of-the-mill desktop applications. Those islands are what seclude developers from the thorny problems of simultaneous data access, deadlock, and other pitfalls of multithreading. Developers are encouraged to identify functions of their applications that would breathe better executed off the main thread, even if they're made up of several sequential or otherwise partially interdependent tasks. GCD makes it effortless to rupture off the entire unit of labor while maintaining the existing order and dependencies between subtasks.

    Those with some multithreaded programming suffer may breathe unimpressed with the GCD. So Apple made a thread pool. tall deal. They've been around forever. But the angels are in the details. Yes, the implementation of queues and threads has an elegant simplicity, and baking it into the lowest levels of the OS really helps to lower the perceived barrier to entry, but it's the API built around blocks that makes imposing Central Dispatch so attractive to developers. Just as Time Machine was "the first backup system people will actually use," imposing Central Dispatch is poised to finally spread the heretofore sunless craft of asynchronous application design to totality Mac OS X developers. I can't wait.

    OpenCL Somehow, OpenCL got in on the <a href="http://arstechnica.com/apple/2007/10/mac-os-x-10-5/8/#core-spheres">"core" branding</a>Somehow, OpenCL got in on the "core" branding

    So far, we've seen a few examples of doing more with more: a new, more modern compiler infrastructure that supports an famous new language feature, and a powerful, pragmatic concurrency API built on top of the new compilers' champion for said language feature. totality this goes a long passage towards helping developers and the OS itself beget maximum expend of the available hardware.

    But CPUs are not the only components experiencing a glut of transistors. When it comes to the proliferation of independent computation engines, another piece of silicon inside every Mac is the undisputed title holder: the GPU.

    The numbers divulge the tale. While Mac CPUs accommodate up to four cores (which may present up as eight rational cores thanks to symmetric multithreading), high-end GPUs accommodate well over 200 processor cores. While CPUs are just now edging over 100 GFLOPS, the best GPUs are capable of over 1,000 GFLOPS. That's one trillion floating-point operations per second. And dote CPUs, GPUs now forward more than one on a board.

    Writing for the GPU

    Unfortunately, the cores on a GPU are not general-purpose processors (at least not yet). They're much simpler computing engines that occupy evolved from the fixed-function silicon of their ancestors that could not breathe programmed directly at all. They don't champion the loaded set of instructions available on CPUs, the maximum size of the programs that will speed is often limited and very small, and not totality of the features of the industry-standard IEEE floating-point computation specification are supported.

    Today's GPUs can breathe programmed, but the most common forms of programmability are still firmly planted in the world of graphics programming: vertex shaders, geometry shaders, pixel shaders. Most of the languages used to program GPUs are similarly graphically focused: HLSL, GLSL, Cg.

    Nevertheless, there are computational tasks outside the realm of graphics that are a capable meet for GPU hardware. It would breathe nice if there were a non-graphics-oriented language to write them in. Creating such a thing is quite a challenge, however. GPU hardware varies wildly in every imaginable way: number and ilk of execution units, available data formats, instruction sets, remembrance architecture, you title it. Programmers don't want to breathe exposed to these differences, but it's difficult to labor around the complete want of a feature or the unavailability of a particular data type.

    GPU vendor NVIDIA gave it a shot, however, and produced CUDA: a subset of the C language with extensions for vector data types, data storage specifiers that reflect typical GPU remembrance hierarchy, and several bundled computational libraries. CUDA is but one entrant in the burgeoning GPGPU realm (General-Purpose computing on Graphics Processing Units). But coming from a GPU vendor, it faces an uphill battle with developers who really want a vendor-agnostic solution.

    In the world of 3D programming, OpenGL fills that role. As you've surely guessed by now, OpenCL aims to consequence the very for general-purpose computation. In fact, OpenCL is supported by the very consortium as OpenGL: the ominously named Khronos Group. But beget no mistake, OpenCL is Apple's baby.

    Apple understood that OpenCL's best casual of success was to become an industry standard, not just an Apple technology. To beget that happen, Apple needed the cooperation of the top GPU vendors, plus an agreement with an established, widely-recognized standards body. It took a while, but now it's totality forward together.

    OpenCL is a lot dote CUDA. It uses a C-like language with the vector extensions, it has a similar model of remembrance hierarchy, and so on. This is no surprise, considering how closely Apple worked with NVIDIA during the progress of OpenCL. There's too no passage any of the tall GPU vendors would radically alter their hardware to champion an as-yet-unproven standard, so OpenCL had to labor well with GPUs already designed to champion CUDA, GLSL, and other existing GPU programming languages.

    The OpenCL difference

    This is totality well and good, but to occupy any impact on the day-to-day life of Mac users, developers actually occupy to expend OpenCL in their applications. Historically, GPGPU programming languages occupy not seen much expend in traditional desktop applications. There are several reasons for this.

    Early on, writing programs for the GPU often required the expend of vendor-specific assembly languages that were far removed from the suffer of writing a typical desktop application using a contemporary GUI API. The more C-like languages that came later remained either graphics-focused, vendor-specific, or both. Unless running code on the GPU would accelerate a core component of an application by an order of magnitude, most developers still could not breathe bothered to navigate this strange world.

    And even if the GPU did give a huge speed boost, relying on graphics hardware for general-purpose computation was very likely to narrow the potential audience for an application. Many older GPUs, especially those create in laptops, cannot speed languages dote CUDA at all.

    Apple's key decision in the design of OpenCL was to allow OpenCL programs to speed not just on GPUs, but on CPUs as well. An OpenCL program can query the hardware it's running on and enumerate totality eligible OpenCL devices, categorized as CPUs, GPUs, or dedicated OpenCL accelerators (the IBM Cell Blade server—yes, that Cell—is apparently one such device). The program can then dispatch its OpenCL tasks to any available device. It's too workable to create a sole rational device consisting of any combination of eligible computing resources: two GPUs, a GPU and two CPUs, etc.

    The advantages of being able to speed OpenCL programs on both CPUs and GPUs are obvious. Every Mac running Snow Leopard, not just those with the recent-model GPUs, can speed a program that contains OpenCL code. But there's more to it than that.

    Certain kinds of algorithms actually speed faster on high-end multi-core CPUs than on even the very fastest available GPUs. At WWDC 2009, an engineer from Electronic Arts demonstrated an OpenCL port of a skinning engine from one of its games running over four times faster on a four-core Mac Pro than on an NVIDIA GeForce GTX285. Restructuring the algorithm and making many other changes to better suit the limitations (and strengths) of the GPU pushed it back ahead of the CPU by a wide margin, but sometimes you just want the system you occupy to speed well as-is. Being able to target the CPU is extremely useful in those cases.

    Moreover, writing vector code for Intel CPUs "the old-fashioned way" can breathe a existent pain. There's MMX, SSE, SSE2, SSE3, and SSE4 to deal with, totality with slightly different capabilities, and totality of which force the programmer to write code dote this:

    r1 = _mm_mul_ps(m1, _mm_add_ps(x1, x2));

    OpenCL's endemic champion for vector types de-clutters the code considerably:

    r1 = m1 * (x1 + x2);

    Similarly, OpenCL's champion for implicit parallelism makes it much easier to select handicap of multiple CPU cores. Rather than writing totality the logic to split your data into pieces and deal those pieces to the parallel-computing hardware, OpenCL lets you write just the code to operate on a sole piece of the data and then forward it, along with the entire obscure of data and the desired even of parallelism, to the computing device.

    This arrangement is taken for granted in traditional graphics programming, where code implicitly works on totality pixels in a texture or totality vertices in a polygon; the programmer only needs to write code that will exist in the "inner loop," so to speak. An API with champion for this kindhearted of parallelism that runs on CPUs as well as GPUs fills an famous gap.

    Writing to OpenCL too future-proofs task- or data-parallel code. Just as the very OpenGL code will derive faster and faster as newer, more powerful GPUs are released, so too will OpenCL code achieve better as CPUs and GPUs derive faster. The extra layer of abstraction that OpenCL provides makes this possible. For example, though vector code written several years ago using MMX got faster as CPU clock speeds increased, a more significant performance boost likely requires porting the code to one of the newer SSE instruction sets.

    As newer, more powerful vector instruction sets and parallel hardware becomes available, Apple will update its OpenCL implementations to select handicap of them, just as video card makers and OS vendors update their OpenGL drivers to select handicap of faster GPUs. Meanwhile, the application developer's code remains unchanged. Not even a recompile is required.

    Here breathe dragons (and trains)

    How, you may wonder, can the very compiled code terminate up executing using SSE2 on one machine and SSE4 on another, or on an NVIDIA GPU on one machine and an ATI GPU on another? To consequence so would require translating the device-independent OpenCL code to the instruction set of the target computing device at runtime. When running on a GPU, OpenCL must too ship the data and the newly translated code over to the video card and collect the results at the end. When running on the CPU, OpenCL must organize for the requested even of parallelism by creating and distributing threads appropriately to the available cores.

    Well, wouldn't you know it? Apple just happens to occupy two technologies that solve these exact problems.

    Want to compile code "just in time" and ship it off to a computing device? That's what LLVM was born to do—and, indeed, what Apple did with it in Leopard, albeit on a more limited scale. OpenCL is a natural extension of that work. LLVM allows Apple to write a sole code generator for each target instruction set, and concentrate totality of its application on a sole device-independent code optimizer. There's no longer any necessity to duplicate these tasks, using one compiler to create the static application executable and having to jury-rig another for just-in-time compilation.

    (Oh, and by the way, bethink Core Image? That's another API that needs to compile code just-in-time and ship it off to execute on parallel hardware dote GPUs and multi-core CPUs. In Snow Leopard, Core Image has been re-implemented using OpenCL, producing a hefty 25% overall performance boost.)

    To handle chore parallelism and provision threads, OpenCL is built on top of imposing Central Dispatch. This is such a natural meet that it's a bit surprising that the OpenCL API doesn't expend blocks. I believe Apple decided that it shouldn't press its luck when it comes to getting its home-grown technologies adopted by other vendors. This decision already seems to breathe paying off, as AMD has its own OpenCL implementation under way.

    The top of the pyramid

    Though the underlying technologies, Clang, blocks and imposing Central Dispatch, will undoubtedly breathe more widely used by developers, OpenCL represents the culmination of that particular technological thread in Snow Leopard. This is the gold measure of software engineering: creating a new public API by edifice it on top of lower-level, but equally well-designed and implemented public APIs.

    A unified abstraction for the ever-growing heterogeneous collection of parallel computing silicon in desktop computers was sorely needed. We've got an increasing population of powerful CPU cores, but they still exist in numbers that are orders of magnitude lower than the hundreds of processing units in modern GPUs. On the other hand, GPUs still occupy a ways to fade to entangle up with the power and flexibility of a full-fledged CPU core. But even with totality the differences, writing code exclusively for either one of those worlds still smacks of leaving money on the table.

    With OpenCL in hand, there's no longer a necessity to allot totality your eggs in one silicon basket. And with the advent of hybrid CPU/GPU efforts dote Intel's Larabee, which expend CPU-caliber processing engines, but in much higher numbers, OpenCL may prove even more famous in the coming years.

    Transistor harvest

    Collectively, the concurrency-enabling features introduced in Snow Leopard limn the biggest boost to asynchronous and parallel software progress in any Mac OS X release—perhaps in any desktop operating system release ever. It may breathe arduous for end-users to derive excited about "plumbing" technologies dote imposing Central Dispatch and OpenCL, let lonely compilers and programming language features, but it's upon these foundations that developers will create ever-more-impressive edifices of software. And if those applications tower over their synchronous, serial predecessors, it will breathe because they stand on the shoulders of giants.

    QuickTime Player's new icon (Not a fan)QuickTime Player's new icon (Not a fan) QuickTime Player

    There's been some confusion surrounding QuickTime in Snow Leopard. The earlier section about QuickTime X explains what you necessity to know about the present and future of QuickTime as a technology and an API. But a few of Apple's decisions—and the extremely overloaded significance of the word "QuickTime" in the minds of consumers—have blurred the picture somewhat.

    The first head-scratcher occurs during installation. If you betide to click on the "Customize…" button during installation, you'll espy the following options:

    QuickTime 7 is an optional install?QuickTime 7 is an optional install?

    We've already talked about Rosetta being an optional install, but QuickTime 7 too? Isn't QuickTime severely crippled without QuickTime 7? Why in the world would that breathe an optional install?

    Well, there's no necessity to panic. That particular in the installer should actually read "QuickTime Player 7." QuickTime 7, the ancient but extremely capable media framework discussed earlier, is installed by default in Snow Leopard—in fact, it's mandatory. But the player application, the one with the ancient blue "Q" icon, the one that many casual users actually believe of as being "QuickTime," that's been replaced with a new QuickTime-X-savvy version sporting a pudgy new icon (see above right).

    The new player application is a tall departure from the old. Obviously, it leverages QuickTime X for more efficient video playback, but the user interface is too completely new. Gone are the gray margin and bottom-mounted playback controls from the ancient QuickTime Player, replaced by a frameless window with a black title bar and a floating, moveable set of controls.

    The new QuickTime Player: boldly going where <a href="http://code.google.com/p/niceplayer/">NicePlayer</a> has gone before Enlarge / The new QuickTime Player: boldly going where NicePlayer has gone before

    It's dote a combination of the window treatment of the excellent NicePlayer application and the full-screen playback controls from the ancient QuickTime Player. I'm a bit bothered by two things. First, the ever-so-slightly clipped corners appear dote a tainted idea. Am I just supposititious to give up those dozen-or-so pixels? NicePlayer does it right, showing crisp, square corners.

    Second, the floating playback controls obscure the movie. What if I'm scrubbing around looking for something in that share of the frame? Yes, you can roam the controls, but what if I'm looking for something in an unknown location in the frame? Also, the title bar obscures an entire swath of the top of the frame, and this can't breathe moved. I prize the compactness of this approach, but it'd breathe nice if the title bar overlap could breathe disabled and the controls could breathe dragged off the movie entirely and docked to the bottom or something.

    (One blessing for people who share my OCD tendencies: if you roam the floating controls, they don't bethink their position the next time you open a movie. Why is that a blessing? Because if it worked the other way, we'd totality spend passage too much time fretting about their inability to restore the controller to its default, precisely centered position. Sad, but true.)

    The new QuickTime Player presents a decidedly iMovie-like (or is it iPhone-like, nowadays?) interface for trimming video. Still-frame thumbnails are placed side-by-side to shape a timeline, with adjustable stops at each terminate for trimming.

    Trimming in the new QuickTime Player Enlarge / Trimming in the new QuickTime Player

    Holding down the option key changes from a thumbnail timeline to an audio waveform display:

    Trimming with audio waveform view Enlarge / Trimming with audio waveform view

    In both the video and audio cases, I occupy to wonder exactly how useful the fancy timeline appearances are. The audio waveform is quite small and compressed, and the limited horizontal space of the in-window display means a movie can only present a handful of video frames in its timeline. Also, if there's any faculty to consequence fine adjustments using something other than extremely careful mouse movements (which are necessarily topic to a limited resolution) then I couldn't find it. Final gash Pro this is not.

    QuickTime Player has scholarly another new trick: screen recording. The controls are limited, so more demanding users will still occupy a necessity for a full-featured screen recorder, but QuickTime Player gets the job done.

    Screen recording in QuickTime PlayerScreen recording in QuickTime Player

    There's too an audio-only option, with a similarly simplified collection of settings.

    Audio recordingAudio recording

    Finally, the new QuickTime Player has the faculty to upload a movie directly to YouTube and MobileMe, forward one via e-mail, or add it to your iTunes library. The export options are too vastly simplified, with preset options for iPhone/iPod, Apple TV, and HD 480p and 720p.

    Unfortunately, the list of things you can't consequence with the new QuickTime Player is quite long. You can't cut, copy, and paste whimsical portions of a movie (trimming only affects the ends); you can't extract or delete individual tracks or overlay one track onto another (optionally scaling to fit); you can't export a movie by choosing from the complete set of available QuickTime audio and video codecs. totality of these things were workable with the ancient QuickTime Player—if, that is, you paid the $30 for a QuickTime Pro license. In the past, I've described this extra fee as "criminally stupid", but the features it enabled in QuickTime Player were really useful.

    It's tempting to refer their absence in the new QuickTime Player to the previously discussed limitations of QuickTime X. But the new QuickTime Player is built on top of QTKit, which serves as a front-end for both QuickTime X and QuickTime 7. And it does, after all, feature some limited editing features dote trimming, plus some previously "Pro"-only features dote full-screen playback. Also, the new QuickTime Player can indeed play movies using third-party plug-ins—a feature clearly powered by QuickTime 7.

    Well, Snow Leopard has an extremely pleasant dumbfound waiting for you if you install the optional QuickTime Player 7. When I did so, what I got was the ancient QuickTime Player—somewhat insultingly installed in the "Utilities" folder—with totality of its "Pro" features permanently unlocked. Yes, the tyranny of QuickTime Pro seems to breathe at an end…

    QuickTime Pro: now free for everyone?QuickTime Pro: now free for everyone?

    …but perhaps the key word above is "seems," because QuickTime Player 7 does not occupy totality "pro" features unlocked for everyone. I installed Snow Leopard onto an vacant disk, and QuickTime 7 was not automatically installed (as it is when the installer detects an existing QuickTime Pro license on the target disk). After booting from my fresh Snow Leopard volume, I manually installed the "QuickTime 7" optional component using the Snow Leopard installer disk.

    The result for me was a QuickTime Player 7 application with totality pro features unlocked and with no visible QuickTime Pro registration information. I did, however, occupy a QuickTime Pro license on one of the attached drives. Apparently, the installer detected this and gave me an unlocked QuickTime Player 7 application, even though the boot volume never had a QuickTime Pro license on it.

    The Dock

    The new appearance of some aspects of the Dock are accompanied by some new functionality as well. Clicking and holding on a running application's Dock icon now triggers Expos�, but only for the windows belonging to that application. Dragging a file onto a docked application icon and holding it there for a bit produces the very result. You can then continue that very drag onto one of the Exposé window thumbnails and hover there a bit to bring that window to the front and drop the file into it. It's a pretty handy technique, once you derive in the rehearse of doing it.

    The Exposé display itself is too changed. Now, minimized windows are displayed in smaller shape on the bottom of the screen below a thin line.

    Dock Exposé with new placement of minimized windows Enlarge / Dock Exposé with new placement of minimized windows

    In the screenshot above, you'll notice that notathing of the minimized windows materialize in my Dock. That's thanks to another welcome addition: the faculty to minimize windows "into" the application icon. You'll find the setting for this in the Dock's preference pane.

    New Dock preference: Minimize windows into application iconNew Dock preference: Minimize windows into application icon Minimized windows in a Dock application menuMinimized window denoted by a diamond

    Once set, minimized windows will slip behind the icon of their parent application and then disappear. To derive them back, either right-click the application icon (see right) or trigger Exposé.

    The Dock's grid view for folders now incorporates a scroll bar when there are too many items to meet comfortably. Clicking on a folder icon in the grid now shows that folder's contents within the grid, allowing you to navigate down several folders to find a buried item. A small "back" navigation button appears once you descend.

    These are totality useful new behaviors, and quite a bounty considering the supposititious "no new features" stance of Snow Leopard. But the fundamental nature of the Dock remains the same. Users who want a more elastic or more powerful application launcher/folder organizer/window minimization system must still either sacrifice some functionality (e.g., Dock icon badges and bounce notifications) or continue to expend the Dock in addition to a third-party application.

    The option to support minimized windows from cluttering up the Dock was long overdue. But my enthusiasm is tempered by my frustration at the continued inability to click on a docked folder and occupy it open in the Finder, while too retaining the faculty to drag items into that folder. This was the default conduct for docked folders for the first six years of Mac OS X's life, but it changed in Leopard. Snow Leopard does not ameliorate matters.

    Docking an alias to a folder provides the single-click-open behavior, but items cannot breathe dragged into a docked folder alias for some inexplicable reason. (Radar 5775786, closed in March 2008 with the terse explanation, "not currently supported.") Worse, dragging an particular to a docked folder alias looks dote it will labor (the icon highlights) but upon release, the dragged particular simply springs back to its original location. I really hoped this one would derive fixed in Snow Leopard. No such luck.

    Dock grid view's in-place navigation with back buttonDock grid view's in-place navigation with back button The Finder

    One of the earliest leaked screenshots of Snow Leopard included an innocuous-looking "Get Info…" window for the Finder, presumably to present that its version number had been updated to 10.6. The more piquant tidbit of information it revealed was that the Finder in Snow Leopard was a 64-bit application.

    The Mac OS X Finder started its life as the designated "dog food" application for the Carbon backward-compatibility API for Mac OS X. Over the years, the Finder has been a frequent target of dissatisfaction and scorn. Those tainted feelings frequently spilled over into the parallel debate over API supremacy: Carbon vs. Cocoa.

    "The Finder sucks because it's a Carbon app. What they necessity is a Cocoa Finder! Surely that will solve totality their woes." Well, Snow Leopard features a 64-bit Finder, and as they totality know, Carbon was not ported to 64-bit. Et voila! A Cocoa Finder in Snow Leopard. (More on the woes in a bit.)

    The conversion to Cocoa followed the Snow Leopard formula: no new features… except for maybe one or two. And so, the "new" Cocoa Finder looks and works almost exactly dote the ancient Carbon Finder. The biggest indicator of its "Cocoa-ness" is the extensive expend of Core Animation transitions. For example, when a Finder window does its schizophrenic transformation from a sidebar-bedecked browser window to its minimally-adorned form, it no longer happens in a blink. Instead, the sidebar slides away and fades, the toolbar shrinks, and everything tucks in to shape its new shape.

    Despite crossing the line in a few cases, the Core Animation transitions consequence beget the application feel more polished, and yes, "more Cocoa." And presumably the expend of Cocoa made it so darn effortless to add features that the developers just couldn't resist throwing in a few.

    The number-one feature request from ponderous column-view users has finally been implemented: sortable columns. The sort order applies to totality columns at once, which isn't as nice as per-column sorting, but it's much better than nothing at all. The sort order can breathe set using a menu command (each of which has a keyboard shortcut) or by right-clicking in an unoccupied district of a column and selecting from the resulting context menu.

    Column view sorting context menu Enlarge / Column view sorting context menu Column view sorting menu Enlarge / Column view sorting menu

    Even the lowly icon view has been enhanced in Snow Leopard. Every icon-view window now includes a small slider to control the size of the icons.

    The Finder's icon view with its new slider controlThe Finder's icon view with its new slider control

    This may appear a bit odd—how often consequence people change icon sizes?—but it makes much more sense in the context of previewing images in the Finder. This expend case is made even more material by the recent expansion of the maximum icon size to 512x512 pixels.

    The icon previews themselves occupy been enhanced to better match the abilities available in Quick Look. allot it totality together and you can smoothly zoom a small PDF icon, for example, into the impressively high-fidelity preview shown below, complete with the faculty to spin pages. One press of the space bar and you'll progress to the even larger and more elastic Quick notice view. It's a pretty smooth experience.

    Not your father's icon: 512x512 pixels of multi-page PDF previewingNot your father's icon: 512x512 pixels of multi-page PDF previewing

    QuickTime previews occupy been similarly enhanced. As you zoom in on the icon, it transforms into a miniature movie player, adorned with an odd circular progress indicator. Assuming users are willing to wrangle with the vagaries of the Finder's view settings successfully enough to derive icon view to stick for the windows where it's most useful, I believe that odd diminutive slider is actually going to derive a lot of use.

    The Finder's QuickTime preview. (The "glare" overlay is a bit much.)The Finder's QuickTime preview. (The "glare" overlay is a bit much.)

    List view too has a few enhancements—accidental, incidental, or otherwise. The drag district for each list view particular now spans the entire line. In Leopard, though the entire line was highlighted, only the file title or icon portion could breathe dragged. Trying to drag anywhere else just extended the selection to other items in the list view as the cursor was moved. I'm not certain whether this change in conduct is intentional or if it's just an unexamined consequence of the underlying control used for list view in the new Cocoa Finder. Either way, thumbs up.

    Double-clicking on the dividing line between two column headers in list view will "right-size" that column. For most columns, this means expanding or shrinking to minimally meet the widest value in the column. Date headers will progressively shrink to present less verbose date formats. Supposedly, this worked intermittently in Leopard as well. But whether Cocoa is bringing this feature for the first time or is just making it labor correctly for the first time, it's a change for the better.

    Searching using the Finder's browser view is greatly improved by the implementation of one of those diminutive things that many users occupy been clamoring for year after year. There's now a preference to select the default scope of the search realm in the Finder window toolbar. Can I derive an amen?

    Default Finder search location: configurable at last.Default Finder search location: configurable at last.

    Along similar lines, there are other long-desired enhancements that will fade a long passage towards making the desktop environment feel more solid. A capable sample is the improved handling of the dreaded "cannot eject, disk in use" error. The obvious follow-up question from the user is, "Okay, so what's using it?" Snow Leopard finally provides that information.

    No more guessingNo more guessing

    (Yes, Mac OS X will spurn to oust a disk if your current working directory in a command-line shell is on that disk. kindhearted of cool, but too kindhearted of annoying.)

    Another workable user response to a disk-in-use error is, "I don't care. I'm in a hurry. Just oust it!" That's an option now as well.

    Forcible ejection in progressForcible ejection in progress

    Hm, but why did I derive information about the offending application in one dialog, an option to force ejection in the other, but neither one presented both choices? It's a mystery to me, but presumably it's related to exactly what information the Finder has about the contention for the disk. (As always, the lsof command is available if you want to figure it out the old-fashioned way.)

    Ummm…Ummm…

    So does the new Cocoa Finder finally transport totality of those embarrassing bugs from the bad-old days of Carbon? Not quite. This is essentially the "1.0" release of the Cocoa Finder, and it has its share of 1.0 bugs. Here's one discovered by Glen Aspeslagh (see image right).

    Do you espy it? If not, notice closer at the order of the dates in the supposedly sorted "Date Modified" column. So yeah, that ancient Finder magic has not been entirely extinguished.

    There too remains some weirdness in the operation of the icon grid. In a view where grid snap is turned on (or is enabled transiently by holding down the command key during a drag) icons appear terrified of each other, leaving huge distances between themselves and their neighbors when they select which grid spot to snap to. It's as if the Finder lives in mortal alarm that one of these files will someday derive a 200-character filename that will overlap with a neighboring file's name.

    The worst incarnation of this conduct happens along the birthright edge of the screen where mounted volumes materialize on the desktop. (Incidentally, this is not the default; if you want to espy disks on your desktop, you must enable this preference in the Finder.) When I mount a new disk, I'm often surprised to espy where it ends up appearing. If there are any icons remotely near to the birthright edge of the screen, the disk icon will spurn to materialize there. Again, the Finder is not avoiding any actual title or icon overlapping. It appears to breathe avoiding the mere possibility of overlapping at some unspecified point in the future. Silly.

    Finder report card

    Overall, the Snow Leopard Finder takes several significant steps forward—64-bit/Cocoa future-proofing, a few new, useful features, added polish—and only a few shuffles backwards with the slight overuse of animation and the continued presence of some puzzling bugs. Considering how long it took the Carbon Finder to derive to its pre-Snow-Leopard feature set and even of polish, it's quite an achievement for a Cocoa Finder to match or exceed its predecessor in its very first release. I'm certain the Carbon vs. Cocoa warriors would occupy had a realm day with that statement, were Carbon not allot out to pasture in Leopard. But it was, and to the victor fade the spoils.

    Exchange

    Snow Leopard's headline "one new feature" is champion for Microsoft Exchange. This appears to be, at least partially, yet another hand-me-down from the iPhone, which gained champion for Exchange in its 2.0 release and expanded on it in 3.0. Snow Leopard's Exchange champion is weaved throughout the expected crop of applications in Mac OS X: iCal, Mail, and Address Book.

    The tall caveat is that it will only labor with a server running Exchange 2007 (Service Pack 1, Update Rollup 4) or later. While I'm certain Microsoft greatly appreciates any additional upgrade revenue this decision provides, it means that for users whose workplaces are still running older versions of Exchange, Snow Leopard's "Exchange support" might as well not exist.

    Those users are probably already running the only other viable Mac OS X Exchange client, Microsoft Entourage, so they'll likely just sit tense and wait for their IT departments to upgrade. Meanwhile, Microsoft is already making overtures to these users with the promised creation—finally—of an honest-to-goodness version of Outlook for Mac OS X.

    In my admittedly brief testing, Snow Leopard's Exchange champion seems to labor as expected. I had to occupy one of the Microsoft mavens in the Ars Orbiting HQ spin up an Exchange 2007 server just for the purposes of this review. However it was configured, totality I had to enter in the Mail application was my complete name, e-mail address, and password, and it automatically discovered totality material settings and configured iCal and Address bespeak for me.

    Exchange setup: surprisingly easyExchange setup: surprisingly easy

    Windows users are no doubt accustomed to this kindhearted of Exchange integration, but it's the first time I've seen it on the Mac platform—and that includes my many years of using Entourage.

    Access to Exchange-related features is decidedly subdued, in keeping with the existing interfaces for Mail, iCal, and Address Book. If you're expecting the swarm of panels and toolbar buttons create in Outlook on Windows, you're in for a bit of a shock. For example, here's the "detail" view of a meeting in iCal.

    iCal event detailiCal event detail

    Clicking the "edit" button hardly reveals more.

    Event editor: that's it?Event editor: that's it?

    The "availability" window too includes the bare minimum number of controls and displays to derive the job done.

    Meeting availability checker Enlarge / Meeting availability checker

    The integration into Mail and Address bespeak is even more subtle—almost entirely transparent. This is to breathe construed as a feature, I suppose. But though I don't know enough about Exchange to breathe completely sure, I can't shudder the sentiment that there are Exchange features that remain inaccessible from Mac OS X clients. For example, how consequence I bespeak a "resource" in a meeting? If there's a passage to consequence so, I couldn't discover it.

    Still, even basic Exchange integration out-of-the-box goes long passage towards making Mac OS X more welcome in corporate environments. It remains to breathe seen how convinced IT managers are of the "realness" of Snow Leopard's Exchange integration. But I've got to believe that being able to forward and receive mail, create and respond to meeting invitations, and expend the global corporate address bespeak is enough for any Mac user to derive along reasonably well in an Exchange-centric environment.

    Performance

    The thing is, there's not really much to affirm about performance in Snow Leopard. Dozens of benchmark graphs lead to the very simple conclusion: Snow Leopard is faster than Leopard. Not shockingly so, at least in the aggregate, but it's faster. And while isolating one particular subsystem with a micro-benchmark may betray some impressive numbers, it's the passage these small changes combine to ameliorate the real-world suffer of using the system that really makes a difference.

    One sample Apple gave at WWDC was making an initial Time Machine backup over the network to a Time Capsule. Apple's approach to optimizing this operation was to address each and every subsystem involved.

    Time Machine itself was given champion for overlapping i/o. Spotlight indexing, which happens on Time Machine volumes as well, was identified as another time-consuming chore involved in backups, so its performance was improved. The networking code was enhanced to select handicap of hardware-accelerated checksums where possible, and the software checksum code was hand-tuned for maximum performance. The performance of HFS+ journaling, which accompanies each file system metadata update, was too improved. For Time Machine backups that write to disk images rather than endemic HFS+ file systems, Apple added champion for concurrent access to disk images. The amount of network traffic produced by AFP during backups has too been reduced.

    All of this adds up to a respectable 55% overall improvement in the speed of an initial Time Machine backup. And, of course, the performance improvements to the individual subsystems capitalize totality applications that expend them, not just Time Machine.

    This holistic approach to performance improvement is not likely to knock anyone's socks off, but every time you speed across a piece of functionality in Snow Leopard that disproportionately benefits from one of these optimized subsystems, it's a pleasure.

    For example, Snow Leopard shuts down and restarts much faster than Leopard. I'm not talking about boot time; I beofvalue the time between the selection of the Shutdown or Restart command and when the system turns off or begins its new boot cycle. Leopard doesn't select long at totality to consequence this; only a few dozen of seconds when there are no applications open. But in Snow Leopard, it's so snappily that I often thought the operating system had crashed rather than shut down cleanly. (That's actually not too far from the truth.)

    The performance boosts offered by earlier major releases of Mac OS X still dwarf Snow Leopard's speedup, but that's mostly because Mac OS X was so excruciatingly sluggish in its early years. It's effortless to create a tall performance delta when you're starting from something abysmally slow. The fact that Snow Leopard achieves consistent, measurable improvements over the already-speedy Leopard is totality the more impressive.

    And yes, for the seventh consecutive time, a new release of Mac OS X is faster on the very hardware than its predecessor. (And for the first time ever, it's smaller, too.) What more can you inquireof for, really? Even that ancient performance bugaboo, window resizing, has been completely vanquished. Grab the corner of a fully-populated iCal window—the worst-case scenario for window resizing in the ancient days—and shudder it as snappily as you can. Your cursor will never breathe more than a few millimeters from the window's grab handle; it tracks your frantic motion perfectly. On most Macs, this is actually capable in Leopard as well. It just goes to present how far Mac OS X has forward on the performance front. These days, they totality just select it for granted, which is exactly the passage it should be.

    Grab bag

    In the "grab bag" section, I usually examine smaller, mostly unrelated features that don't warrant full-blown sections of their own. But when it comes to user-visible features, Snow Leopard is kindhearted of "all grab bag," if you know what I mean. Apple's even got its own incarnation in the shape of a giant webpage of "refinements." I'll probably overlap with some of those, but there'll breathe a few new ones here as well.

    New columns in open/save dialogs

    The list view in open and save dialog boxed now supports more than just "Name" and "Date Modified" columns. Right-click on any column to derive a selection of additional columns to display. I've wanted this feature for a long time, and I'm glad someone finally had time to implement it.

    Configurable columns in open/save dialogsConfigurable columns in open/save dialogs Improved scanner support

    The bundled Image Capture application now has the faculty to talk to a wide orbit of scanners. I plugged in my Epson Stylus CX7800, a device that previously required the expend of third-party software in order to expend the scanning feature, and Image Capture detected it immediately.

    Epson scanner + Image Capture - Epson software Enlarge / Epson scanner + Image Capture - Epson software

    Image Capture is too not a tainted diminutive scanning application. It has pretty capable automatic protest detection, including champion for multiple objects, obviating the necessity to manually crop items. Given the sometimes-questionable trait of third-party printer and scanner drivers for Mac OS X, the faculty to expend a bundled application is welcome.

    System Preferences bit wars

    System Preferences, dote virtually totality other applications in Snow Leopard, is 64-bit. But since 64-bit applications can't load 32-bit plug-ins, that presents a problem for the existing crop of 32-bit third-party preference panes. System Preferences handles this situation with a reasonable amount of grace. On launch, it will display icons for totality installed preference panes, 64-bit or 32-bit. But if you click on a 32-bit preference pane, you'll breathe presented with a notification dote this:

    64-bit application vs. 32-bit plug-in: fight!64-bit application vs. 32-bit plug-in: fight!

    Click "OK" and System Preferences will relaunch in 32-bit mode, which is conveniently indicated in the title bar. Since totality of the first-party preference panes are compiled for both 64-bit and 32-bit operation, System Preferences does not necessity to relaunch again for the duration of its use. This raises the question, why not occupy System Preferences launch in 32-bit mode totality the time? I suspect it's just another passage for Apple to "encourage" developers to build 64-bit-compatible binaries.

    Safari plug-ins

    The inability of of 64-bit applications load 32-bit plug-ins is a problem for Safari as well. Plug-ins are so famous to the Web suffer that relaunching in 32-bit mode is not really an option. You'd probably necessity to relaunch as soon as you visited your first webpage. But Apple does want Safari to speed in 64-bit mode due to some significant performance enhancements in the JavaScript engine and other areas of the application that are not available in 32-bit mode.

    Apple's solution is similar to what it did with QuickTime X and 32-bit QuickTime 7 plug-ins. Safari will speed 32-bit plug-ins in sever 32-bit processes as needed.

    Separate processes for 32-bit Safari plug-insSeparate processes for 32-bit Safari plug-ins

    This has the added, extremely significant capitalize of isolating potentially buggy plug-ins. According to the automated crash reporting built into Mac OS X, Apple has said that the number one cause of crashes is Web browser plug-ins. That's not the number one cause of crashes in Safari, reason you, it's the number one cause when considering totality crashes of totality applications in Mac OS X. (And though it was not mentioned by name, I believe they totality know the primary culprit.)

    As you can espy above, the QuickTime browser plug-in gets the very treatment as glisten and other third-party 32-bit Safari plug-ins. totality of this means that when a plug-in crashes, Safari in Snow Leopard does not. The window or tab containing the crashing plug-in doesn't even close. You can simply click the reload button and give the problematic plug-in another casual to duty correctly.

    While this is still far from the much more robust approach employed by Google Chrome, where each tab lives in its own independent process, if Apple's crash statistics are to breathe believed, isolating plug-ins may generate most of the capitalize of truly sever processes with a significantly less radical change to the Safari application itself.

    Resolution independence

    When they final left Mac OS X in its seemingly interminable march towards a truly scalable user interface, it was almost ready for prime time. I'm wretched to affirm that resolution independence was obviously not a priority in Snow Leopard, because it hasn't gotten any better, and may occupy actually regressed a bit. Here's what TextEdit looks dote at a 2.0 scale factor in Leopard and Snow Leopard.

    TextEdit at scale factor 2.0 in LeopardTextEdit at scale factor 2.0 in Leopard TextEdit at scale factor 2.0 in Snow LeopardTextEdit at scale factor 2.0 in Snow Leopard

    Yep, it's a bummer. I still bethink Apple advising developers to occupy their applications ready for resolution independence by 2008. That's one of the few dates that the Jobs-II-era Apple has not been able to hit, and it's getting later totality the time. On the other hand, it's not dote 200-DPI monitors are raining from the sky either. But I'd really dote to espy Apple derive going on this. It will undoubtedly select a long time for everything to notice and labor correctly, so let's derive started.

    Terminal splitters

    The Terminal application in Tiger and earlier versions of Mac OS X allowed each of its windows to breathe split horizontally into two sever panes. This was invaluable for referencing some earlier text in the scrollback while too typing commands at the prompt. Sadly, the splitter feature disappeared in Leopard. In Snow Leopard, it's back with a vengeance.

    Arbitrary splitters, baby!Arbitrary splitters, baby!

    (Now if only my favorite text editor would derive on board the train to splittersville.)

    Terminal in Snow Leopard too defaults to the new Menlo font. But balky to earlier reports, the One capable Monospaced Font, Monaco, is most definitely still included in Snow Leopard (see screenshot above) and it works just fine.

    System Preferences shuffle

    The seemingly obligatory rearrangement of preference panes in the System Preferences application accompanying each release of Mac OS X continues in Snow Leopard.

    System Preferences: shuffled yet again Enlarge / System Preferences: shuffled yet again System Preferences (not running) with Dock menuSystem Preferences (not running) with Dock menu

    This time, the "Keyboard & Mouse" preference pane is split into sever "Keyboard" and "Mouse" panes, "International" becomes "Language & Text," and the "Internet & Network" section becomes "Internet & Wireless" and adopts the Bluetooth preference pane.

    Someday in the distant future, perhaps Apple will finally arrive at the "ultimate" arrangement of preference panes and they can totality finally fade more than two years without their muscle remembrance being disrupted.

    Before touching on, System Preferences has one trim trick. You can launch directly into a specific preference pane by right-clicking on System Preferences's Dock icon. This works even when System Preferences is not yet running. kindhearted of creepy, but useful.

    Core location

    One more gift from the iPhone, Core Location, allows Macs to figure out where in the world they are. The "Date & Time" preference pane offers to set your time zone automatically based on your current location using this newfound ability.

    Set your Mac's time zone automatically based on your current location, thanks to Core Location.Set your Mac's time zone automatically based on your current location, thanks to Core Location. Keyboard magic

    Snow Leopard includes a simple facility for system-wide text auto-correction and expansion, accessible from the "Language & Text" preference pane. It's not quite ready to give a dedicated third-party application a speed for its money, but hey, it's free.

    Global text expansion and auto-correction Enlarge / Global text expansion and auto-correction

    The keyboard shortcuts preference pane has too been rearranged. Now, instead of a single, long list of system-wide keyboard shortcuts, they're arranged into categories. This reduces clutter, but it too makes it a bit more difficult to find the shortcut you're interested in.

    Keyboard shortcuts: now with categories Enlarge / Keyboard shortcuts: now with categories The sleeping Mac dilemma

    I don't dote to leave my Mac Pro turned on 24 hours a day, especially during the summer in my un-air-conditioned house. But I consequence want to occupy access to the files on my Mac when I'm elsewhere—at work, on the road, etc. It is workable to wake a sleeping Mac remotely, but doing so requires being on the very local network.

    My solution has been to leave a smaller, more power-efficient laptop on at totality times on the very network as my Mac Pro. To wake my Mac Pro remotely, I ssh into the laptop, then forward the magic "wake up" packet to my Mac Pro. (For this to work, the "Wake for Ethernet network administrator access" checkbox must breathe checked in the "Energy Saver" preference pane in System Preferences.)

    Snow Leopard provides a passage to consequence this without leaving any of my computers running totality day. When a Mac running Snow Leopard is allot to sleep, it attempts to hand off ownership of its IP address to its router. (This only works with an AirPort Extreme foundation station from 2007 or later, or a Time Capsule from 2008 or later with the latest (7.4.2) firmware installed.) The router then listens for any attempt to connect to the IP address. When one occurs, it wakes up the original owner, hands back the IP address, and forwards traffic appropriately.

    You can even wake some recent-model Macs over WiFi. Combined with MobileMe's "Back to My Mac" dynamic DNS thingamabob, it means I can leave totality my Macs asleep and still occupy access to their contents anytime, anywhere.

    Back to my hack

    As has become traditional, this new release of Mac OS X makes life a bit harder for developers whose software works by patching the in-memory representation of other running applications or the operating system itself. This includes Input Managers, SIMBL plug-ins, and of course the dreaded "Haxies."

    Input Managers derive the worst of it. They've actually been unsupported and non-functional in 64-bit applications since Leopard. That wasn't such a tall deal when Mac OS X shipped with a whopping two 64-bit applications. But now, with almost every application in Snow Leopard going 64-bit, it's suddenly very significant.

    Thanks to Safari's want of an officially sanctioned extension mechanism, developers looking to enhance its functionality occupy most often resorted to the expend of Input Managers and SIMBL (which is an Input-Manager-based framework). A 64-bit Safari puts a damper on that entire market. Though it is workable to manually set Safari to launch in 32-bit mode—Get Info on the application in the Finder and click a checkbox—ideally, this is not something developers want to force users to do.

    Happily, at least one commonly used Safari enhancement has the capable fortune to breathe built on top of the officially supported browser plug-in API used by Flash, QuickTime, etc. But that may not breathe a feasible approach for Safari extensions that enhance functionality in ways not tied directly to the display of particular types of content within a webpage.

    Though I arrangement to speed Safari in its default 64-bit mode, I'll really miss Saft, a Safari extension I expend for session restoration (yes, I know Safari has this feature, but it's activated manually—the horror) and address bar shortcuts (e.g., "w noodles" to notice up "noodles" in Wikipedia). I'm hoping that ingenious developers will find a passage to overcome this new challenge. They always appear to, in the end. (Or Apple could add a proper extension system to Safari, of course. But I'm not holding my breath.)

    As for the Haxies, those usually rupture with each major operating system update as a matter of course. And each time, those determined fellows at Unsanity, against totality odds, manage to support their software working. I salute them for their effort. I delayed upgrading to Leopard for a long time based solely on the absence of my beloved WindowShade X. I hope I don't occupy to wait too long for a Snow-Leopard-compatible version.

    The common trend in Mac OS X is away from any sort of involuntary remembrance space sharing, and towards "external" plug-ins that live in their own, sever processes. Even contextual menu plug-ins in the Finder occupy been disabled, replaced by an enhanced, but still less-powerful Services API. Again, I occupy faith that developers will adapt. But the waiting is the hardest part.

    ZFS MIA

    It looks dote we'll totality breathe waiting a while longer for a file system in shining armor to replace the venerable HFS+ (11 years young!) as the default file system in Mac OS X. Despite rumors, outright declarations, and much actual pre-release code, champion for the impressive ZFS file system is not present in Snow Leopard.

    That's a shame because Time Machine veritably cries out for some ZFS magic. What's more, Apple seems to agree, as evidenced by a post from an Apple employee to a ZFS mailing list final year. When asked about a ZFS-savvy implementation of Time Machine, the reply was encouraging: "This one is famous and likely will forward sometime, but not for SL." ("SL" is short for Snow Leopard.)

    There are many reasons why ZFS (or a file system with similar features) is a impeccable meet for Time Machine, but the most famous is its faculty to forward only the block-level changes during each backup. As Time Machine is currently implemented, if you beget a small change to a giant file, the entire giant file is copied to the Time Machine volume during the next backup. This is extremely wasteful and time consuming, especially for large files that are modified constantly during the day (e.g., Entourage's e-mail database). Time Machine running on top of ZFS could transfer just the changed disk blocks (a maximum of 128KB each in ZFS, and usually much smaller).

    ZFS would too bring vastly increased robustness for data and metadata, a pooled storage model, constant-time snapshots and clones, and a pony. People sometimes inquireof what, exactly, is wrong with HFS+. Aside from its obvious want of the features just listed, HFS+ is limited in many ways by its dated design, which is based on HFS, a twenty-five year-old file system.

    To give just one example, the centrally located Catalog File, which must breathe updated for each change to the file system's structure, is a frequent and inevitable source of contention. Modern file systems usually spread their metadata around, both for robustness (multiple copies are often kept in sever locations on the disk) and to allow for better concurrency.

    Practically speaking, believe about those times when you speed Disk Utility on an HFS+ volume and it finds (and hopefully repairs) a bunch of errors. That's bad, okay? That's something that should not betide with a modern, thoroughly checksummed, always-consistent-on-disk file system unless there are hardware problems (and a ZFS storage pool can actually deal with that as well). And yet it happens totality the time with HFS+ disks in Mac OS X when various bits of metadata derive corrupted or become out of date.

    Apple gets by year after year, tacking new features onto HFS+ with duct tape and a prayer, but at a inescapable point there simply has to breathe a successor—whether it's ZFS, a home-grown Apple file system, or something else entirely. My fingers are crossed for Mac OS X 10.7.

    The future soon

    Creating an operating system is as much a social exercise as a technological one. Creating a platform, even more so. totality of Snow Leopard's considerable technical achievements are not just designed to capitalize users; they're too intended to goad, persuade, and otherwise herd developers in the direction that Apple feels will breathe most advantageous for the future of the platform.

    For this to work, Snow Leopard has to actually find its passage into the hands of customers. The pricing helps a lot there. But even if Snow Leopard were free, there's still some cost to the consumer—in time, worry, software updates, etc.—when performing a major operating system upgrade. The very goes for developers who must, at the very least, certify that their existing applications speed correctly on the new OS.

    The habitual passage to overcome this kindhearted of upgrade hesitation has been to pack the OS with new features. New features sell, and the more copies of the new operating system in use, the more motivated developers are to update their applications to not just speed on the new OS, but too select handicap of its new abilities.

    A major operating system upgrade with "no new features" must play by a different set of rules. Every party involved expects some counterbalance to the want of new features. In Snow Leopard, developers stand to gleam the biggest benefits thanks to an impressive set of new technologies, many of which cover areas previously unaddressed in Mac OS X. Apple clearly feels that the future of the platform depends on much better utilization of computing resources, and is doing everything it can to beget it effortless for developers to roam in this direction.

    Though it's obvious that Snow Leopard includes fewer external features than its predecessor, I'd wager that it has just as many, if not more internal changes than Leopard. This, I fear, means that the initial release of Snow Leopard will likely suffer the typical 10.x.0 bugs. There occupy already been reports of new bugs introduced to existing APIs in Snow Leopard. This is the exact contrary of Snow Leopard's implied promise to users and developers that it would concentrate on making existing features faster and more robust without introducing new functionality and the accompanying new bugs.

    On the other side of the coin, I imagine totality the teams at Apple that worked on Snow Leopard absolutely reveled in the occasion to polish their particular subsystems without being burdened by supporting the marketing-driven feature-of-the-month. In any long-lived software product, there needs to breathe this kindhearted of release valve every few years, lest the entire code foundation fade off into the weeds.

    There's been one other "no new features" release of Mac OS X. Mac OS X 10.1, released a mere six months after version 10.0, was handed out for free by Apple at the 2001 Seybold publishing conference and, later, at Apple retail stores. It was too available from Apple's online store for $19.95 (along with a copy of Mac OS 9.2.1 for expend in the Classic environment). This was a different time for Mac OS X. Versions 10.0 and 10.1 were slow, incomplete, and extremely immature; the transition from classic Mac OS was far from over.

    Judged as a modern incarnation of the 10.1 release, Snow Leopard looks pretty darned good. The pricing is similar, and the benefits—to developers and to users—are greater. So is the risk. But again, that has more to consequence with how horrible Mac OS X 10.0 was. Choosing not to upgrade to 10.1 was unthinkable. Waiting a while to upgrade to Snow Leopard is reasonable if you want to breathe certain that totality the software you trust about is compatible. But don't wait too long, because at $29 for the upgrade, I await Snow Leopard adoption to breathe quite rapid. Software that will speed only on Snow Leopard may breathe here before you know it.

    Should you buy Mac OS X Snow Leopard? If you're already running Leopard, then the acknowledge is a resounding "yes." If you're still running Tiger, well, then it's probably time for a new Mac anyway. When you buy one, it'll forward with Snow Leopard.

    As for the future, it's tempting to view Snow Leopard as the "tick" in a new Intel-style "tick-tock" release strategy for Mac OS X: radical new features in version 10.7 followed by more Snow-Leopard-style refinements in 10.8, and so on, alternating between "feature" and "refinement" releases. Apple has not even hinted that they're considering this ilk of plan, but I believe there's a lot to recommend it.

    Snow Leopard is a unique and fine release, unlike any that occupy forward before it in both scope and intention. At some point, Mac OS X will surely necessity to derive back on the bullet-point-features bandwagon. But for now, I'm content with Snow Leopard. It's the Mac OS X I know and love, but with more of the things that beget it decrepit and offbeat engineered away.

    Snowy eyes Looking back

    This is the tenth review of a complete Mac OS X release, public beta, or developer preview to speed on Ars, dating back to December 1999 and Mac OS X DP2. If you want to jump into the Wayback Machine and espy how far Apple has forward with Snow Leopard (or just want to bone up on totality of the tall cat monikers), we've gone through the archives and dug up some of their older Mac OS X articles. joyful reading!

  • Five years of Mac OS X, March 24, 2006
  • Mac OS X 10.5 Leopard, October 28, 2007
  • Mac OS X 10.4 Tiger, April 28, 2005
  • Mac OS X 10.3 Panther, November 9, 2003
  • Mac OS X 10.2 Jaguar, September 5, 2002
  • Mac OS X 10.1 (Puma), October 15, 2001
  • Mac OS X 10.0 (Cheetah), April 2, 2001
  • Mac OS X Public Beta, October 3, 2000
  • Mac OS X Q & A, June 20, 2000
  • Mac OS X DP4, May 24, 2000
  • Mac OS X DP3: tribulation by Water, February 28, 2000
  • Mac OS X Update: Quartz & Aqua, January 17, 2000
  • Mac OS X DP2, December 14, 1999

  • Mozilla ends Firefox champion for Mac OS Tiger | killexams.com existent questions and Pass4sure dumps

    How collaboration apps foster digital transformation

    Next Firefox to drop Mac OS X 10.4 champion | killexams.com existent questions and Pass4sure dumps

    Mozilla has officially decided that the next major version of Firefox will require at least Mac OS X 10.5 when running on Apple computers.

    "We believe a Mac OS X 10.5 minimum will allow us to provide the best suffer workable to their users," Mozilla Mac programmer Josh Aas said Tuesday in a mailing list announcement. Firefox is built on a browser engine called Gecko, and the upcoming version 1.9.3 will occupy technology for Mac OS X 10.4 and before removed, he said.

    The recently released Firefox 3.6 works on Mac OS X 10.4, aka Tiger. Mozilla will champion it for some months after the browser's replacement version is issued, which means 10.4 champion should continue into 2011.

    Aas ran into some resistance earlier this month when he announced Mozilla's crave to drop Mac OS X 10.4 support. In a sever mailing list comment, Mozilla's Asa Dotzler expressed some enthusiasm for trying to embolden people to upgrade.

    "It's dote a public health issue. Internet-connected computers that are not kept up to date and secure are almost guaranteed to derive compromised and those infected machines are used to assault the ease of the Internet users with spam, more malware, or DDOSes," Dotzler said, referring to distributed denial-of-service attacks. "It's not just a personal selection and as stewards of a wholesome Internet, Mozilla is in a unique position to thrust this kindhearted of messaging. We're not trying to sell people new hardware or software or worthless anti-virus measures, so they should breathe able to communicate this well without people assuming some ulterior (profit) motive."

    Mozilla is working on an update to Firefox 3.6, which uses Gecko 1.9.2, that puts plug-ins such as Adobe glisten and Microsoft Silverlight into a sever remembrance location in an application to increase stability. The group hopes to release a beta version of that Firefox version by the terminate of March.

    Separately, Mozilla is working on Gecko 1.9.3 and plans to issue a new alpha release of the software this week.

    Correction at 9:55 a.m. PST: The headline has been fixed to reflect the proper version of Mac OS X.



    Direct Download of over 5500 Certification Exams

    3COM [8 Certification Exam(s) ]
    AccessData [1 Certification Exam(s) ]
    ACFE [1 Certification Exam(s) ]
    ACI [3 Certification Exam(s) ]
    Acme-Packet [1 Certification Exam(s) ]
    ACSM [4 Certification Exam(s) ]
    ACT [1 Certification Exam(s) ]
    Admission-Tests [13 Certification Exam(s) ]
    ADOBE [93 Certification Exam(s) ]
    AFP [1 Certification Exam(s) ]
    AICPA [2 Certification Exam(s) ]
    AIIM [1 Certification Exam(s) ]
    Alcatel-Lucent [13 Certification Exam(s) ]
    Alfresco [1 Certification Exam(s) ]
    Altiris [3 Certification Exam(s) ]
    Amazon [2 Certification Exam(s) ]
    American-College [2 Certification Exam(s) ]
    Android [4 Certification Exam(s) ]
    APA [1 Certification Exam(s) ]
    APC [2 Certification Exam(s) ]
    APICS [2 Certification Exam(s) ]
    Apple [69 Certification Exam(s) ]
    AppSense [1 Certification Exam(s) ]
    APTUSC [1 Certification Exam(s) ]
    Arizona-Education [1 Certification Exam(s) ]
    ARM [1 Certification Exam(s) ]
    Aruba [8 Certification Exam(s) ]
    ASIS [2 Certification Exam(s) ]
    ASQ [3 Certification Exam(s) ]
    ASTQB [8 Certification Exam(s) ]
    Autodesk [2 Certification Exam(s) ]
    Avaya [101 Certification Exam(s) ]
    AXELOS [1 Certification Exam(s) ]
    Axis [1 Certification Exam(s) ]
    Banking [1 Certification Exam(s) ]
    BEA [5 Certification Exam(s) ]
    BICSI [2 Certification Exam(s) ]
    BlackBerry [17 Certification Exam(s) ]
    BlueCoat [2 Certification Exam(s) ]
    Brocade [4 Certification Exam(s) ]
    Business-Objects [11 Certification Exam(s) ]
    Business-Tests [4 Certification Exam(s) ]
    CA-Technologies [20 Certification Exam(s) ]
    Certification-Board [10 Certification Exam(s) ]
    Certiport [3 Certification Exam(s) ]
    CheckPoint [43 Certification Exam(s) ]
    CIDQ [1 Certification Exam(s) ]
    CIPS [4 Certification Exam(s) ]
    Cisco [318 Certification Exam(s) ]
    Citrix [48 Certification Exam(s) ]
    CIW [18 Certification Exam(s) ]
    Cloudera [10 Certification Exam(s) ]
    Cognos [19 Certification Exam(s) ]
    College-Board [2 Certification Exam(s) ]
    CompTIA [76 Certification Exam(s) ]
    ComputerAssociates [6 Certification Exam(s) ]
    Consultant [2 Certification Exam(s) ]
    Counselor [4 Certification Exam(s) ]
    CPP-Institute [4 Certification Exam(s) ]
    CSP [1 Certification Exam(s) ]
    CWNA [1 Certification Exam(s) ]
    CWNP [13 Certification Exam(s) ]
    CyberArk [1 Certification Exam(s) ]
    Dassault [2 Certification Exam(s) ]
    DELL [11 Certification Exam(s) ]
    DMI [1 Certification Exam(s) ]
    DRI [1 Certification Exam(s) ]
    ECCouncil [22 Certification Exam(s) ]
    ECDL [1 Certification Exam(s) ]
    EMC [128 Certification Exam(s) ]
    Enterasys [13 Certification Exam(s) ]
    Ericsson [5 Certification Exam(s) ]
    ESPA [1 Certification Exam(s) ]
    Esri [2 Certification Exam(s) ]
    ExamExpress [15 Certification Exam(s) ]
    Exin [40 Certification Exam(s) ]
    ExtremeNetworks [3 Certification Exam(s) ]
    F5-Networks [20 Certification Exam(s) ]
    FCTC [2 Certification Exam(s) ]
    Filemaker [9 Certification Exam(s) ]
    Financial [36 Certification Exam(s) ]
    Food [4 Certification Exam(s) ]
    Fortinet [14 Certification Exam(s) ]
    Foundry [6 Certification Exam(s) ]
    FSMTB [1 Certification Exam(s) ]
    Fujitsu [2 Certification Exam(s) ]
    GAQM [9 Certification Exam(s) ]
    Genesys [4 Certification Exam(s) ]
    GIAC [15 Certification Exam(s) ]
    Google [4 Certification Exam(s) ]
    GuidanceSoftware [2 Certification Exam(s) ]
    H3C [1 Certification Exam(s) ]
    HDI [9 Certification Exam(s) ]
    Healthcare [3 Certification Exam(s) ]
    HIPAA [2 Certification Exam(s) ]
    Hitachi [30 Certification Exam(s) ]
    Hortonworks [4 Certification Exam(s) ]
    Hospitality [2 Certification Exam(s) ]
    HP [752 Certification Exam(s) ]
    HR [4 Certification Exam(s) ]
    HRCI [1 Certification Exam(s) ]
    Huawei [21 Certification Exam(s) ]
    Hyperion [10 Certification Exam(s) ]
    IAAP [1 Certification Exam(s) ]
    IAHCSMM [1 Certification Exam(s) ]
    IBM [1533 Certification Exam(s) ]
    IBQH [1 Certification Exam(s) ]
    ICAI [1 Certification Exam(s) ]
    ICDL [6 Certification Exam(s) ]
    IEEE [1 Certification Exam(s) ]
    IELTS [1 Certification Exam(s) ]
    IFPUG [1 Certification Exam(s) ]
    IIA [3 Certification Exam(s) ]
    IIBA [2 Certification Exam(s) ]
    IISFA [1 Certification Exam(s) ]
    Intel [2 Certification Exam(s) ]
    IQN [1 Certification Exam(s) ]
    IRS [1 Certification Exam(s) ]
    ISA [1 Certification Exam(s) ]
    ISACA [4 Certification Exam(s) ]
    ISC2 [6 Certification Exam(s) ]
    ISEB [24 Certification Exam(s) ]
    Isilon [4 Certification Exam(s) ]
    ISM [6 Certification Exam(s) ]
    iSQI [7 Certification Exam(s) ]
    ITEC [1 Certification Exam(s) ]
    Juniper [65 Certification Exam(s) ]
    LEED [1 Certification Exam(s) ]
    Legato [5 Certification Exam(s) ]
    Liferay [1 Certification Exam(s) ]
    Logical-Operations [1 Certification Exam(s) ]
    Lotus [66 Certification Exam(s) ]
    LPI [24 Certification Exam(s) ]
    LSI [3 Certification Exam(s) ]
    Magento [3 Certification Exam(s) ]
    Maintenance [2 Certification Exam(s) ]
    McAfee [8 Certification Exam(s) ]
    McData [3 Certification Exam(s) ]
    Medical [68 Certification Exam(s) ]
    Microsoft [375 Certification Exam(s) ]
    Mile2 [3 Certification Exam(s) ]
    Military [1 Certification Exam(s) ]
    Misc [1 Certification Exam(s) ]
    Motorola [7 Certification Exam(s) ]
    mySQL [4 Certification Exam(s) ]
    NBSTSA [1 Certification Exam(s) ]
    NCEES [2 Certification Exam(s) ]
    NCIDQ [1 Certification Exam(s) ]
    NCLEX [3 Certification Exam(s) ]
    Network-General [12 Certification Exam(s) ]
    NetworkAppliance [39 Certification Exam(s) ]
    NI [1 Certification Exam(s) ]
    NIELIT [1 Certification Exam(s) ]
    Nokia [6 Certification Exam(s) ]
    Nortel [130 Certification Exam(s) ]
    Novell [37 Certification Exam(s) ]
    OMG [10 Certification Exam(s) ]
    Oracle [282 Certification Exam(s) ]
    P&C [2 Certification Exam(s) ]
    Palo-Alto [4 Certification Exam(s) ]
    PARCC [1 Certification Exam(s) ]
    PayPal [1 Certification Exam(s) ]
    Pegasystems [12 Certification Exam(s) ]
    PEOPLECERT [4 Certification Exam(s) ]
    PMI [15 Certification Exam(s) ]
    Polycom [2 Certification Exam(s) ]
    PostgreSQL-CE [1 Certification Exam(s) ]
    Prince2 [6 Certification Exam(s) ]
    PRMIA [1 Certification Exam(s) ]
    PsychCorp [1 Certification Exam(s) ]
    PTCB [2 Certification Exam(s) ]
    QAI [1 Certification Exam(s) ]
    QlikView [1 Certification Exam(s) ]
    Quality-Assurance [7 Certification Exam(s) ]
    RACC [1 Certification Exam(s) ]
    Real Estate [1 Certification Exam(s) ]
    Real-Estate [1 Certification Exam(s) ]
    RedHat [8 Certification Exam(s) ]
    RES [5 Certification Exam(s) ]
    Riverbed [8 Certification Exam(s) ]
    RSA [15 Certification Exam(s) ]
    Sair [8 Certification Exam(s) ]
    Salesforce [5 Certification Exam(s) ]
    SANS [1 Certification Exam(s) ]
    SAP [98 Certification Exam(s) ]
    SASInstitute [15 Certification Exam(s) ]
    SAT [1 Certification Exam(s) ]
    SCO [10 Certification Exam(s) ]
    SCP [6 Certification Exam(s) ]
    SDI [3 Certification Exam(s) ]
    See-Beyond [1 Certification Exam(s) ]
    Siemens [1 Certification Exam(s) ]
    Snia [7 Certification Exam(s) ]
    SOA [15 Certification Exam(s) ]
    Social-Work-Board [4 Certification Exam(s) ]
    SpringSource [1 Certification Exam(s) ]
    SUN [63 Certification Exam(s) ]
    SUSE [1 Certification Exam(s) ]
    Sybase [17 Certification Exam(s) ]
    Symantec [135 Certification Exam(s) ]
    Teacher-Certification [4 Certification Exam(s) ]
    The-Open-Group [8 Certification Exam(s) ]
    TIA [3 Certification Exam(s) ]
    Tibco [18 Certification Exam(s) ]
    Trainers [3 Certification Exam(s) ]
    Trend [1 Certification Exam(s) ]
    TruSecure [1 Certification Exam(s) ]
    USMLE [1 Certification Exam(s) ]
    VCE [6 Certification Exam(s) ]
    Veeam [2 Certification Exam(s) ]
    Veritas [33 Certification Exam(s) ]
    Vmware [58 Certification Exam(s) ]
    Wonderlic [2 Certification Exam(s) ]
    Worldatwork [2 Certification Exam(s) ]
    XML-Master [3 Certification Exam(s) ]
    Zend [6 Certification Exam(s) ]





    References :


    Dropmark : http://killexams.dropmark.com/367904/11514457
    Wordpress : http://wp.me/p7SJ6L-sO
    Scribd : https://www.scribd.com/document/358140011/Pass4sure-9L0-060-Braindumps-and-Practice-Tests-with-Real-Questions
    weSRCH : https://www.wesrch.com/business/prpdfBU1HWO000FSGN
    Issu : https://issuu.com/trutrainers/docs/9l0-060
    Dropmark-Text : http://killexams.dropmark.com/367904/12072367
    Youtube : https://youtu.be/4cboa9WUoRY
    Blogspot : http://killexams-braindumps.blogspot.com/2017/10/pass4sure-9l0-060-practice-tests-with.html
    RSS Feed : http://feeds.feedburner.com/DontMissTheseApple9l0-060Dumps
    Vimeo : https://vimeo.com/243594918
    Google+ : https://plus.google.com/112153555852933435691/posts/en6mPyzMHLx?hl=en
    publitas.com : https://view.publitas.com/trutrainers-inc/ensure-your-success-with-this-9l0-060-question-bank
    Calameo : http://en.calameo.com/account/book#
    Box.net : https://app.box.com/s/nd843u4l6jqq00ah3ow7wpgaq7tk4lr3
    zoho.com : https://docs.zoho.com/file/5kgmr69826c61d00d4b0e95b76c04843ce7f1






    Back to Main Page

    www.pass4surez.com | www.killcerts.com | www.search4exams.com