3 ms·
I switched from FF -> Chrome some years ago. Sometimes I try to switch back. Maybe FF is fast.. but it feels clunky, I wish they would copy Chromes GUI right of
by ippa 13y ago
I switched from FF -> Chrome some years ago. Sometimes I try to switch back. Maybe FF is fast.. but it feels clunky, I wish they would copy Chromes GUI right off :). Also the "screen" flickers when I scroll, in Chrome it doesn't. And that's on a high-end windows PC.
I like what Mozilla is doing with regards to privacy and so on though...
- webwanderings 13y agoThanks for confirming about the screen scrolling. I thought I was the only one.
- callahad 13y agoFirefox's UI is heading generally in this direction: https://wiki.mozilla.org/images/0/0c/Australis-i02-Tabs.jpg https://wiki.mozilla.org/images/0/0c/Australis-i02-Tabs.jpg Try out a UX Nightly http://people.mozilla.org/~jwein/ux-nightly/ http://people.mozilla.org/~jwein/ux-nightly/ to get a feel for the work-in-progress version.
- magic_haze 13y agoTry FxChrome: https://addons.mozilla.org/en-US/firefox/addon/fxchrome https://addons.mozilla.org/en-US/firefox/addon/fxchrome I switched from Chrome a few weeks back and had the same opinion about firefox's native UI. FxChrome and Close-Tabs-to-the-Right [https://addons.mozilla.org/en-US/firefox/addon/close-tabs-to-the-right https://addons.mozilla.org/en-US/firefox/addon/close-tabs-to...] made the switch completely worth it. Edit: I noticed a difference in the default scrolling as well. Try disabling smooth scrolling (Options -> Advanced -> General.)
- padenot 13y agoJust wanted to note that a close-tabs-to-the-right menu entry was recently added in Nightly builds.
- sp332 13y agoFirefox downloads image data but doesn't decode it until you browse to that spot on the page. Do you think that's what you're seeing? You can disable that in about:config, just toggle image.mem.decodeondraw to false.
- agumonkey 13y agoChrome devs got the `snap` right. It is 99% instantaneous, it's beating any of my extremist~ expectations impressively. Sometimes, though, it gets stuck in async hell. And with lots of tabs it loses some responsiveness (on my old core duo). Firefox is slower but regular, I'm abusing it with dozens of tabs and it stays stable. All in all, I can't applaud Mozilla enough for pulling prolongated and difficult efforts (the new 3-layered releases process, memory compaction, js jit) with only a tiny percent of Chrome's ressources. This is really impressive.