4 ms·
Have you actually tested this? The blog post makes it sound like this just landed. Of all the things that frustrate me about Firefox (and it is my daily driver
by eslaught 4y ago
Have you actually tested this? The blog post makes it sound like this just landed.
Of all the things that frustrate me about Firefox (and it is my daily driver), UI latency is not one of them.
- userbinator 4y agoNeither XUL nor HTML layout are native. As I understand it, they only switched from one non-native UI to another, which has pretty much the same performance implications.
- RussianCow 4y agoThere's no reason a non-native UI can't also be responsive. The two things are completely orthogonal.
- mort96 4y agoI very clearly feel the difference in latency between Chromium's UI and Firefox's UI.
- eek2121 4y agoI haven't tested this, per say, however I've noticed that Firefox is noticeably slower and buggier than Chrome or other webkit-based browsers. whether or not that is due to the parent or the engine I do not know. I still use Firefox, however, thanks to Google and Microsoft constantly pushing me to use their stuff. If Google could have stuck with Chromium/webkit/related tech being open source with no motivation, I would have never switched. As it is I still have to open up edge to get decent quality streams from Streaming sites because Firefox doesn't support the DRM used. The actual biggest gripes for me: * tabs can, and do, crash. When this happens, pots luck on whether the browser can recover or not. * NVIDIA driver updates on Windows almost always cause Firefox to stop rendering stuff prior to reboot. Edge and Chrome do not have this issue. While I can somewhat understand, Mozilla should warn users. I've updated several times across 4 NVIDIA GPUs and I've had this issue. Firefox has asked me to restore tabs exactly once. The rest of the time they were gone. * The really odd theme of the day is that hitting reload on Firefox shows signals that it is reloading, but it never does. If I duplicate the tab the site loads fine. Dev console shows no errors. Firefox is at least 10% slower on major sites like twitter, etc. vs chrome/edge, as of my last test.
- eslaught 4y agoHuh, interesting. I'm on macOS, and I don't think I've experienced any of this. My #1 gripe is that an increasing number of websites just don't work. Microsoft Teams is a big culprit, but I've had issues with medical and bank websites too. It's not Mozilla's fault that we're increasingly in a Chrome monoculture, but it sure is frustrating to live with.