gw280

Regarding memory leaks, the core Firefox codebase is fairly slim these days in terms of memory usage, and my understanding is that most of the issues people have been reporting are due to misbehaving addons. Of course, this doesn't help the user so we've been actively working on fixing that.

There's a pretty good blog post detailing the "addon problem" and the fixes we've rolled out at https://blog.mozilla.org/nnethercote/2012/07/19/firefox-15-plugs-the-add-on-leaks/

We also have an ongoing site at https://areweslimyet.com/ which tracks our memory usage.

Well there are a few reasons really:

• As Josh said, version numbers are fairly arbitrary. It's just a number. It doesn't matter if it's 15.0 or 3.14. It's just a scheme to denote what revision of a piece of software you're on.

• New features tend to be reserved for a major release, and we absolutely need to be able to release new features as and when they're ready due to the way HTML5 evolves. Thus, either we: a) increase the frequency of major version bumps, or b) allow minor version bumps to contain new features. We chose a).

• It's easier to remember what version you're on. Remembering that you're on "Firefox 15" is far easier than remembering that you're on "Firefox 5.6.3".

HTML5 is a constantly evolving standard, and so the browser needs to be able to keep having features added supporting the latest HTML5 standards incrementally instead of having to wait a year or two for the next major version to be released. The rapid release cycle deals with this issue nicely.

+1 for SC2. My life for aiur.

The unlimited snacks. Especially creme eggs at Easter.