Asked an entire room full of webdevs yesterday if any of them knew that FF/Chrome/Opera/Brave/etc. for iOS weren't allowed to compete on engine quality. Zero hands up.
-
Show this thread
-
The consequences of being forced into WebKit WebView on iOS are massive. Every browser there faces a Sophie's Choice: fast JS or no netstack pluggability. They all choose not losing benchmarks by a huge amount. And that's only one in the long line of constraints.
3 replies 24 retweets 147 likesShow this thread -
Alternative browsers on iOS can never *really* be the default. And they can't use their own engines. And they can't use Service Workers, which means no Push Notifications or offline support. And no PWA installability. Etc. etc.
7 replies 30 retweets 170 likesShow this thread -
Apple dramatically under-invests in WebKit, which means that the richest users have the jankiest web, and switching browsers doesn't help. Business decision makers don't think the web can deliver the experiences they want to give users because, on iOS (which they use), it can't.
13 replies 98 retweets 320 likesShow this thread -
Replying to @slightlylate
This isn't to say that Safari/WebKit engineering isn't good. I've had the pleasure of meeting some of them and they are good people who build a good product.
1 reply 0 retweets 9 likes
Pound for pound, I'd happily suggest they're the best in the world! I have nothing against the fine folks on that team. This is a set of decisions made by folks far above line engineering and mgmt.
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.