<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 27, 2011, at 8:19 , Yoshiki Ohshima wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>One more bit of trick I can think of is to run another JavaScript<br>environment in NaCl; the upside of this would be to have a completely<br>separated address space for your program. Lively Kernel currently<br>seemingly does a good job of not hard-crashing easily even when the<br>programmer is trying self-rewriting code. But if such code is<br>literally isolated in another address space, it would be much safer to<br>experiment. (Though most of this safely can be provided by browser<br>tabs.)<br></div></blockquote></div><br><div>There is already a way to safely run (unknown) JS code in a sandbox-like environment on your web page. I have looked into this the last couple of days and (web) workers (HTML 5) seem to do a great job and are available not only in Chrome (as NaCI is).</div><div>One example is <a href="https://github.com/eligrey/jsandbox">https://github.com/eligrey/jsandbox</a>. But I am sure there are more implementations for that.</div><div><br></div><div>Of course, this does not solve the problem of getting hardware access (and right know I am not sure why I would want that for an environment like the Lively Kernel).</div><div>But I would be interested in ideas/projects that do need hardware access...</div><div><br></div><div>Cheers,</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Marko</div></body></html>