3 ms·
Tried it again last week. Still slow, I'm afraid, despite Mozilla literally inventing a new kind of programming language to speed it up! A lot of it has to do
by andai 6y ago
Tried it again last week. Still slow, I'm afraid, despite Mozilla literally inventing a new kind of programming language to speed it up!
A lot of it has to do with design, though. ie. when opening a new window, Chrome draws the window instantly and then fills in the UI, while Firefox waits until the window is completely built to display it. Even though they become usable at roughly the same time, Chrome responds instantly to the command while Firefox exhibits zero sign of life for hundreds of milliseconds.
- onli 6y agoEvery new windows FF can open opens immediately on my system. What kind of window are you opening there?
- andai 6y agoCtrl+N. New browser window. This is true across computers and across operating systems.
- onli 6y agoDefinitely not true on my system. There is a flash of some reorganization of the windows content that Chromium does not do, but both windows open instantly. And also: Come on, that wouldn't make a browser slow. Users open new windows once when starting the browser. The rest is about how fast they render pages, react to JS workloads, and maybe how fast they open tabs. FF is more than on par in all of this.
- andai 6y agoI open new windows constantly. Opening the actual browser though is a whole other story, where the difference is even more striking. Curious what you said about FF reorganizing the window contents, in my experience Chrome does that and not FF. It's true JS performance is quite similar. But I've noticed (measured) differences in page load speed as well -- including latency again, the time until it actually responds to the enter key and initiates a network request. (In the network panel this is reported as Stalled.)