Given that the higher order bit is clearly the safari vs chrome, I hope this will improve. It must improve. Too much difference.
-
-
Replying to @MiguelCamba @addyosmani and
I think you've misinterpreted this data. Its not showing the dif between safari and chrome, but rather devices of different power
1 reply 0 retweets 0 likes -
Replying to @Snugug @addyosmani and
I know, but there’s powerful androids (Galaxy Note II p.e) that perform much worse than even the IP 5c (which has a CPU from from 2012)
1 reply 0 retweets 0 likes -
Replying to @MiguelCamba @addyosmani and
I highly recommend you watch https://youtu.be/4bZvq3nodf4 from
@slightlylate. Does a great job explaining why advertised power !== actual power1 reply 0 retweets 0 likes -
Replying to @Snugug @addyosmani and
I know about it. But even in my own desktop, my test suite runs 70% faster in safari than chrome. Same device. That’s almost twice as fast.
2 replies 0 retweets 0 likes -
Replying to @MiguelCamba @Snugug and
That’s not to say chrome is a bad browser, it has many features safari lacks, but in pure JS execution safari destroys it.
1 reply 0 retweets 0 likes -
Replying to @MiguelCamba @Snugug and
Safari is actually ahead of Chrome in terms of ES2016+ implementation.
2 replies 0 retweets 0 likes -
Replying to @Martndemus @Snugug and
I was thinking in web features rather than JS features, starting with your beloved PWAs
1 reply 0 retweets 1 like -
Replying to @MiguelCamba @Snugug and
I wouldn't ding a browser for not having implemented a W3C WD yet. If it's a CR, then it's a different story.
1 reply 0 retweets 1 like -
Replying to @Martndemus @Snugug and
TIL that service workers are still a working draft
1 reply 0 retweets 2 likes
They're REC track w/ multiple interoperable implementations. Core is stable. "Working draft" misleading.
-
-
Replying to @slightlylate @MiguelCamba and
Actually, this is worth digging into because it's such a persistent myth. The W3C process is *hugely* conservative.
1 reply 1 retweet 3 likes -
Replying to @slightlylate @MiguelCamba and
Many features that make it into the WHATWG "living standard" wouldn't even be counted as WDs in the W3C process.
2 replies 0 retweets 0 likes - 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.