Earlier quoted context omitted.
Yea, I also noticed that, save for the pages with tons of images, firefox has actually been better than chrome in that respect for the last few releases. Now with this fix, I'm seriously thinking of jumping back. Then I'll finally have my sweet DownThemAll again. Many kudos to the firefox devs, performance and memory-usage is very important, and it seems they realized that before it was too late. Even with my 16GB I'…
isn't 16GB enough to run an extra VM for dev? also, try docker.
Firefox fixes save gigabytes of memory on image-heavy pages
91–100 of 203 posts
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#92Earlier quoted context omitted.
On one hand true, on the other - it isn't that those fixes are some magic, extra smart hackery (at least on the idea level, dunno about the implementation). Don't load an image that user don't see, remove an image that user saw but don't see anymore - those seem as rather obvious solutions.
The great thing about Firefox is that if something is so obvious, you could also contribute to the development effort...
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#93Is it time to switch back to Firefox from Chrome? I remember when I originally switched around Firefox 3.5.x Chrome was much leaner and faster. Has the pendulum finally swung back the other way?
I have 4 different Chromium profiles, and two different firefox profiles, with different levels of privacy / security. Each profile is also linked to a particular context, for example, a tab each for project A, project B, personal, etc.
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#94Earlier quoted context omitted.
Yea, I also noticed that, save for the pages with tons of images, firefox has actually been better than chrome in that respect for the last few releases. Now with this fix, I'm seriously thinking of jumping back. Then I'll finally have my sweet DownThemAll again. Many kudos to the firefox devs, performance and memory-usage is very important, and it seems they realized that before it was too late. Even with my 16GB I'…
Last I tried Firefox, pretty recently, it still needed to address some serious issues, when compared to Chrome: * Unresponsiveness due to one tab thrashing * Bad use of screen-space (bookmarks always visible, cannot disappear titlebar like in Chrome [there's only a Windows extension for that], menu-bar takes up another bar of space by default) * Launching firefox has stop-the-world behavior to check/update extensions…
So, yeah, I guess you didn't really try. Perhaps you're just attached to Chrome.
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#95Re: Firefox fixes save gigabytes of memory on image-heavy pages
#96Earlier quoted context omitted.
Why should one use bookmarks rather than many tabs? I have many concurrent projects going, and things I refer to regularly, so I just leave them grouped in my tree of tabs on the sidebar. Much more efficient than digging through nested bookmark menus, or trying to make sure the bookmarks are properly classified. Basically, my tabs are bookmarks, except tabs are integrated into the web-browser better.
So, the problem is that the bookmark UI design is broken.
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#97Re: Firefox fixes save gigabytes of memory on image-heavy pages
#98Earlier quoted context omitted.
Bookmarks don't save state, which is especially annoying in a time where async calls are used so heavily.
A URL should contain all of the state needed. If it doesn't then it's a poorly designed website.
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#99Earlier quoted context omitted.
On one hand true, on the other - it isn't that those fixes are some magic, extra smart hackery (at least on the idea level, dunno about the implementation). Don't load an image that user don't see, remove an image that user saw but don't see anymore - those seem as rather obvious solutions.
The great thing about Firefox is that if something is so obvious, you could also contribute to the development effort...
Re: Firefox fixes save gigabytes of memory on image-heavy pages
#100Earlier quoted context omitted.
I never saw a reason to switch to Chrome to begin with. Performance was acceptable for me, while other benefits always made Firefox more useful (privacy with encrypted Sync, better add-ons and etc.). And some time ago, Firefox clearly became a leader in performance as well. All this "jumping to Chrome" was simply a hype thing IMHO, and I generally don't care about hype.
From a developer standpoint, the dev tools in Chrome far exceed those in Firefox. The nightly releases are just starting to compare.