QUOTE(super_evil_alien @ Aug 26 2010, 12:15 AM)
Still got some issues with the tabbed browsing.
Nokia is really messing with good thing.If it's not broken why fix it?Mozilla based browser is just perfect.Almost all reviewers will say is including iOS hardcore lovers.Why change it to webkit?There's already endless result that showing that webkit based browser just isn't as good.Latest prove is Blackberry OS 6.
Webkit is good in it's own way. It's lean, mean, modular and thus can be optimised for mobile devices. Gecko (the MicroB engine) renders pages very well desktop-style yes, but it's bloated (and eats RAM and CPU time) due to the fact that Mozilla had grandiose plans on making it able to DO EVERYTHING and the kitchen sink (plus the fact that it's a desktop core to begin with).
» Click to show Spoiler - click again to hide... «
Main reason why if you leave Firefox and Chrome running on your computer (with the same amount of tabs), Firefox clogs up and eats CPU cycles after a while EVEN WITH the pugged memory leaks in the latest version.
But that is a different story altogether.
Point in fact, an unmodded MicroB plain sucks on an unstable EDGE connection - it times out all the time (it's even worse on GPRS). With a modded user.js, it's not bad though. Midori/Tear - being based on webkit - is a bit better on mobile connections, a shame both apps have sucky UI that is not touch optimised.
But in the end, IT'S HOW YOU USE the code that matters, and I'm hoping the webkit monstrosity Nokia plans to drop on Meego is a good implementation of - rather than a shoddy copy of Mobile Chrome or Mobile Safari.
More details on Gecko (microB) vs Webkit (Tear/Midori/The NEW Meego Browser) here, for those who'd care to read:
» Click to show Spoiler - click again to hide... «
http://arstechnica.com/open-source/news/20...ed-to-gecko.ars http://arstechnica.com/open-source/news/20...integrators.arshttp://tech.kateva.org/2007/02/gecko-vs-we...erspective.htmlThey are old linkies, and Gecko would have matured by then but remember, MicroB's gecko engine predates the newer one used in Fennec (it's an updated version of the old N800/N810 code, which itself is an old branch of the Gecko code) - and as such the arguments above are more then relevant. Plus the fact that NITs use desktop browser code mainly.
ALSO, the normal, Symbian based Nokias all use a webkit browser, and a common pool to work with would be advantageous to Nokia R&D.
As for me? I would like to be given a choice, Nokia. I'm greedy and I want both! Preferably with the latest Flash EVEN if I plan to shut it off by default and only use it when needed.
And don't worry guys. AS SOON AS Flash 10 comes out for Meego, some enterprising coder will SURELY backport it back to Maemo 5. They're both compiled for ARM Linux anyhow, rite?
EDIT: Somehow, just to prove a point maybe, I'm suddenly made aware of the fact that my beloved UCWeb/UCBrowser has gone webkit and has turned into UCMobile - complete with l33t RAM sucking skillz (and much improved web rendering + proper javascript/flashlite support).
Man, these people need to go develop for Maemo/Meego rather than continue to stress themselves out with the limited RAM available on Nokia's Symbian phones. Although if they DO succeed, they deserve mountains of respect as even in its buggy, crash-prone form right now UCMobile kicks Opera Mobile's behind simply for being so customizable (Adaptive View FTW).
This post has been edited by Eiraku: Aug 26 2010, 03:05 AM 
Aug 25 2010, 11:00 PM
Quote
0.0311sec
0.47
6 queries
GZIP Disabled