A better URL is <a href="https://fosdem.org/2015/schedule/event/emacs_and_elisp_on_the_chromebook/" rel="nofollow">https://fosdem.org/2015/schedule/event/emacs_and_elisp_on_th...</a><p>It links to the current URL (the slide deck PDF), as well as a video recording of the presentation, and metadata about the presentation.
Normally I wouldn't question the usefulness of a project, but I'm having trouble seeing why this would be worthwhile.<p>Emacs already runs natively on every operating system for which Chrome also runs, so the portability aspect is not so important. And most of the time you would want to have a shell and even a compiler, so the sandboxing is kind of a problem.<p>I guess a sandboxed emacs is kind of a strange thing to think about. The trouble with emacs is that it brings in so many dependencies that you are getting dangerously close to replicating a full OS in a browser tab, but then you might as well just use a normal operating system (or a VM).<p>The idea of a Chromebook that I can run emacs on is really appealing, so much so that I did just that, but used Crouton. I thought I'd mainly be ssh'ing into a server, but actually have done a lot of stuff locally. Chromebooks make a really nice laptop if you can work completely in the shell and browser. It's all very simple.<p>I could see a use for this for having org-mode available in a browser, that would be useful, but it's a lot of work to go to just for that.
If you want to try Emacs running in Chrome (using NaCL):<p><a href="https://commondatastorage.googleapis.com/naclports/builds/pepper_41/trunk-253-g089940f/publish/emacs/glibc/emacs/emacs.html" rel="nofollow">https://commondatastorage.googleapis.com/naclports/builds/pe...</a><p>You have to go to chrome://flags/ and enable "Native Client" and restart Chrome.