14
msdsk
63d

Okay, this is MAJOR FUCKING BULLSHIT.
I understand variability of, dunno, 10, but 40?
The tests were ran on the same machine, one after another. What the fuck?

Comments
  • 7
    Because Firefox uses their own JS & DOM engines, which are significantly bloatier than V8 & WebKit. Since Firefox takes way longer to implement new APIs and features, it may also require some polyfills, which are often several times slower than native implementations.
  • 1
    It might not be that worse, It waits till the page becomes completely stable, your page can be usable much before that.
  • 1
    Make sure that you use a sandboxed browser for each run. I would still expect Firefox to be a little worse on bleeding edge stuff.
  • 8
    No wonder Chrome performs better. Google basically owns W3C and W3C dictates web standards. Other browsers will always be behind...
  • 7
    @lamka02sk
    To some extent the W3C has always been that. The advisory board represents the original status quo, it is by design a standards org for getting deep pocketed companies to agree with each other by proxy.

    Also don't forget that google funds a large majority of Mozilla's operating capital via a search revenue agreement. Any antitrust action against google, kills Mozilla. They're also still Novell, the company that made people pay for a browser until Microsoft made a free one.

    Everything is big corporations. None of them care about you, standards, quality of life, equality, the future the children or people. It's all about money. #BandAid #Ripped
  • 0
    Did you do those tests on browser sessions with only those tabs and no extensions?

    If not, then that's a part of your problem.
  • 1
    @lamka02sk That's not really how it is. Mozilla still has a considerable say in W3C. Unlike Google, however, Mozilla has one community working on things like W3C specs, and a completely separated community of people actually implementing them. Mozilla also has the third community of people who come up with ideas for new functionalities to be added to W3C standards. These communities have only a small overlap, and a good portion of people there are volunteers. So by the time Google implements their 3rd working draft in Chrome and makes a polyfill, Mozilla can't even find the original author of the idea or most of the people who initially contributed to it, let alone dedicating a few developers to research potential implementation and trade-offs of those proposals.
  • 0
    Make sure your Firefox is fully updated. It improved a LOT recently.
  • 0
    @SortOfTested once you get past the capitalist/communist labels, and just list values, you'll find we may not agree on everything, but theres a lot that we do.

    sweet abrahams ballsack, im starting to sound like a third positionist.
Add Comment