3 ms·
>The time for vetoing it was when it was being decided (and Apple does shoot down tons of proposals), not when everyone else already agreed is was a good idea.
by nemothekid 5y ago
>The time for vetoing it was when it was being decided (and Apple does shoot down tons of proposals), not when everyone else already agreed is was a good idea.
But this isn't what happens. Safari is pretty good at standards (they do support BigInt and fetch). What actually happens is Google "proposes" a standard, pushes it to Chrome, then goads Mozilla and Apple into adopting it. Half of the time web developers cry about Safari not adopting Standards its because they want to adopt a experimental API that Google pushed
- kinjba11 5y ago> Safari is pretty good at standards (they do support BigInt and fetch) That is why I say "Safari gets them years later". For example: Chrome 42, released April 2015, supported fetch. Safari 10, released March 2017, supported fetch. Nearly two years after Chrome and Firefox. * https://webkit.org/blog/7477/new-web-features-in-safari-10-1/ https://webkit.org/blog/7477/new-web-features-in-safari-10-1... * https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API#browser_compatibility https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API#b...