Slashdot Mirror
Mozilla's New Logo Reminds Us that It Is, In Fact, a Web Firm (cnet.com)
Mozilla has a new logo. The company has ditched the world "ill" from the name with a colon and two slashes. From a report: Last year, Mozilla, the internet company best known for the Firefox browser, publicly started the rebranding process by opening the door to public feedback. With several options on display, Mozilla asked for comments and input from all who cared to share. As of today, the new logo is official and the simple change is meant as a reminder that Mozilla is more than just a browser.
Dear Mozilla: Too much navel-gazing, and not enough good software engineering and innovation.
I realized that Mozilla was no longer focused on software when they used donors' money, not to fix bugs and add features, but to sponsor a surfing competition in Hawaii.
My brain parses "://" as gibberish and reads that logo as "moz a".
Circumcision is child abuse.
It's in my list of things I do immediately after installing Firefox to make it usable:
1. restore title bar and menu bar
2. do not close window when closing last tab
3. do not hide http url prefix
Circumcision is child abuse.
Having done a lot of source comparisons between Firefox and PaleMoon (and especially PaleMoon v26 and v27), it appears that these are not memory leaks, but bad caching policy. Firefox seems to want to cache things indefinitely even if the resources are not needed anymore, but it does not actually "leak" them. I'm still trying to track down how Firefox's automatic management settings work, because this stuff is not controlled with user settings (anything that can be set in user.js).
For a long time I've insisted that if you close all windows and point the last window to about:blank, the browser will still hang on to over a gig of memory. If you do cycle collects and minimize memory usage, the browser still won't release memory. However, if you do a lot of bizarre stuff to flush out the browser history, like open dozens of blank pages and do lots of Backs and Forwards, eventually the browser can be coaxed into clearing caches and you can then cycle collect to get memory usage below 300MB again. The memory does release correctly when it has to. The browser is just designed to use a max, fixed amount of memory, as a percentage of how much RAM you have in your computer. My last tests were with Firefox 47, and on my 16GB Win7 x64 system, that fixed amount appears to be exactly 1.6GB. Firefox 50 uses less memory than 47, but I haven't tested what the max limit is, yet.
The browser is simply trying too hard to be fast by caching the hell out of everything it doesn't need to -- mostly in the Javascript runtime and heap. I have no doubts this can be easily fixed by tweaking some settings, and not rewriting code. Mozilla just absolutely refuses to do this.