"We are advocating that you all help build a better JS on JS, which then becomes standardized as JS.next," Eich wrote.
The better way is a dialog between JS developers, especially natural leaders among them such as @jashkenas, and TC39 members.
This won't involve "scientific polling". There's no substitute for nice judgment and (ultimately) sound language design theory and practice. But the experts must also learn from the users, who've moved mountains on their own over the last ten years. And users, meaning JS developers, should step up to this dialog and away from fear and passivity.
In a blog post that formed the basis for her JSConf presentation, Rebecca Murphey wrote: "As a community, we need to agree on a core set of functionality that ought to be provided by the language but isn't, and implement that itself as an interchangeable module."
CoffeeScript and Google's "transcompiler" (transpiler) Traceur lead Josh Peek to tweet: "Takeaway of #jsconf: JS compilers/transpilers are the future. Coding in regular JS is going to be like not using a framework."