{"id":22,"date":"2005-06-09T00:07:36","date_gmt":"2005-06-08T14:07:36","guid":{"rendered":"https:\/\/www.gedda.info\/?p=22"},"modified":"2005-06-09T00:07:36","modified_gmt":"2005-06-08T14:07:36","slug":"apple-and-sun-a-most-unlikely-duo","status":"publish","type":"post","link":"https:\/\/www.gedda.info\/?p=22","title":{"rendered":"Apple and Sun: a most unlikely duo"},"content":{"rendered":"<p>Like many who heard the <a href=\"http:\/\/www.macworld.com\/news\/2005\/06\/06\/powerpcintel\/index.php\">news<\/a> this week, I have a few opinions on what the short and long-term implications for both Apple and the industry will be as a result of Steve\u00e2\u20ac\u2122s decision. But I\u00e2\u20ac\u2122m not going to reveal them, at least not now. My immediate attention is draw to the interesting <a href=\"http:\/\/blogs.sun.com\/roller\/page\/jonathan\/20050605#an_invitation\">ambitions<\/a> of <a href=\"http:\/\/www.sun.com\">Sun Microsystems\u00e2\u20ac\u2122<\/a> President and COO <a href=\"http:\/\/blogs.sun.com\/jonathan\">Jonathan Schwartz<\/a>.<\/p>\n<p>In his open letter to Steve Jobs, Jonathan invites Apple to adopt Solaris 10 as the platform for next-generation Intel-based Macs. Although Jonathan was being quite shrewd in suggesting Apple might switch (no pun intended) to Intel on the basis of a <a href=\"http:\/\/news.com.com\/Apple+to+ditch+IBM%2C+switch+to+Intel+chips\/2100-1006_3-5731398.html?tag=nefd.lede\">rumour<\/a>, I think he\u00e2\u20ac\u2122ll sooner witness Dell ship an AMD-based box than Apple adopt Solaris, for a few good reasons.<\/p>\n<p>As Steve mentioned during the keynote, Mac OS X has been \u00e2\u20ac\u0153leading a secret double life\u00e2\u20ac\u009d for the past five years. So project \u00e2\u20ac\u02dcMarklar\u00e2\u20ac\u2122, as rumoured a number of years ago, indeed does exist. Big deal? Not really. Let\u00e2\u20ac\u2122s scratch the surface a bit to find out how easy the port would have been for Apple\u00e2\u20ac\u2122s talented software engineers.<\/p>\n<p>Even before the <a href=\"http:\/\/www.opendarwin.org\">OpenDarwin<\/a> project began three years ago, Apple released the <a href=\"http:\/\/www.opensource.apple.com\/darwinsource\/\">source code<\/a> to Darwin 1.3.1 which was the underbelly of Mac OS X 10.0 \u00e2\u20ac\u201c yes, the first release five years ago. And that version was also available as an x86 binary so anyone could download and run it on an Intel machine. With that in mind, let\u00e2\u20ac\u2122s look at Apple\u00e2\u20ac\u2122s open source stack to see which packages have not only been ported to Intel but are being <i>actively developed<\/i> on Intel (read x86)\u00e2\u20ac\u00a6<\/p>\n<p>Mach kernel \u00e2\u20ac\u201c Intel<br \/>\nBSD subsystem \u00e2\u20ac\u201c Intel<br \/>\nBash \u00e2\u20ac\u201c Intel<br \/>\nGCC \u00e2\u20ac\u201c Intel<br \/>\nGNU file utilities \u00e2\u20ac\u201c Intel<br \/>\nApache \u00e2\u20ac\u201c Intel<br \/>\nPostfix \u00e2\u20ac\u201c Intel<br \/>\nWebcore (fork of KHTML) \u00e2\u20ac\u201c Intel<br \/>\nX11 \u00e2\u20ac\u201c Intel<br \/>\nOpenGL &#8211; Intel<br \/>\nCUPS \u00e2\u20ac\u201c Intel<br \/>\nGIMP-Print \u00e2\u20ac\u201c Intel<br \/>\nMySQL \u00e2\u20ac\u201c Intel<br \/>\nSamba \u00e2\u20ac\u201c Intel<br \/>\nCyrus \u00e2\u20ac\u201c Intel<br \/>\nOpenSSH \u00e2\u20ac\u201c Intel<br \/>\nPHP \u00e2\u20ac\u201c Intel<br \/>\nPerl \u00e2\u20ac\u201c Intel<br \/>\nPython &#8211; Intel<br \/>\nJboss \u00e2\u20ac\u201c Intel<br \/>\nJabber \u00e2\u20ac\u201c Intel<br \/>\nEmacs \u00e2\u20ac\u201c Intel<br \/>\nVim \u00e2\u20ac\u201c Intel<\/p>\n<p>So there you have it, a list of \u00e2\u20ac\u02dcIntel compatible\u00e2\u20ac\u2122 software within Mac OS X. There is more \u00e2\u20ac\u201c and I hate to think of the amount of open source code hidden inside OS X\u00e2\u20ac\u2122s proprietary eye candy &#8211; but surely that\u00e2\u20ac\u2122s enough. My point being that Apple\u00e2\u20ac\u2122s \u00e2\u20ac\u02dcport\u00e2\u20ac\u2122 of OS X to Intel seems more of a case of compiling all the x86 software and then porting the GUI on top of that. But as Steve revealed both architectures are from a common code base anyway.<\/p>\n<p>What does that have to do with Solaris? Well, nothing for now and it probably never will. Why on Earth would Apple now \u00e2\u20ac\u201c after supporting two architectures with a common open source code base \u00e2\u20ac\u201c take an abrupt left turn and port all of this software to the Solaris kernel and subsystem? What would Apple gain? A bunch of high-end features that it\u00e2\u20ac\u2122s hardware doesn\u00e2\u20ac\u2122t even support?<\/p>\n<p>I\u00e2\u20ac\u2122m not sure why Jonathan would even suggest Apple should support Solaris now when it has done such a good job with BSD and GPL code. Remember, when Apple started working on OS X, x86 Solaris was proprietary and lacked the vibrant development community <a href=\"http:\/\/www.freebsd.org\">FreeBSD<\/a> has enjoyed since its inception. It\u00e2\u20ac\u2122s ironic that A-UX &#8211; Apple\u00e2\u20ac\u2122s System V-based Unix well before OS X \u00e2\u20ac\u201c was dropped in favour of a BSD code base, while Sun dropped its BSD-based SunOS in favour of System V which now underpins Solaris.<\/p>\n<p>Rather than being future collaborators, I\u00e2\u20ac\u2122d go so far as to say that Apple and Sun will become even more competitive as the <a href=\"http:\/\/www.apple.com\/xserve\/\">former<\/a> <a href=\"http:\/\/www.computerworld.com.au\/index.php?id=294629988\">begins<\/a> to <a href=\"http:\/\/www.apple.com\/xserve\/raid\/\">encroach<\/a> on the <a href=\"http:\/\/store.sun.com\">latter\u00e2\u20ac\u2122s turf<\/a>.<\/p>\n<p>By the way, I\u00e2\u20ac\u2122m glad you appreciate <a href=\"http:\/\/www.konfabulator.com\/\">innovation<\/a> Jonathan, just be wary that inventing may be closer to <a href=\"http:\/\/www.apple.com\/macosx\/features\/dashboard\/\">counterfeiting<\/a> than we are led to believe&#8230; \ud83d\ude09<\/p>\n<p>Rodney<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Like many who heard the news this week, I have a few opinions on what the short and long-term implications for both Apple and&#8230;<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,27,31],"tags":[],"class_list":["post-22","post","type-post","status-publish","format-standard","hentry","category-apple","category-open-source","category-sun"],"_links":{"self":[{"href":"https:\/\/www.gedda.info\/index.php?rest_route=\/wp\/v2\/posts\/22","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gedda.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gedda.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gedda.info\/index.php?rest_route=\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gedda.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=22"}],"version-history":[{"count":0,"href":"https:\/\/www.gedda.info\/index.php?rest_route=\/wp\/v2\/posts\/22\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.gedda.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=22"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gedda.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=22"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gedda.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=22"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}