Porting Emacs to Chromebooks and the Web [pdf]
fosdem.org
fosdem.org
It links to the current URL (the slide deck PDF), as well as a video recording of the presentation, and metadata about the presentation.
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.
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).
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.
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.
I was thinking this would be wonderful. I am torn between digging into Common Lisp or Clojure, and thought this would be a great first idea.
I am currently stuck with emacs only, but have been playing with MobileOrg for Android. What are you and others doing?
It was, years ago. But right now, it takes less memory than most of my chrome tabs. New frames pop up very quickly, and the only thing that makes me notice it starting from scratch is disk I/O.
https://commondatastorage.googleapis.com/naclports/builds/pe...
You have to go to chrome://flags/ and enable "Native Client" and restart Chrome.
Loading NaCl module.
Loaded runnable-ld.so [1057 KiB]
Loaded emacs_x86_64.nexe [5559 KiB]
Loaded libppapi_simple.so [390 KiB]
Loaded libpthread.so.1106743a [1529 KiB]
Loaded libnacl_io.so [3626 KiB]
Loaded libppapi_cpp.so [2489 KiB]
Loaded libstdc++.so.6 [5583 KiB]
Loaded libtiff.so.5 [659 KiB]
Loaded libjpeg.so.8 [453 KiB]
Loaded libpng16.so.16 [466 KiB]
Loaded libz.so.1 [233 KiB]
Loaded libm.so.1106743a [1270 KiB]
Loaded libgif.so.4 [147 KiB]
Loaded libXaw.so.7 [805 KiB]
Loaded libXmu.so.6 [255 KiB]
Loaded libXt.so.6 [773 KiB]
Loaded libSM.so.6 [147 KiB]
Loaded libICE.so.6 [244 KiB]
Loaded libXext.so.6 [232 KiB]
Loaded libX11.so.6 [1964 KiB]
Loaded librt.so.1106743a [467 KiB]
Loaded libncurses.so.5 [595 KiB]
Loaded libc.so.1106743a [11743 KiB]
Loaded libgcc_s.so.1 [336 KiB]
Loaded libXpm.so.4 [222 KiB]
Loaded libxcb.so.1 [296 KiB]
Loaded libXau.so.6 [138 KiB]
Loaded libdl.so.1106743a [314 KiB]
Unable to create home directory in persistent storage: No such file or directory
At that point I thought it had failed, but after about a minute emacs came up. On OSX it seems to use about 215-240 MB, vs anywhere from 50-200 MB for my other chrome tabs.Anyone have crouton handy to compare the overhead?
What software? "The browser"? And do I misread the crouton instructions or is that actually still running the very same thing, same software, in developer mode with chroots for Other Things™?
As for replacing your ubuntu machine, the default distro is 12.04, but I'm sure you can install the latest.
I don't know about the amount of shell tabs you can have (as I use tmux), but my short experiment seems to hold up well.
The only problems I think you'll face is the scary 'OS Verification' at startup and limited memory (but can be solved by using a SD card). croutons are cheap to install so install, remove, install until you find your niche.
Then I just startup a ssh server there. And head back to ChromeOS and SSH to local host (the secure shell plugin is good for this). This means my chroot is totally independent of any chromeos windows or crosh shells.
Not a chrome web app, but works pretty fast and responsive for me.
Basically I want a Linux laptop that "just works", with MBPr quality (or better) build, screen, and keyboard. One obvious choice is the updated XPS 13. A perhaps less-obvious choice is the Pixel.
Having said all that, Emacs for ChromeOS could have some advantages, e.g. battery life, not needing to "break the security seal" by putting a Chromebook in developer mode, and not needing to chroot (although that's quite easy and ~30 minutes).