Do "undocumented" OSX tweaks give Apple apps an advantage?

Devin Coldewey

Devin Coldewey is a Seattle-based writer and photographer. He has written for the TechCrunch network since 2007. Some posts he’d like you to read: The Dangers of Externalizing Knowledge | Generation i | Surveillant Society | Choose Two | Frame Wars | The User’s Manifesto | Our Great Sin His personal website is coldewey.cc. → Learn More

Friday, February 29th, 2008

20080228-timing.png

Vladimir, one of the coders working on Firefox 3, was having some trouble overcoming a few performance issues in the builds. He did a little investigation, resulting in the chart above and others, and found that Firefox’s display rate appeared to be being throttled by the OS for no particular reason. The problem didn’t affect Safari, and it wasn’t until he dug deep into Webkit’s coding crevasses that he found the solution: a set of special instructions and shortcuts so poorly documented that they may as well be secret. He worked some in (just a few lines) and Firefox exploded out of the gate.

Vlad doesn’t think this code was hidden maliciously, but it seems at least to be a little negligent on Apple’s part to bury these so deep. Of course, I’m not a coder and I don’t know what I’m talking about.

Finding the OSX Turbo Button

blog comments powered by Disqus