“The notion of a Firefox smartphone browser seemed implausible only a few short years ago, but today it’s very much a reality. Firefox Mobile for Maemo demonstrates the flexibility of the Firefox Web browser and its potential to bring a desktop-like browsing experience to constrained computing environments. It is truly an impressive achievement, but it’s only the beginning of what Mozilla hopes to accomplish on handheld devices. Stay tuned for our follow-up about Weave, in which we will examine some of the opportunities for innovation created by Firefox Mobile.”
AFAIK The BIG MAJOR advantage that Mozilla has over other engines is that it can do REAL ADBLOCKING.
While webkit based browsers always download everything and then filter (all ads etc) Firefox adblock disregards A LOT of stuff and doesn’t even download most of junk ad stuff nobody wants and that makes websites load much faster over slow mobile data connections.
The future is very bright for Firefox!
it is faster than Firefox, has flash enabled by default and I think it is still more intuitive to use.
But Firefox has weave, so every time I am on the go I use Firefox instead of MicroB. Weave is just so damn handy.
It is a tough choice now but N900 is no short of good browsers
What a good dilemma Nokia has on its hands now. And in a few weeks Qt4.6 with webkit engine.;)
Maemo, ah yes – the OS platform that Nokia like to break ABI compatibility on every year or so (and therefore GUI based apps don’r work or barely work between major versions), and pretty much obsoletes your device every 18 months (N770, then N800 and then N810.) You’ll forgive me if I pass on this one.
But AFAIK there are incompatibilities between major versions even on Windows Mobile platform. So it is expected, isn’t it?
How is this different from most other mobile platforms?
Huh? Both N800 and n810 received the update to “Diablo” (OS2008).
Symbian did this too – all apps were incompatible between major versions. So in mobile world this often happens. Anyway, in mobile world you don’t have so much resources, to bloat with “legacy” support, like Windows for example. You must cut what is old or not used.
I’d really like to see this on my Android device (Samsung Galaxy). I’ve tried a couple of browsers on it so far, but haven’t found the perfect solution yet. Plus the Android platform seems so much more promising compared to Maemo (if you put Google’s “Big Brother” attitude aside, at least), now that it’s being used on more and more devices.
You seem to be confusing “promising” with “popular”.
Android is a big Java sandbox, while Maemo is a Debian based Linux platform, built on open technologies throughout the stack. To each his own, I guess…
Edited 2010-02-03 20:58 UTC