3 ms·

> 1. Google implements this 2. Chrome becomes the fastest browser by a wide margin 3. Other browsers die or become minor players 4. Google leverages this to enf

> 1. Google implements this 2. Chrome becomes the fastest browser by a wide margin 3. Other browsers die or become minor players 4. Google leverages this to enforce their own changes into the HTML/Javascript domain, "for the better" of the web and maybe even into mobile. 5. Web is broken unless you use Chrome Er, you just made up five steps, none of which have happened yet, and then conclude that they sound like "Google's version of EEE". That's what happens when you make up a "Google's version of EEE" scenario" :) It's a proposed ES7+ addition being implemented behind a runtime flag. Can you be specific about what that has to do with Korean banking laws and destruction of the competitive browser landscape?

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 ago
  Well, 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...
ddoolin 12y ago
This is rough and maybe slightly off but the gist is that Korean banks (and other institutions) are required by law to use ActiveX and other IE-only technologies which had (has?) kept IE's browser share ridiculously high (with most on older versions). I lived there for a few years and worked with Macs. I was completely unable to access my bank account online. Even when I could log in on a Windows desktop, there's an extremely overly-complicated (and quite manual) certificate system also required.

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 ago
Well, 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...

ddoolin 12y ago

This is rough and maybe slightly off but the gist is that Korean banks (and other institutions) are required by law to use ActiveX and other IE-only technologies which had (has?) kept IE's browser share ridiculously high (with most on older versions). I lived there for a few years and worked with Macs. I was completely unable to access my bank account online. Even when I could log in on a Windows desktop, there's an extremely overly-complicated (and quite manual) certificate system also required.