4 ms·

Maybe rather than a new language, we should work towards browser "assembly" code. Lots of modern JavaScript development is in the direction of: write in languag

by mumrah 15y ago

Maybe rather than a new language, we should work towards browser "assembly" code. Lots of modern JavaScript development is in the direction of: write in language X, compile to JS. Would be nice if there was a lower-level target than JS

jules 15y ago
They are doing that with NativeClient. It runs x86 assembly and LLVM IL in the browser. Supposedly they'll even make it work in other browsers than Chrome.
- stephenhalter 15y ago
  NaCl does not allow direct manipulation of the DOM or provide other JavaScript APIs like canvas. NaCl provides alternative ways of getting things done like pp::Graphics2D, but it is not meant for DHTML. Dash, on the other hand, provides access to JavaScript APIs. I think that browser "assembly" code, like Dash, would have to support this, particularly if it is meant to be an alternative to compiling to JavaScript.
  - Detrus 15y ago
    Pepper is the link between NaCl and browser APIs.
- nxn 15y ago
  PNaCl seems like a separate project from NaCl to me, and NaCl itself can't run LLVM IL. Also, there's really opposition of having it implemented in other browsers, at least Mozilla vocally opposed it. I think that if they managed to do it via a plugin though, that could work.
compay 15y ago
Agree 100%. The fact that Javascript is the only language you can realistically use to script the browser is a terrible limitation and legacy of bad technical decisions at Netscape more than a decade ago. I'm always surprised at the lack of concern about this. While I do actually like Javascript a lot, I think we need to have more choices. When people point out Node as a benefit because "you can use the same language on the client and the server" I agree - but it misses the bigger problem in that, if you want to use the same language on the client and the server, you only have one real choice.

4 ms·

Maybe rather than a new language, we should work towards browser "assembly" code. Lots of modern JavaScript development is in the direction of: write in languag

by mumrah 15y ago

jules 15y ago
They are doing that with NativeClient. It runs x86 assembly and LLVM IL in the browser. Supposedly they'll even make it work in other browsers than Chrome.
- stephenhalter 15y ago
  NaCl does not allow direct manipulation of the DOM or provide other JavaScript APIs like canvas. NaCl provides alternative ways of getting things done like pp::Graphics2D, but it is not meant for DHTML. Dash, on the other hand, provides access to JavaScript APIs. I think that browser "assembly" code, like Dash, would have to support this, particularly if it is meant to be an alternative to compiling to JavaScript.
  - Detrus 15y ago
    Pepper is the link between NaCl and browser APIs.
- nxn 15y ago
  PNaCl seems like a separate project from NaCl to me, and NaCl itself can't run LLVM IL. Also, there's really opposition of having it implemented in other browsers, at least Mozilla vocally opposed it. I think that if they managed to do it via a plugin though, that could work.
compay 15y ago
Agree 100%. The fact that Javascript is the only language you can realistically use to script the browser is a terrible limitation and legacy of bad technical decisions at Netscape more than a decade ago. I'm always surprised at the lack of concern about this. While I do actually like Javascript a lot, I think we need to have more choices. When people point out Node as a benefit because "you can use the same language on the client and the server" I agree - but it misses the bigger problem in that, if you want to use the same language on the client and the server, you only have one real choice.