Another advantage (IMHO) would be the momentum and drive behind WebKit. And one of the founders of Meego is a main contributor to WebKit.
On Thu, Aug 5, 2010 at 4:35 AM, Martin Sandsmark <[email protected]>wrote: > On Wed, Aug 04, 2010 at 11:18:18PM +0200, stefan hakansson wrote: > > Honestly, it is more of a guess. But my understanding is that QtWebKit > uses > > GStreamer for media, and that GStreamer is in turn using the available > > platform resources in an efficient way. In contrast (still to my > > understanding that may be wrong) browsers such as Chrome and Fennec uses > > their own media frameworks that are in a much worse position when it > comes > > to utilize platform specific capabilities. > > I would assume the biggest performance win would be from not loading yet > another dom parser, javascript interpreter (or bytecode compiler as it is), > renderers and whatnot into memory (since Qt has these already). > > (That the JS engine in QtWebKit is much faster than the one in Fennec, as > well as the hardware-accelerated rendering are just a bonus, IMHO, though I > don't think WebKit has the HW-accelerated pixmap compositing from KHTML > yet. > This is stuff that may or may not be solved in future releases of Fennec.) > > -- > Martin Sandsmark > IT-Komiteen, Samfundet > :wq > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
