5 ms·

Isn't this what extensions are for? When is Mozilla going to channel its resources into building a JavaScript engine that can keep up with Chrome's so that the

Isn't this what extensions are for? When is Mozilla going to channel its resources into building a JavaScript engine that can keep up with Chrome's so that the web is actually usable in FF again?

qwertyuiop924 10y ago
actually, on 64-bit, IonMonkey is within 100 milliseconds of V8 either direction. With backtracking, it's within quite a lot less than that most of the time. On some benchmarks, it's even faster than V8. Source: https://arewefastyet.com/overview/#/machine/29 https://arewefastyet.com/overview/#/machine/29
- cauterized 10y ago
  Well, I guess it's time to get better benchmarks. Because FF regularly beachballs for me on web apps Safari and Chrome don't even blink at.
  - qwertyuiop924 10y ago
    ...Some webapps just flat-out won't consistantly run on FF. Given that FF is fully standards compliant, some of both of these problems could be attributed to shoddy web developers. Then again, FF could be at fault. I don't really know in this case.
    - bzbarsky 10y ago
      "fully standards compliant" is definitely overselling it. Firefox aims for that, but doesn't always succeed. (Disclaimer: I work on standards support in Firefox, among other things.)
      - qwertyuiop924 10y ago
        Fair 'nuff. I'm more on the user side of the browser equation, so you would know. But you do have pretty good standards compliance, last I checked.
        bzbarsky 10y ago
        Sure. We do try. :)
  - bzbarsky 10y ago
    Have you filed bugs on Mozilla for those? There's more than a JS engine to a web app; you could be running into layout or style system issues just as easily... But the important part is that we can't fix performance issues we don't know about, so please report performance issues if you encounter them!
- buster 10y ago
  I must say i was a Chrome user for the past years and changed back to Firefox for approx. 6 months now. Aurora and Stable. But after thinking that i can cope with a little bit of sluggishness and slowness it's just too much of a difference in responsiveness overall. Chrome starts much faster, tabs open much faster, tab switching is faster. In Chrome it is _instant_. In Firefox it is fast but it's noticeable to the point where it distracts from fast keypresses. Sometimes i am pressing keys faster then Firefox is ready to accept and Firefox misses keys. Yes, firefox is fast but it's not yet right where Chrome is. Today, i tested the experimental features but in the end, i switched back to Chrome. I just hope Servo will be great and wait. Until then, i am running Chrome again. P.S.: I've used FF and Chrome on Windows and Linux, and on both OS, Chrome beats Firefox in UI responsiveness.
  - qwertyuiop924 10y ago
    I wasn't talking about UI. I was talking about JS engine speed. UI speed, yeah, Chrome beats FF by a country mile.
fzzzy 10y ago
Every Test Pilot experiment is an extension.
deleted 10y ago
[deleted]

Isn't this what extensions are for? When is Mozilla going to channel its resources into building a JavaScript engine that can keep up with Chrome's so that the web is actually usable in FF again?

qwertyuiop924 10y ago

actually, on 64-bit, IonMonkey is within 100 milliseconds of V8 either direction. With backtracking, it's within quite a lot less than that most of the time. On some benchmarks, it's even faster than V8. Source: https://arewefastyet.com/overview/#/machine/29 https://arewefastyet.com/overview/#/machine/29

cauterized 10y ago
Well, I guess it's time to get better benchmarks. Because FF regularly beachballs for me on web apps Safari and Chrome don't even blink at.
- qwertyuiop924 10y ago
  ...Some webapps just flat-out won't consistantly run on FF. Given that FF is fully standards compliant, some of both of these problems could be attributed to shoddy web developers. Then again, FF could be at fault. I don't really know in this case.
  - bzbarsky 10y ago
    "fully standards compliant" is definitely overselling it. Firefox aims for that, but doesn't always succeed. (Disclaimer: I work on standards support in Firefox, among other things.)
    - qwertyuiop924 10y ago
      Fair 'nuff. I'm more on the user side of the browser equation, so you would know. But you do have pretty good standards compliance, last I checked.
      - bzbarsky 10y ago
        Sure. We do try. :)
- bzbarsky 10y ago
  Have you filed bugs on Mozilla for those? There's more than a JS engine to a web app; you could be running into layout or style system issues just as easily... But the important part is that we can't fix performance issues we don't know about, so please report performance issues if you encounter them!
buster 10y ago
I must say i was a Chrome user for the past years and changed back to Firefox for approx. 6 months now. Aurora and Stable. But after thinking that i can cope with a little bit of sluggishness and slowness it's just too much of a difference in responsiveness overall. Chrome starts much faster, tabs open much faster, tab switching is faster. In Chrome it is _instant_. In Firefox it is fast but it's noticeable to the point where it distracts from fast keypresses. Sometimes i am pressing keys faster then Firefox is ready to accept and Firefox misses keys. Yes, firefox is fast but it's not yet right where Chrome is. Today, i tested the experimental features but in the end, i switched back to Chrome. I just hope Servo will be great and wait. Until then, i am running Chrome again. P.S.: I've used FF and Chrome on Windows and Linux, and on both OS, Chrome beats Firefox in UI responsiveness.
- qwertyuiop924 10y ago
  I wasn't talking about UI. I was talking about JS engine speed. UI speed, yeah, Chrome beats FF by a country mile.

fzzzy 10y ago

Every Test Pilot experiment is an extension.

deleted 10y ago

[deleted]