If they did finally solve this, I might be nearly back to using FF as a primary. With Chrome I have had more and more problems with certain sites (not all legacy either) the last few months. Also, I've been impressed with the improvements in speed and reliability of Firefox in the last couple of releases. Everyone remembers the days of 15 second FF startup because you had a handful of add-ons turned on.<p>Now, I've gained some discipline and stopped installing 50K plugins, but Firefox has done the heavy lifting here. On FF 15 I only have a small amount of plugins (partially because I abandoned its usage) but on my work Mac, it goes from shutdown to usable in 685ms.<p>If anyone you know is delusional enough to think that competition doesn't improve products, just point to FF. The existence and popularity of Chrome has turned FF from a decrepit bloatware to a sleek modern web racehorse. I'm proud of those guys because in all honesty, I was convinced they would fail. Kudos.
I applaud the Mozilla team for its huge effort in squashing the FF memory leaks. That must have been such a huge pain to solve and it took many years. Well done and congrats.<p>That said, I really hope the authors of plugins like Firebug, Adblock Plus, and LastPass among many others will do their parts to get rid of bad memory leaks.<p>Using OSX 10.7.4, I opened up FF 14.1 to about 325MB-350MB of memory. After downloading FF 15 and restarting, I saw no change in my memory consumption. Once I disabled the three I mentioned above, I was only then able to start FF around 250MB, still really high but better.<p>I want Mozilla and Firefox to succeed as I really want there to be solid competition for Chrome. Please, add-on authors, do your parts too!
Unfortunately I'm still sticking with Chrome. I love Firefox but Chrome loads "instantly" while Firefox: even 15 still has a noticeable lag when you launch it.<p>Firefox has always felt very unresponsive in terms of the UI and loading times. The only browser I've found less responsive is Safari (IE, is very responsive).<p>Memory consumption was an issue at one stage in Firefox's history but they mostly fixed that (from 1 GB/usage down to like 200 MB~ after a day of browsing).
Here's some detailed information about the addon leak fix from the developer who fixed it: <a href="http://blog.kylehuey.com/post/21892343371/fixing-the-memory-leak" rel="nofollow">http://blog.kylehuey.com/post/21892343371/fixing-the-memory-...</a>
Unfortunately I got addicted to pentadactyl after a couple of threads here. Which broke on 15 and made me go back from beta to stable.<p>I wonder what changed internally to lead to irc comments that in effect said 'it's a major undertaking to make pentadactyl work for this new version' and this commit: <a href="http://code.google.com/p/dactyl/source/detail?r=2557fa60103046ebfeaee1eb4f3e1377cdd6366f" rel="nofollow">http://code.google.com/p/dactyl/source/detail?r=2557fa601030...</a><p>Really don't want to miss that addon anymore.
How many releases of firefox have we had now that claim to have fixed its memory problems? I make this at least four, which is a few too many for me to believe it this time.
> a completely silent background updater<p>This is not an improvement. I do not like it when my computer changes itself without asking.<p>- Does no one question this anymore?
- Why should we blindly accept every single update unquestioningly?
- Why should we be forced to deal with the problems they introduce after the fact?
- Why will no one contemplate that constant automatic updates are an attack vector unto themselves?<p>The more you force your feedlot of end-user livestock to tolerate potentially disruptive updates, the more they will grow accustomed to not being in control of their own machines, and the less likely they will be to notice a real problem as a signal amidst all the noise. Honestly, why even bother pretending to have control of our machines anymore.<p>When people ask me for help now, my eyes glaze over, and I am often forced to respond "I don't know what the fuck that thing is doing. It clearly has a mind of it's own."<p>This, my friends, is an affront to the very sensibility of the control an "open source" project, should ostensibly extend to it's community and user base. And spare me your bullshit about "Oh, hay guyz, you can just go on GIT or SVN and look at the code yourself!"<p>It's time-consuming, technical, and inaccessible to normal people, never mind the complications of different platforms, and the shifting sands of dependencies, commits and continuous integration.<p>YOU KIDS STAY OFF MY LAWN!<p>/rant
Mouse lock support for FPS games is really exciting for me. I've wanted to make first-person WebGL games, but before this was available it simply wasn't feasible.
The WebGl demo video is impressive though. Not just the execution, but the fact that this isnt made specificlly for webgl.<p>Its c++ code compiled to Javascript. This seems to suggest PS2/Wii era games can easily be ported to fully native fully crosplatform html5 applications.<p>I do wonder about security. The videocard drivers are not hardened against abuse: yet they live completely outside of any sandbox. And WebGL is just passing these OpenGL commandos unfiltered to the drivers.<p>Good news for Intel, with their open driver stack. And bad news for NVidea and ATI with their messy legacy drivers and firmware full of unchecked liscenced closed-source 3rd party code.
Does anyone know how these "silent updates" handle add-on compatibility? I prefer being "hassled" by update notifications if an update is going to break my favorite add-ons.
There has been some talk about ubuntu here-- what is the best way to keep up to date with browsers on ubuntu (/linux).. there is no 'check for updates' within firefox, and the repositories are often out of date [1]<p>1. to be fair, i don't know about FF, i can't really complain that it might be a day out of date.. but chromium is way behind. Also what about living on the beta/aurora channels?
Also 16b1 and 17a2 coming out sometime tomorrow.<p>October 9th: Firefox 16 desktop/mobile, 17b1, 18a2<p>November 20th: Firefox 17 desktop/mobile, 18b1, 19a2<p>Schedule pace seems insane but getting used to it and I'm fine with the way it doesn't seem to break anything.<p>Firefox 99 in 2017?
<a href="http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/15.0/mac/en-US/Firefox%2015.0.dmg" rel="nofollow">http://download.cdn.mozilla.net/pub/mozilla.org/firefox/rele...</a><p><a href="http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/15.0/win32/en-US/Firefox%20Setup%2015.0.exe" rel="nofollow">http://download.cdn.mozilla.net/pub/mozilla.org/firefox/rele...</a><p>Direct links to the OS X version and win32 version.
If Firefox really have fixed the issues with memory leaking, I might go back to using it more again. I was one of those developers that switched over to Chrome like the majority, I have a feeling for some it's a little too late for Firefox to be fixing an issue that has plagued the browser since around version 1.5.<p>I still recall years ago Mozilla even denying that there was a memory leak and were always quick to blame plugins for the leaks and while that's true in some instances to an extent, Chrome showed us that bad plugins can be managed correctly and not break your browser performance.<p>Giving it a shot now, Firefox can't afford to blow this again.
Just for the record: Old people don't like changes, so when Firefox silently changes and updates the wording of a menu, or changes the new tab behavior, etc., my 70 year old dad bitches and calls me to find out what is wrong with his computer.<p>Silent updates: only for bugfixes. Sure would be nice if version numbers meant anything these days.
I don't like to use Chrome. Updates for IE are not available because I am still on XP. Safari is also not updating itself for Windows.<p>So what are the options left any more?<p>It seems things are getting pathetic in the browser market.