|
|
|
|
|
by kevingadd
4452 days ago
|
|
Scroll latency has nothing to do with performance. You can achieve low scroll latency by doing scrolling and composition on a worker thread - which, IIRC, is more or less what OS X and iOS do, and is something Safari can take advantage of freely because it's not portable. If memory serves, recent builds of Firefox (on the non-release channels) are actually starting to roll out OMTC (off main thread compositing) which delivers the same sort of 'performance' you like about Safari, while keeping the perks of Firefox having a faster parser, faster JS runtime, and modern feature set. You are generally correct that latency is important, though. I don't know if the Chrome dev team prioritizes it much, but Mozilla recently started putting more effort into measuring and reducing latency in various parts of the browser (inattention had let latencies get pretty bad in some places.) Safari's fortunes aren't tied to advertising because Apple already extracted a payment for every user that runs Safari. They're free to do those things like disable cookies and bundle an ad blocker because they don't have to consider the desires of content creators or generate a revenue stream via their browser. It's the same set of tactics Microsoft was free to use with IE. It's impossible for Firefox or Chrome to offer similar features without directly undermining their revenue sources. |
|