Octane is better, though still flawed: https://blog.mozilla.org/nnethercote/2012/08/24/octane-minus....
The state of browser benchmarking isn't good. Here are my ideas on how to fix it: https://blog.mozilla.org/nnethercote/2014/06/16/a-browser-be.... The political/organizational challenges are as big or bigger than the technical challenges.
And really, you should care most about how each browser performs on the workloads you are interested in.
You can delete the word "browser" from that sentence and it's still true. Just one example: You wouldn't believe how many large projects rely on Dhrystone for benchmarking and selecting silicon.
"Real apps" using idiomatic JS should be used as benchmarks, and those apps should approximate apps in widespread deployment. For example, how fast can a reactjs re-render for a complex page run?
But GGC is mostly about reducing pause times (latency). (And yes, people have taken to calling that "jank". I still resist the term when I can, since it's no more precise than anything that came before but people seem to think it must mean something specific.)
Sunspider: 182.5ms +/- 4.6% Octane: 21148
# Chrome Sunspider: 206.7ms +/- 1.2% Octane: 24921
I adore Mozilla and use Firefox as my primary browser. As a web developer I hope those benchmarks get tighter.