Blog Entry

RSS Feed Browse

Tempest in a Teapot: Apple's "Programming Secrets"

Written by Sam Dean - Mar. 05, 2008

In case you haven't noticed, a blog post from a few days ago by developer Vladimir Vukicevic, who is working on performance enhancements for the Firefox 3 browser, has been making major waves for allegedly pointing to programming and API "secrets" that enable Apple's own applications to run more efficiently with its operating system than other applications can. InfoWorld and other tech publications have made a big deal of the post, and the hubbub made it to Slashdot. The whole thing looks like a tempest in a teapot to me.

Vukicevic's post was interpreted as pointing to some undocumented APIs that purportedly allow Apple's Safari browser to perform more efficiently than, say, any open source browser can. That interpretation then gathered steam until charges of attempts from Apple to "cripple" non-Apple software have been flying around.

Vukicevic did uncover some undocumented APIs, but an update to his post makes clear that he himself finds the coverage of his findings sensational. "To be clear, I do not think that Apple is in any way trying to purposely 'cripple' non-Apple software," he says. "I also do not think that undocumented APIs give Safari any kind of significant performance advantage. However, as I said, the undocumented functionality could be useful for Firefox and other apps to implement things in a simpler (and potentially more efficient) manner. I don't think this is malicious, it's just an unfortunate cutting of corners that is way too easy for a company that's not fully open to do."

Moreover, I can echo Vukicevic's confidence in the performance of Firefox 3. I've been steadily using the beta versions, and performance is one of the main reasons why many people will upgrade. I already find its performance perfectly competitive with Safari.

Undocumented APIs, historically, have been exploited to lend an advantage to software companies who own both an operating system and key applications, as was true in Microsoft's past. Such lack of openness can put open source applications, in particular, at a disadvantage. However, in this case, it seems clear that the allegations of intentional crippling of competitive applications are overblown.

Do you think Apple should be more open?


Comments

Add Comment
  1. By on Mar. 05, 2008

    Mac OS X is based on FreeBSD - they have built several key open source technologies into their Operating System. If they actually released Mac OS X into the wild, with their User experience and tools, I'm sure they could give the other linux vendors a run for their money, if they wanted to go up market into the servers.


    I DO feel they need to get more open, particularly since they have managed to do so well on the backs of Open Source.


    Safari is a good browser, but I think Firefox, with its openness is out-innovating Safari. If they had not prevented Firefox from being on the iphone, it would only be a matter of time before they managed to get a great experience on the iphone too (Firefox, that is).


    0 Votes
  2. By samdean on Mar. 05, 2008

    It never ceases to amaze me how many significant things are based on FreeBSD. The Mac OS is indeed, and did you know that Yahoo's entire site runs on FreeBSD? That means that if Microsoft acquires them, a large part of their infrastructure will be running on FreeBSD. Who'dathunk?


    Sam


    0 Votes
  3. By on Mar. 06, 2008

    That's right, baby. And FreeBSD is treated like the bastard child of Linux flavors...


    0 Votes
  4. By on Mar. 06, 2008

    If you had read the entire original issue, it is not an API that was in question but an SPI (or system level API).


    And while this SPI is not directly available to developers (they never are from any vendor), Apple makes it available as part of WebKit. This allows them to continue to tweak and improve these calls without breaking existing applications that rely on them. They simply update WebKit and it continues to work as a dependency for any application that makes a call to it.


    So, I ask, what exactly is the issue? Other than you spreading FUD, that is. WebKit is open source, and anyone can download the source. How is Apple not being open here?


    Sam, I think you should get all the facts and make sure you understand the process involved before you make wild & unfounded allegations.


    0 Votes
Share Your Comments

If you are a member, to have your comment attributed to you. If you are not yet a member, Join OStatic and help the Open Source community by sharing your thoughts, answering user questions and providing reviews and alternatives for projects.

Trackback URL
Please use the following URL to add a trackback to this article.
http://ostatic.com/trackback/158309