2 ms·
What about Firefox? Is Safari's team smaller than Firefox's as well? Looking at this page: https://webkit.org/team/ https://webkit.org/team/ and comparing it t
by osrec 6y ago
What about Firefox? Is Safari's team smaller than Firefox's as well?
Looking at this page: https://webkit.org/team/ https://webkit.org/team/ and comparing it to https://wiki.mozilla.org/Firefox/Team/whois https://wiki.mozilla.org/Firefox/Team/whois would suggest otherwise.
Do you have numbers from elsewhere to back up that claim?
Btw, I'm not saying Google are right to power through with poorly designed APIs either, but when there is a standard in place, why Safari takes sooo long to implement it is perplexing (or perhaps just a rather obvious strategy).
- dmitriid 6y ago> Is Safari's team smaller than Firefox's as well? Unknown > but when there is a standard in place, why Safari takes sooo long to implement it is perplexing Some standards are so bad, even Chrome ends up deprecating them (see Custom Elements v0). Or they just go out of favor (see HTML Imports). Or they are so poorly specified that even years after "becoming a standard" they have things like "this section is not specified yet" in their texts. And the status of these "standards" is often not above "Candidate Recommendation" (that is it is gathering implementation experience, and yes, that refers to Service Workers). BTW Service Workers were moved to Candidate Recommendation about half a year ago: https://github.com/w3c/ServiceWorker/issues/1460 https://github.com/w3c/ServiceWorker/issues/1460 ("Double check everyone is happy with v1 going to CR.") So yeah, I don't know what to say. Safari isn't chasing every API under the sun? Good for them. Web Devs assuming that whatever's in Chrome is the be all end all standards on the web? Bad for the web and for the devs. Apple possibly not prioritising Safari? Bad for the web as well.