1. 16

  2. 6

    Some of the real goodies are on the Changes for Developers page. Things that will immediately fill holes are:

    1. You can now finally do forEach on nodelists. No more [].forEach.call etc.! Rewrite all the things!
    2. The console can now use sourcemaps to link to the original location of errors (and other things) in source, instead of going into the compiled scripts.
    3. You can now trace the origin of xhrs much easily, since they get stack traces. This was something missing from FF which Chrome had for a long while.

    That entire page is worth a quick read :)

    1. 4

      uh oh we just added these hot 4 features, better bump up the major version!

      1. 5

        Well, it’s not like Firefox follows SemVer.

        Firefox used to adhere to a strict 6-week train model of promoting features to release. Now they publish a 6-to-8 week schedule for the year, for the same process. It’s actually quite cool, I’d recommend checking out the first link if you’re not familiar with the train model.

        See also:

        1. 3

          Didn’t they change their model when chrome started pumping out versions like crazy? I seem to remember using FF 3 for ages and 4.0 being a big deal.

          1. 4

            Indeed they changed their model after Chrome sped up the release process. As I understand, they did it to match the rate of evolution in the web. Firefox’s release model before then was probably too long, too slow to keep up with the rate of change in Javascript APIs, etc. Hurray?

            1. 1

              Oh, I see. I was under the impression that they didn’t increase the rate of releases but just bumped the major version number up more often to make it seem like they were making more progress (like chrome).