Linked by tessmonsta on Sat 20th Mar 2010 11:15 UTC
Permalink for comment 414540
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2006-01-19
Christian Packman is to credit for the fast scaled bitmap rendering. He wrote assembly code versions of the scaling routines I wrote. The Chrome rendering has excellent down-scaling. The Haiku app_server downscaling only looks good above a factor of 0.5. But I don't believe proper downscaling is the main reason for Chrome's slowness. Firefox on Windows should also be faster, but Chrome on Windows appears as slow as the Linux version. But the WebKit guys are already working on hardware accelerated compositing from what I understand of the codebase so they should soon catch up to IE9 in rendering speed. And of course Chrome is much faster in other respects -- network caching, faster Javascript and multi-threading contribute to an overall much snappier experience. Eventually, we should be able to have all that enabled in WebPositive as well.