Linked by Thom Holwerda on Wed 18th Aug 2010 21:03 UTC, submitted by suka
Permalink for comment 437424
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2008-01-09
Firefox can already use the cpu and if it supports OpenGL it also can use the gpu. What would you gain if you support cocoa? "
The same you do on Windows not writing it in plain C/C++ with no use of DirectX API's.
You get a whole bunch of GPU accelerated routines (with software fallbacks): you get Core Animation, you get Core Text, and you get an easier path towards 64 bit Firefox on Mac. You would also be able to use Apple's dev tools for a more productive debugging and extra performance (Clang for static analysis and compilation).
I'd also imagine it could have an easier time integrating into the OS X experience making use of they Keychain to store passwords and other sensitive data, it could use the system's spellchecker, it might open PDF's in the browser itself without external plugins, etc...
The problem with this approach is that you would have a hard time keeping the Windows and Linux C/C++ ports and the OS X Cocoa version at the same pace... not impossible, but it might be a burden for Mozilla and the OSS devs which might not like Objective-C that much.