{"id":1616,"date":"2007-06-18T11:54:58","date_gmt":"2007-06-18T14:54:58","guid":{"rendered":"http:\/\/brockerhoff.net\/bb\/viewtopic.php?p=2152"},"modified":"2010-05-08T17:41:04","modified_gmt":"2010-05-08T20:41:04","slug":"re-the-64-bit-sky-is-falling","status":"publish","type":"post","link":"https:\/\/brockerhoff.net\/blog\/2007\/06\/18\/re-the-64-bit-sky-is-falling\/","title":{"rendered":"Re: The 64-bit sky is falling!"},"content":{"rendered":"

OK, here’s what I wrote a few days ago, regarding the Mac OS X transition to Intel:
\nRainer Brockerhoff wrote:<\/strong><\/p>\n

…Most Cocoa developers that didn’t call Carbon frameworks to any great extent, or that didn’t have to deal with complex binary files, were able to recompile their apps into the Universal (“fat binary”) format in a few hours or days. In contrast, most developers of Carbon apps of any complexity faced months or years of conversion.<\/p><\/blockquote>\n

I invited comments on Apple’s carbon-dev<\/a> mailing list, and some people objected to the paragraph quoted above. In particular, Apple engineer Eric Albert wrote<\/a>:<\/p>\n

I’d probably moved more Mac OS X code to Intel than anyone else before the announcement — some of the iApps and a bunch of other apps, plus a ton of work in the OS — and of the code I’d worked on, the Cocoa apps happened to take more work than the Carbon ones. That was really nothing more than coincidence because the Carbon apps I was working on dealt with structured data better than the Cocoa ones, but there’s nothing inherently more complex about the Intel transition for Carbon than there is for Cocoa. Mathematica, which is most assuredly a complex Carbon app, took four hours to get up and running on Intel, faster than any other app I’ve seen.<\/p>\n

The primary reason for some Carbon apps taking a long time to move to Intel was that they weren’t using Mach-O or Xcode at the time the transition was announced and both were required for Intel support.<\/p>\n

Carbon apps already using Mach-O and Xcode came over to Intel fairly easily.<\/p><\/blockquote>\n

Well, that’s quite definite; I was wrong there. I was wondering why, though, and here’s what I found: the RDF<\/a> is to blame… \"icon_wink.gif\"<\/p>\n

Here’s what Steve Jobs said<\/a> at the WWDC 2005 keynote, where I was physically present, and quite near the front too:<\/p>\n

So, let’s take a look at this again: Widgets, Scripts and Java just work. Cocoa apps, literally a few days and your Cocoa app’s going to be running with an Intel version. Carbon apps, it’s to be a few weeks, a few more tweaks, although there are exceptions to that although we maybe overstating it here, which we’ll see in a minute. And and in Metrowerks we don’t know, you’ve got to get to Xcode. So the key here is getting to Xcode.<\/p><\/blockquote>\n

And I distinctly remember the same point being made later in the reserved “state of the union” sessions: click a checkbox in Xcode, “boom” for Cocoa… not that easy with Carbon.<\/p>\n

There it is then. I don’t have any Carbon apps myself, and didn’t have to migrate anything from Metrowerks CodeWarrior either, so I thought Carbon was to blame for stuff like the Adobe Photoshop delay. I’ll update my original post below; thanks to everybody who sent in comments.<\/p>\n","protected":false},"excerpt":{"rendered":"

OK, here’s what I wrote a few days ago, regarding the Mac OS X transition to Intel: Rainer Brockerhoff wrote: …Most Cocoa developers that didn’t call Carbon frameworks to any great extent, or that didn’t have to deal with complex binary files, were able to recompile their apps into the Universal (“fat binary”) format in […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[4,19],"tags":[26,23,21,22],"class_list":["post-1616","post","type-post","status-publish","format-standard","hentry","category-dev","category-software","tag-cocoa","tag-mac","tag-wwdc","tag-xcode"],"featured_image_src":null,"author_info":{"display_name":"Rainer Brockerhoff","author_link":"https:\/\/brockerhoff.net\/blog\/author\/rbrockerhoff\/"},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1q3Zc-q4","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/posts\/1616","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/comments?post=1616"}],"version-history":[{"count":0,"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/posts\/1616\/revisions"}],"wp:attachment":[{"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/media?parent=1616"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/categories?post=1616"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/brockerhoff.net\/blog\/wp-json\/wp\/v2\/tags?post=1616"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}