View Single Post
Posts: 338 | Thanked: 496 times | Joined on Oct 2010
#33
Originally Posted by Copernicus View Post
Er, but why not? Mozilla is a group founded long ago to build a web browser, and up to this day still centered around their web browser. I would expect their code to be quite performant...



If I've got this right, UP is using "oxide" for their web engine, and oxide is based on chromium. Therefore, UP is using Google's engine for its web layout; which, again, should provide a superior browsing experience.

And, again, this is also what Qt themselves have recently done -- pretty much given up on their existing webkit engine, and gone with Chromium. If/when Jolla migrates to the more recent versions of Qt, their browser should hopefully better match Ubuntu Phone and other chromium-based systems...
You're really clutching at straws here.

Sailfish Browser is based on Gecko? Please insert your new excuse here.

If Webkit on Qt has been so abandoned and is so poor, and Gecko so great (though not as fast as Chromium), then why are the (deprecated) versions of Qt Webkit used in WebPirate & WebCat still (much) faster than the (much newer Gecko build) Sailfish Browser?

Also, UP's browser gets better results in OctaneV2 than either Chrome or Opera (Chrome based) in lightweight AOSP Android builds on the same (Nexus 5) phone ... and the UP port for N5 is a community Alpha (like the SF N5 port).

Anyway, anything that significantly loads the CPU in Sailfish tends to cause the app to hang, freeze or badly slow down long before 100% CPU utilisation is reached ... this shouldn't happen.

Last edited by bluefoot; 2015-07-17 at 14:00.