Note however that Firefox was safer even before they introduced their permissions system simply by having a review system that works. But as it is right now, I can't tolerate such lag, for a trivial action I perform thousands of times a day.įirefox does support media keys, but it's experimental and you have to enable them in about:config: But I have been disappointed on this front every single time. I switch back to Firefox roughly once a year after reading how fast it's gotten. From a user experience (I do command, I expect feedback) this makes a huge difference. But Firefox waits until the whole window is built before it displays it, while Chrome opens the window immediately and fills it in. This seems to be another 10-20x difference (though I'd have to record my screen and measure the difference).Ĭuriously, Re: UI lag, I think the actual time until the navbar is usable is about the same. With Firefox it takes about 0.5-1 seconds before anything happens at all. I cannot even perceive the delay between pressing Ctrl+N and a new window appearing. Chrome and Chromium based browsers do that. When I press Ctrl+N, I expect a new window to open immediately. On Chrome the block is 3-18ms (15-50x (!!) faster). Network inspector says Firefox is spending 150-270ms "blocked" before it even initiates the connection. 1.5 to 2x slower - and that's after all the performance upgrades they've done with Rust and Quantum.
Just tested with a "hello world" page (18ms ping).Ĭhrome takes 102-200ms to render the page, Firefox takes 150-400ms.
0 kommentar(er)
