Re:Js.js - A JavaScript interpreter in JavaScript
by cjfont on Monday January 02, 2012 @06:26PM
(#3417857)
Any thoughts as to applications for this? At ~65MB, I don't see this getting used client side.
[ Parent
| on HN ]
Re:Js.js - A JavaScript interpreter in JavaScript
by Animus7 on Monday January 02, 2012 @06:32PM
(#3417874)
I don't even think the worst part is the download (which can be cached). The worst part is the fact that you're running your script, interpreted by a weirdly generated unoptimized script, interpreted by a scripting engine which only then runs on metal. I'm shooting in the dark, but I'd bet the performance and memory usage would be a disaster for anything but Hello, world.
Re:Js.js - A JavaScript interpreter in JavaScript
by spullara on Monday January 02, 2012 @08:01PM
(#3418143)
Actually, right now, even Hello world is a disaster. My guess is that this will drive some interesting improvements to emscripten and LLVM so there may be some benefits down the line.
Re:Js.js - A JavaScript interpreter in JavaScript
by wahnfrieden on Monday January 02, 2012 @07:08PM
(#3417985)
There's also going to be an enormous startup time as it has to parse and compile all that code, even if it's already cached.
Re:Js.js - A JavaScript interpreter in JavaScript
by jterrace on Monday January 02, 2012 @06:41PM
(#3417901)
65MB is our current unoptimized, uncompressed version. I expect the final version to be around 5-10MB. Still large, but not quite as bad.
Re:Js.js - A JavaScript interpreter in JavaScript
by cdata on Monday January 02, 2012 @10:01PM
(#3418418)
I'm not super familiar with Narcissus in practice, but on paper your projects sound very similar. Were there any interesting reasons why you opted to make this project instead?