10 ms·

And just like that, Safari has surpassed Chrome in interop 2022 https://wpt.fyi/interop-2022 https://wpt.fyi/interop-2022

by culi 5y ago

alwillis 5y ago
The experimental numbers haven’t changed since Interop 2022 was announced. That is, there hasn’t been a new version of Safari Technology Preview, which is what the experimental numbers are based on.
- culi 5y ago
  Woops you're right. This was premature. But once 15.4 has been released it'll have surpassed Chrome in the stable release as well.
_-david-_ 5y ago
Click stable. Safari is nowhere close.
- gsnedders 5y ago
  That'll still be Safari 15.1, alas; 15.4 should be close to the experimental score shown.
  - jtbayly 5y ago
    Why haven't the stable versions 15.2 and 15.3 been tested? Will 15.4 be tested?
    - gsnedders 5y ago
      Uh, it's 15.3 that's being run, I just can't write the right number it turns out. (I honestly have no idea why I said 15.1!) 15.4 should show up in day or two, there's a bunch of latency in how those metrics are generated currently…
inopinatus 5y ago
Webkit is not committed to fully implementing the HTML Living Standard, or more precisely, they are committed to killing off the parts they don't like by declining to implement them. They point-blank refuse to implement Customized Built-in Elements, for example, and in such (unusually, for the context) vehement, uncompromising, and unconstructive language¹ that I can only surmise some Apple apparatchik's fragile ego would be irreparably shattered by even contemplating an amendment of this position. Thanks to such attitudes, Safari remains the "new IE", the problem browser for which developers must find workarounds. (1) e.g. https://github.com/WICG/webcomponents/issues/509 https://github.com/WICG/webcomponents/issues/509 and other forums besides
- inopinatus 5y ago
  Curiously, the above remark was at +4 and is currently -2, which really just goes to show how polarising Apple is by timezone.
- eyelidlessness 5y ago
  I glanced at the linked issue and I see demands for disregarding the standard to accommodate a non-standard API. Is that what you’re asking for? Or are you on the side of implementing the living standard as it evolves? If there’s another position I’m missing feel free to fill in the blank.
  - inopinatus 5y ago
    That is a very heavily commented ticket (600+ comments) so it’s hard to assess all the alternative positions. However, in my view: as one of the four stewards of WHATWG, Apple have an obligation to either implement the standard, or propose a convincing alternative that the steering group can adopt. I don’t know what’s more embarrassing; that Apple tried to use market power to modify a standard after failing to do so in committee, or that after six years even that strategy was a failure. Either way it all smacks of institutional arrogance.
    - dmitriid 5y ago
strix_varius 5y ago
Web application developers will rightly question the claim that Safari has surpassed Chrome in anything in 2022. With "Safari Technology Preview" and the test suite that this site has chosen to group into "Experimental," you'll see FF: 74, Safari: 73, Chrome: 72. With "stable" and actually-consumed versions of browsers (a more important goal for "interop"), you'll see: - FF: 74 - Chrome: 66 - Safari: 50
- culi 5y ago
  Interop is meant to guide future development. I think there's a reason the default values are based on the experimental versions instead of stable releases

And just like that, Safari has surpassed Chrome in interop 2022 https://wpt.fyi/interop-2022 https://wpt.fyi/interop-2022

by culi 5y ago

And just like that, Safari has surpassed Chrome in interop 2022 https://wpt.fyi/interop-2022 https://wpt.fyi/interop-2022

alwillis 5y ago

The experimental numbers haven’t changed since Interop 2022 was announced. That is, there hasn’t been a new version of Safari Technology Preview, which is what the experimental numbers are based on.

culi 5y ago
Woops you're right. This was premature. But once 15.4 has been released it'll have surpassed Chrome in the stable release as well.

_-david-_ 5y ago

Click stable. Safari is nowhere close.

gsnedders 5y ago
That'll still be Safari 15.1, alas; 15.4 should be close to the experimental score shown.
- jtbayly 5y ago
  Why haven't the stable versions 15.2 and 15.3 been tested? Will 15.4 be tested?
  - gsnedders 5y ago
    Uh, it's 15.3 that's being run, I just can't write the right number it turns out. (I honestly have no idea why I said 15.1!) 15.4 should show up in day or two, there's a bunch of latency in how those metrics are generated currently…

inopinatus 5y ago

Webkit is not committed to fully implementing the HTML Living Standard, or more precisely, they are committed to killing off the parts they don't like by declining to implement them. They point-blank refuse to implement Customized Built-in Elements, for example, and in such (unusually, for the context) vehement, uncompromising, and unconstructive language¹ that I can only surmise some Apple apparatchik's fragile ego would be irreparably shattered by even contemplating an amendment of this position. Thanks to such attitudes, Safari remains the "new IE", the problem browser for which developers must find workarounds. (1) e.g. https://github.com/WICG/webcomponents/issues/509 https://github.com/WICG/webcomponents/issues/509 and other forums besides

inopinatus 5y ago
Curiously, the above remark was at +4 and is currently -2, which really just goes to show how polarising Apple is by timezone.
eyelidlessness 5y ago
I glanced at the linked issue and I see demands for disregarding the standard to accommodate a non-standard API. Is that what you’re asking for? Or are you on the side of implementing the living standard as it evolves? If there’s another position I’m missing feel free to fill in the blank.
- inopinatus 5y ago
  That is a very heavily commented ticket (600+ comments) so it’s hard to assess all the alternative positions. However, in my view: as one of the four stewards of WHATWG, Apple have an obligation to either implement the standard, or propose a convincing alternative that the steering group can adopt. I don’t know what’s more embarrassing; that Apple tried to use market power to modify a standard after failing to do so in committee, or that after six years even that strategy was a failure. Either way it all smacks of institutional arrogance.
  - dmitriid 5y ago

strix_varius 5y ago

Web application developers will rightly question the claim that Safari has surpassed Chrome in anything in 2022. With "Safari Technology Preview" and the test suite that this site has chosen to group into "Experimental," you'll see FF: 74, Safari: 73, Chrome: 72. With "stable" and actually-consumed versions of browsers (a more important goal for "interop"), you'll see: - FF: 74 - Chrome: 66 - Safari: 50

culi 5y ago
Interop is meant to guide future development. I think there's a reason the default values are based on the experimental versions instead of stable releases