3 ms·
If you’re on iOS, Apple gates Firefox from using JIT JS compilation which massively hinders performance. E: I was wrong/extremely out-of-date - it does have JI
by wswope 3y ago
If you’re on iOS, Apple gates Firefox from using JIT JS compilation which massively hinders performance.
E: I was wrong/extremely out-of-date - it does have JIT but relies on the Safari/Webkit implementation. In ancient versions of iOS, the WebView widget that third-party browsers were forced to use had JIT disabled, but that’s long since changed.
- ornornor 3y agoFor this benchmark I get 12.0 in FF and 13.9 on safari. I’m glad it’s not so big of a gap as I already pay a penalty for not wanting to use safari on iOS (in terms of integration with iOS and usability from Apple’s artificial limitations on third party browsers)
- capitainenemo 3y agoIt's more than that right? They have to use all of webkit. So it's pretty much a reskinned Safari in terms of layout/rendering/JS.
- om2 3y agoThat’s not accurate. Firefox and all third party WebKit apps get the same JOT as Safari.
- capitainenemo 3y agoRight, but expecting the same behaviour from "Firefox" on iOS as on desktop is just not going to happen, since they have no control over the core engine. It's why, in general using iOS devices for cross-browser testing is pretty useless.
- om2 3y agoThis is a fair point, though it is possible for app-level things that the browsers do to regress performance from the baseline pure engine level. In this case, I think the 3 score must be either very old/low-end Android hardware or a measurement error. I don’t think any iOS browser gets 3.x scores, on even remotely modern hardware.