4 ms·
I missed the Q&A question about standardization, and that alleviates some of the concerns about how this will be play out. But again, the concern is that Googl
by swang 12y ago
I missed the Q&A question about standardization, and that alleviates some of the concerns about how this will be play out.
But again, the concern is that Google is going to go ahead with this even before any approval. So when every single javascript related product from Google is already using it, what's preventing Google from just shrugging and going "oh well" and just continuing on with their modifications?
What is V8 for if not for Chrome (since V8 is not beholden to node/iojs)?
- kbenson 12y agoWell, you can always look to past behavior, such as with SPDY[1]. Once something like SPDY was adopted as HTTP/2, Google decided on dropping SPDY support for Chrome. Their core complaints with HTTP were addressed in a new standard, so there's no reason for them to keep their specific variation alive and cluttering the browser landscape. 1: http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-ht...