Firefox goes for lucky number 13.
Mozilla continues its torrid pace of releasing new versions of Firefox. Not scheduled for release until tomorrow, what appears to be a final version of Firefox 13 has appeared online.
New features and changes include:
- When opening a new tab, users are now presented with their most visited pages
- The default home page now has quicker access to bookmarks, history, settings, and more
- SPDY protocol now enabled by default for faster browsing on supported sites
- Restored background tabs are not loaded by default for faster startup
- Smooth scrolling is now enabled by default
See the full release notes for more.
Grab the download for your platform: Windows, Mac, and Linux
Ha, but I thought it was a new version every other day (sarcasm)
Smooth scrolling is now enabled by default
WTF. Who decided on this crap?
At the top of the comments, click the blue text link that says "Read comments on the forums", scroll down to your comment, and there is an edit button. This is not true for tomsguide.com articles, but it is true for tomshardware.com articles.
Also, here's a link to it right here:
http://www.tomshardware.com/forum/15881-55-firefox-online-early-download
Smooth scrolling is now enabled by default
WTF. Who decided on this crap?
... Do you want a faster browser or not? Not having every page load until you are using it speeds things up. Chrome does something similar.
Chrome max tabs on low end machines with 2GB or less: A few dozen, maybe a little more. FF max tabs on such machines: Hundreds, perhaps thousands. Not everyone uses so many, but FF is one of the few browsers (only major browser globally) that can do it without huge memory imprints. Individual processes for tabs is a huge part of why Chrome uses so much memory in comparison. There are trade-offs to consider to each approach. Regardless, FF could add multi-threading support without having each tab in its own process. Also, Chrome doesn't always have a process for every tab. Grouped tabs often share a process.
FF is also usually more stable than Chrome right now (I've had several crashes that forced me to restart Chrome, but I've yet to have such happen to my FF in a long time) and stability can be more important than speed. Besides, it's not like FF is slow anyway, especially with No-script, adblock, fasterfox, etc. They take only a few seconds to install and you're good to go after a few minutes spent setting them up if their defaults aren't as good as you want them to be.
there isn't another way to support multi-threading without creating another process (for another cpu), with it's own memory space, and so on... the same goes for the other tabs. Every one of them needs to be another process in order to take advantage of a second (or more) cpus, otherwise, only one cpu will being multi-tasking in between threads in the same process.. and for example, if one of them makes an IO operation, the hole process will wait for the IO operation to get done before continuing.. this translates to FF frozen till IO operation finishes.. (no tab switching, no animation at all, totally freezed)
Chrome uses sandboxes to isolate the memory between tabs (it's more secure) and that's not free in terms of memory
Actually, FF could be multi-threaded without having each tab (or tab group) as an independent process. It would simply take more work and wouldn't have the advantage of Chrome's tab/tab group sandboxing, but it would have the advantage of using less memory. It's all trade offs about what we are willing to give up for what gain.
there is working link, when you click to download current version, just in the link replace 12.0 with 13.0 and you will start downloading the new version
Here is the link: