News for hackers. Stuff that matters.
Re:PyPy.js: First Steps by rfk on Tuesday July 23, 2013 @11:25PM (#6094332)
The RPython toolchain has another mode of operation, which outputs higher-level class-based code rather than low-level C-style code. They use this for a CLR backend, but it would be interesting to try implementing a JavaScript backend at that level and compare it to the lowlevel+emscripten approach.

(This may have been tried in the past; in the post "10 years of PyPy" it's mentioned that there was once a JavaScript backend but it was removed because it was a horrible idea: http://morepypy.blogspot.com.au/2013/02/10-years-of-pypy.htm...)

Re:PyPy.js: First Steps by voltagex_ on Tuesday July 23, 2013 @11:53PM (#6094439)
Common Language Runtime? I can't find any mention of this backend.
Re:PyPy.js: First Steps by rfk on Tuesday July 23, 2013 @11:59PM (#6094448)
I got my acronyms wrong, it's called the "CLI" backend, but it's definitely in there: http://doc.pypy.org/en/latest/cli-backend.html
Re:PyPy.js: First Steps by rfk on Wednesday July 24, 2013 @12:35AM (#6094546)
Heh, actually it might be possible to cheat a little with this backend as well, using http://www.jsil.org/ to translate the output of the cli backend into javascript. Trying C+Emscripten versus CIL+JSIL would be a very interesting comparison.