There seems to be confusion about how, exactly, Apple keeps the web second-class on iOS. Understandable! It's the interplay of several interlocking effects. Let's examine them (thread).https://twitter.com/slightlylate/status/1190665796717957120 …
-
Show this thread
-
Replying to @slightlylate @mattjbaldo
Then there the time, without justification as far as I remember, that they stomped on WebCL with a legal notice. While WebGL 2.0 compute shaders are getting close, there's still no other GPU compute standard for web browsers. https://pcper.com/wp-content/uploads/2017/02/0abc-apple-webcl-disclosure-jan14-clean.pdf …
1 reply 0 retweets 3 likes -
Replying to @scottmichaud @mattjbaldo
WebGPU is being co-driven by Apple folk, and I'm excited about it.
2 replies 0 retweets 6 likes -
Replying to @slightlylate @mattjbaldo
Hopefully the W3C will be more careful about accepting anything from Apple. Their lawyers haven't had problems abusing those contributions in the past. But yes hopefully it's all positive.
1 reply 0 retweets 0 likes -
Replying to @scottmichaud @mattjbaldo
Apple plays by the rules at W3C (and elsewhere). I don't see I'll intent there, and certainly not of late.
1 reply 0 retweets 1 like -
Replying to @slightlylate @mattjbaldo
It's not ill intent that's the problem. It's lawyers going back to see what stick they can wield in 10 years.
2 replies 0 retweets 0 likes
Again, I don't see much of that game playing of late. Important to avoid anchoring on one bad historical example (e.g. touch events) and credit teams where and when things improve.
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.