4 ms·

Maybe I'm misunderstanding something here. This reads like Google is now attempting to dictate the direction Javascript goes in, by implementing proposals befo

Maybe I'm misunderstanding something here. This reads like Google is now attempting to dictate the direction Javascript goes in, by implementing proposals before they've become standards, and shipping them in their browser. Given the dominance of the browser engine, it effectively sets the direction of the language, particularly if people start to use it (which they will). This is feeling like IE6 all over again. We're getting non-standard implementations of standards, that will further encourage websites to be "Chrome only".

mkozlows 8y ago
Implementing proposals before they become standards is totally normal and a good way to prove out the proposal. Google's implemented tons of proposals, and generally pulled out the ones that didn't become standardized.
magicalist 8y ago
> implementing proposals before they've become standards, and shipping them in their browser. Is that like commenting before knowing how the TC-39 standardization process works? :P The proposals are Stage 3. To reach Stage 4 and be complete, there have to be actual, multiple implementations shipping[1]. As the spec page notes, implementations are also almost done in both Firefox[2] and Safari[3]. [1] https://tc39.github.io/process-document/ https://tc39.github.io/process-document/ [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1499448 https://bugzilla.mozilla.org/show_bug.cgi?id=1499448 [3] https://bugs.webkit.org/show_bug.cgi?id=174212 https://bugs.webkit.org/show_bug.cgi?id=174212
dragonwriter 8y ago
> This reads like Google is now attempting to dictate the direction Javascript goes in, by implementing proposals before they've become standards, and shipping them in their browser. You seem to be proposing a Catch-22 that would freeze JavaScript forever: no one should implement a feature before it is a standard, but completing the process to become a standard requires implementations to exist. Therefore, no new feature can ever be implemented or become part of the standard.

mkozlows 8y ago

Implementing proposals before they become standards is totally normal and a good way to prove out the proposal. Google's implemented tons of proposals, and generally pulled out the ones that didn't become standardized.

magicalist 8y ago

> implementing proposals before they've become standards, and shipping them in their browser. Is that like commenting before knowing how the TC-39 standardization process works? :P The proposals are Stage 3. To reach Stage 4 and be complete, there have to be actual, multiple implementations shipping[1]. As the spec page notes, implementations are also almost done in both Firefox[2] and Safari[3]. [1] https://tc39.github.io/process-document/ https://tc39.github.io/process-document/ [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1499448 https://bugzilla.mozilla.org/show_bug.cgi?id=1499448 [3] https://bugs.webkit.org/show_bug.cgi?id=174212 https://bugs.webkit.org/show_bug.cgi?id=174212

dragonwriter 8y ago

> This reads like Google is now attempting to dictate the direction Javascript goes in, by implementing proposals before they've become standards, and shipping them in their browser. You seem to be proposing a Catch-22 that would freeze JavaScript forever: no one should implement a feature before it is a standard, but completing the process to become a standard requires implementations to exist. Therefore, no new feature can ever be implemented or become part of the standard.