3 ms·

The Blink team have simply become the new IE style refuseniks, using mobile performance as the standard excuse. Mozilla, Apple and Microsoft have all been creat

The Blink team have simply become the new IE style refuseniks, using mobile performance as the standard excuse. Mozilla, Apple and Microsoft have all been creating new "standard" APIs which no one else implements, yet in order to get best performance on their systems you have to use. If you read the history of that bug someone rightly points out a key thing is MS have to support the pen on surface, and that was as important to MS there as multitouch was to Apple with iOS. Mobile performance is clearly that to the Chrome team, and this mismatch of priorities is what is at the root of the problem.

teleclimber 12y ago
> The Blink team have simply become the new IE style refuseniks Don't kid yourself. Sometimes it's the IE team that refuses to play along. Example: WebRTC. Overall I feel that the cooperation between vendors on standards is quite good. but you can't expect all these mega corps to agree on everything all the time.
- gtjrossi 12y ago
  On the contrary! I work on the IE team and we're playing along nicely. Google just joined us on the ORTC spec, which Chrome considers to be essentially Web RTC 1.1. http://www.cnet.com/news/reconciliation-draws-closer-for-skype-like-chat-on-the-web/ http://www.cnet.com/news/reconciliation-draws-closer-for-sky... For IE implementation status, follow along here: http://status.modern.ie/webrtcobjectrtcapi http://status.modern.ie/webrtcobjectrtcapi and check out our ORTC prototype: http://html5labs.interoperabilitybridges.com/prototypes/object-rtc/object-rtc/info http://html5labs.interoperabilitybridges.com/prototypes/obje...
cromwellian 12y ago
You mean like Apple refusing Pointer Events first, or Mozilla refusing WebP, NaCL/PNaCl/Pepper, trying to refuse Web Audio, MS refusing WebGL, Canvas, Web Audio, WebRTC. Every vendor fights their own turf battles. Not-invented-here seems to also be a big issue in standards committees.

teleclimber 12y ago

> The Blink team have simply become the new IE style refuseniks Don't kid yourself. Sometimes it's the IE team that refuses to play along. Example: WebRTC. Overall I feel that the cooperation between vendors on standards is quite good. but you can't expect all these mega corps to agree on everything all the time.

gtjrossi 12y ago
On the contrary! I work on the IE team and we're playing along nicely. Google just joined us on the ORTC spec, which Chrome considers to be essentially Web RTC 1.1. http://www.cnet.com/news/reconciliation-draws-closer-for-skype-like-chat-on-the-web/ http://www.cnet.com/news/reconciliation-draws-closer-for-sky... For IE implementation status, follow along here: http://status.modern.ie/webrtcobjectrtcapi http://status.modern.ie/webrtcobjectrtcapi and check out our ORTC prototype: http://html5labs.interoperabilitybridges.com/prototypes/object-rtc/object-rtc/info http://html5labs.interoperabilitybridges.com/prototypes/obje...

cromwellian 12y ago

You mean like Apple refusing Pointer Events first, or Mozilla refusing WebP, NaCL/PNaCl/Pepper, trying to refuse Web Audio, MS refusing WebGL, Canvas, Web Audio, WebRTC. Every vendor fights their own turf battles. Not-invented-here seems to also be a big issue in standards committees.