Re: why not just import new language into browser?

I would be very happy to know that the web assembly standard answers my question. thanks you to all of those who understand my request and make progress for it. 2015-05-27 0:35 GMT+08:00 Matthew Robb : > > On Tue, May 26, 2015 at 12:22 PM, eric wrote:

Re: why not just import new language into browser?

在 15/5/28 02:04, duanyao 写道: 在 2015年05月27日 23:01, 李白|字一日 写道: 2015-05-27 2:18 GMT+08:00 duanyao duan...@ustc.edu mailto:duan...@ustc.edu: 在 2015年05月26日 11:13, eric 写道: I would like to suggest a language neutro interface for all languages inside all browsers. Web

Re: why not just import new language into browser?

在 2015年05月27日 23:01, 李白|字一日 写道: 2015-05-27 2:18 GMT+08:00 duanyao duan...@ustc.edu mailto:duan...@ustc.edu: 在 2015年05月26日 11:13, eric 写道: I would like to suggest a language neutro interface for all languages inside all browsers. Web APIs are defined in WebIDL,

Re: why not just import new language into browser?

On Wed, May 27, 2015 at 5:01 PM, 李白|字一日 calid...@gmail.com wrote: Web Api, Native Client are all the efforts made to make the browser side to be a platform other than HTML + CSS + JAVASCRIT Parser. Web API (by which I assume you mean the APIs defined in the W3C and WHATWG standards) is

Re: why not just import new language into browser?

2015-05-27 2:18 GMT+08:00 duanyao duan...@ustc.edu: 在 2015年05月26日 11:13, eric 写道: I would like to suggest a language neutro interface for all languages inside all browsers. Web APIs are defined in WebIDL, which is language neutro. However I don't think the implementations of those APIs in

Re: why not just import new language into browser?

I would like to suggest that everyone let this thread die. It's way out of scope for es-discuss, and three kinds of bogus just considering the Subject: line. If anyone wants to chat about it, HN has regular recurring why not blub? and why not bytecode threads. /be (co-moderator with @awbjs)

Re: why not just import new language into browser?

2015-05-26 4:13 GMT+01:00 eric calid...@gmail.com: and the import of class is no need for frontend developement. the import of classes will lead to the demand of packages or namespaces. all this only to polute the simplicity javascript has today. And no good to the javascript developement .

Re: why not just import new language into browser?

2015-05-26 18:18 GMT+01:00 eric calid...@gmail.com: why asm.js ? because there is no support for c++/c from browsers. what if the browsers support c++/c navtively? by script language=c src=http://code.site.com/abc.o; http://code.site.com/abc.o /script which will run faster than asm.js.

Re: why not just import new language into browser?

Programmers are always facing different environments or problems. the differences between frontend and backend or the database or os kernel are minor to talented programmers. You are laugh at yourself. Abandoning dart doesn't mean that the way is wrong, maybe only the timing is not proper.

Re: why not just import new language into browser?

在 15/5/26 20:46, Matthew Robb 写道: On Mon, May 25, 2015 at 11:13 PM, eric calid...@gmail.com mailto:calid...@gmail.com wrote: I would like to suggest a language neutro interface for all languages inside all browsers. ​I hate to be the broken record guy but I guess on these lists

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

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