Since Stuart landed the Qt port into mozilla-central the other day and Ryan Paul wrote an article on Qt and Mozilla I thought it might be worth it to add some context to that work.
Ryan’s article contains this quote from Nokia developer Oleg Romaxa:
“Nokia will use the best browser for the job,” he said. “Currently, we cannot make a full-featured and integrated browser with WebKit in mobile. But with Mozilla, we do not need to do anything, we can take existing models and API’s which are available. Also, NPAPI support is already in the Gecko web rendering engine. They are also concerned that WebKit is, to some extent, controlled by Apple, who are in competition to Nokia with their iPhone.”
There are a few important things to note here. First, that Mozilla is the complete package. We’ve got everything that you need to implement a browser. Disk cache, integrated (and well tested!) networking, a super-fast JS implementation, an XML UI markup language (XUL) and a brand that regular humans recognize. Those things mean you can get to market faster as a mobile integrator or developer instead of having to create them yourselves again.
Second, our neutral stance. We believe in the web over any particular platform. From Nokia’s standpoint if you’re building on the same technology that one of your major competitors is leading vs. working with someone who absolutely wants a web browser to succeed across all of Nokia’s platforms – which partner would you choose? I’ve often said “pick your partners carefully” and this has to be an important part of any technology decision making process.
There’s also another interesting flip side to this: who is WebKit’s other major competitor? Apple itself. Just like Microsoft’s push to get Silverlight out in the world, Apple wants people to write apps to their native platform. In this case, the iPhone. Given the strategic value of the native platform as part of Apple’s offerings, their investment in WebKit will (or at least should) always lag behind. We’re investing everything we have in the web and our platform and it’s starting to pay dividends.
And since I have your attention here are two other very interesting checkins: GTK+ and directfb (which people are actually building products on) and worker threads (ala Gears.)
Look at our current (and planned) platform support: win32, windows mobile, win32 + qt, mac OSX, linux + gtk2, linux + qt, qt embedded, linux + gtk2-directfb, x86, ppc, arm. We’re bringing the web to everyone and we’re doing it with a single coherent project with regular releases. That’s what I mean when I say “for everyone everwhere.” The web is bigger than any platform and we’re the embodiment of that mantra.
Mozilla is moving. It’s fast and furious now. And I think we’re just getting started.
[ Update: It was pointed out to me that what I wrote above might be misinterpreted as announcing that Nokia had picked a platform or something similar. Just to be clear that wasn't what I was doing, and as far as I know they haven't. I don't have knowledge about that decision inside of Nokia. Only they know. I was just pointing out what a decision making process might look like and the importance of picking well-aligned partners. And the fact that we're running on more and more platforms these days which is cool as hell. ]
