{"id":4357,"date":"2012-02-20T17:18:33","date_gmt":"2012-02-20T22:18:33","guid":{"rendered":"http:\/\/mjtsai.com\/blog\/?p=4357"},"modified":"2019-07-30T09:52:28","modified_gmt":"2019-07-30T13:52:28","slug":"os-x-10-8-mountain-lion","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2012\/02\/20\/os-x-10-8-mountain-lion\/","title":{"rendered":"OS X 10.8 Mountain Lion"},"content":{"rendered":"

Mountain Lion<\/a> is said to arrive this summer, with Apple returning to a yearly update schedule. More frequent upgrades should help speed the adoption of new APIs and Objective-C language features, but I question whether Apple has the resources to pull this off. Some would say that it’s already stretched thin between Mac and iOS development and that quality has suffered<\/a>. Indeed, the yearly schedule had already proved unsustainable before the iPhone was released.<\/p>\n

A new release every year means that Apple will need to produce a continuous stream of new user-facing features that can appear in screenshots and on feature lists. But what I want most from OS upgrades (and the developer tools<\/a>) are bug fixes, stability, and polish. Despite the Lion-derived name, Mountain Lion seems to be more of a “feature” release than Snow Leopard. Have we seen the end of super-stable releases like Mac OS X 10.5.8 and 10.6.8? Developers can provide plenty of exciting new features and apps if they have a solid foundation to build upon. By the same token, if there’s a constant churn and the ground is always shifting, we burn development and support time without having much to show for it. It also makes it harder to be ruthless<\/a>. So I question the wisdom of having yearly updates to both OS X and iOS.<\/p>\n

Some of the more egregious problems with Lion’s Address Book<\/a> and iCal<\/a> seem to be fixed. (The skeuomorphic chrome<\/a> remains in place, though.) And there’s some cool new stuff in Mountain Lion for developers. More in-depth discussion will have to wait until the NDA is lifted.<\/p>\n

The biggest news is, of course, Gatekeeper<\/a> and the Developer ID—which are along the lines of the system that Wil Shipley<\/a> proposed. The technology behind Gatekeeper is good and unsurprising<\/a>. What’s important is how Apple will use it and what comes next.<\/p>\n

Is Gatekeeper proof that Apple wants a vibrant Mac software market outside of the Mac App Store? Or is it just another click of the ratchet to a future where all software must be approved by Apple? I think it’s a Rorschach test; the facts can interpreted either way. On the one hand, it’s encouraging that Apple is providing for a level of security between zero and fully sandboxed. That’s a win for users, developers, and Apple. On the other hand, adding a Gatekeeper-like feature would also be a necessary transition step towards a more restricted world. We went from total freedom to a Security preferences pane that offers three radio buttons for which types of apps are allowed. The next step could be reducing it to two or to one.<\/p>\n

The bottom line: are you more worried about Apple having a killswitch for your favorite apps than you are about a family member downloading and launching a malicious app that said killswitch would have protected against? Right now, with almost no Mac malware, it seems unnecessary to make any sort of tradeoff. But it’s prudent to be ready in case that changes.<\/p>\n

Here are some areas to watch going forward:<\/p>\n

    \n
  1. What language will Apple use to describe apps that don’t use Developer ID? How strong will the implication be that they’re unsafe or second-class?<\/li>\n
  2. Will Apple only use Gatekeeper to block true malware? Originally we were told that the iTunes App Store review process was to protect users and the cell network. Apple would provide some common-sense guidelines that determined which apps would be improved and rejected. What actually happened was that app review was capricious. Apple rejected some apps for business and political reasons. It approved others that clearly violated the guidelines. Some types of safe apps were unwanted. Other apps had “too many” competitors in their genre.<\/li>\n
  3. Will Gatekeeper eventually step in below the file quarantine level?<\/li>\n
  4. What recourse is there for an application that’s mistakenly identified as malware?<\/li>\n
  5. Will apps from identified developers have access to the same APIs<\/a> as apps in the Mac App Store? Currently the answer is No, and Mountain Lion has added more such APIs, widening the gulf. Actions speak louder than words, and Apple has yet to even say that it desires parity. Thus, I’m skeptical of the feel-good rhetoric to Panic about not poisoning the well.<\/li>\n
  6. What will happen on March 1? It’s now been more than eight months since the sandbox’s semi-secret debut at WWDC 2011. At the technical level, it still isn’t ready for primetime. At the policy level, it’s still unclear what the March deadline means. And communication from Apple has been almost entirely absent on these important issues. Originally it made a kind of sense that, if the sandbox implementation had been complete and solid, it should be adopted before the next major release of the OS. Now, with Mountain Lion scheduled for this summer, I don’t see how Apple can justify imposing the sandbox on Lion. There isn’t even a mechanism to prevent sandboxed apps from launching, and causing harm, on the earlier versions of Lion that had more bugs.<\/li>\n
  7. Will Apple add support for Developer ID apps to iOS? This seems incredibly unlikely, but it sure would be effective at restoring goodwill. It’s becoming increasingly clear to people that the App Store doesn’t guarantee safety, and Gatekeeper shows that other options are possible.<\/li>\n<\/ol>\n

    See also the posts from Matt Alexander<\/a>, Marco Arment<\/a>, Rainer Brockerhoff<\/a>, Jacqui Cheng<\/a>, Andrew Cunningham and Anand Lal Shimpi<\/a>, Dustin Curtis<\/a>, Chris Foresman<\/a>, Dan Frakes<\/a>, Steven Frank<\/a>, Jean-Louis Gassée<\/a>, John Gruber<\/a>, Pierre Igot<\/a>, Daniel Jalkut<\/a>, Jesper<\/a>, Rich Mogull<\/a>, Dan Moren<\/a>, David Pogue<\/a>, John Siracusa<\/a>, Jason Snell<\/a>, Sean Sullivan<\/a>, The Talk Show<\/a>, Marcel Weiher<\/a>, and Dave Winer<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"

    Mountain Lion is said to arrive this summer, with Apple returning to a yearly update schedule. More frequent upgrades should help speed the adoption of new APIs and Objective-C language features, but I question whether Apple has the resources to pull this off. Some would say that it’s already stretched thin between Mac and iOS […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"apple_news_api_created_at":"2019-07-30T13:52:31Z","apple_news_api_id":"28d3e8f5-e3a2-4a3e-a35b-64e0d3089d16","apple_news_api_modified_at":"2019-07-30T13:52:31Z","apple_news_api_revision":"AAAAAAAAAAD\/\/\/\/\/\/\/\/\/\/w==","apple_news_api_share_url":"https:\/\/apple.news\/AKNPo9eOiSj6jW2Tg0widFg","apple_news_coverimage":0,"apple_news_coverimage_caption":"","apple_news_is_hidden":false,"apple_news_is_paid":false,"apple_news_is_preview":false,"apple_news_is_sponsored":false,"apple_news_maturity_rating":"","apple_news_metadata":"\"\"","apple_news_pullquote":"","apple_news_pullquote_position":"","apple_news_slug":"","apple_news_sections":"\"\"","apple_news_suppress_video_url":false,"apple_news_use_image_component":false,"footnotes":""},"categories":[2],"tags":[1846,30,17,53],"class_list":["post-4357","post","type-post","status-publish","format-standard","hentry","category-technology","tag-app-review","tag-mac","tag-mountainlion","tag-sandboxing"],"apple_news_notices":[],"_links":{"self":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/4357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/comments?post=4357"}],"version-history":[{"count":11,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/4357\/revisions"}],"predecessor-version":[{"id":4412,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/4357\/revisions\/4412"}],"wp:attachment":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/media?parent=4357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/categories?post=4357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/tags?post=4357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}