Re: why not just import new language into browser?

Lol "you" don't see the advantages, yet most do (including me). Why wouldn't we improve the language itself. So just leave the language alone like that, and let's focus on using plugins for other languages to work?? really?? and then we'll have to put in work into updating and fixing bugs on those

why not just import new language into browser?

hi, all after es6 was drafted for a long time, i don't see any advantages from these changes. the import syntax is no better than require('module') or require(['sss'], function() {}); and the import of class is no need for frontend developement. the import of classes will lead to the demand

Re: Class decorators and async process

Gray Zhang wrote: It’s OK, I just wait for |this.weapon| to resolve, but then my |hit| method becomes async, and everything based on |@inject| property should be async, which is not actually what I want. Async can be contaminating, yes. Sync is out of bounds in browsers, and for Node.js a

Re: forward-incompatible Function.prototype.toString requirement

I've published an initial proposal here: https://github.com/michaelficarra/Function-prototype-toString-revision Feel free to add comments by opening a Github issue or pull request. I will add this proposal to the agenda for this week's meeting. On Fri, Apr 17, 2015 at 9:08 AM, Mark S. Miller wro