Ruby in the browser with NativeClient (NaCl)
summary
Shows how Google Chrome's Native Client executes compiled native code in a sandboxed browser runtime: you compile C/C++ (or Ruby ports) with a special toolchain, ship architecture-specific binaries plus an nmf manifest, and the browser verifies and runs them with the Pepper API under the same security boundaries as JavaScript. Demos include compile Ruby to NaCl and a fully playable Quake running in browser, plus examples of App Engine using NaCl and a fallback path using PNaCl LLVM bitcode → Emscripten to JS; limitations: no arbitrary FS or raw sockets, toolchain and API versions matter.
AI-written summary · about
chapters (18)
- 0:00Language diversity
- 1:45Browser limitations
- 3:24JavaScript experience
- 5:09Ruby experiments
- 6:52Ruby in the browser
- 8:28Server-side Ruby
- 9:31Microsoft Gestalt
- 12:46Plugin history
- 16:52Chrome architecture
- 19:03Native client
- 25:17Code capabilities
- 28:38Ruby with NaCl
- 31:41Running Quake
- 34:44NaCl use cases
- 39:42Portable NaCl
- 41:21Emscripten
- 46:29Future of web innovation
- 58:00Q&A
related talks
46mQt for Native Client
16mNative CPU Performance in the Brow
34mReimagining 2D graphics and game development with Ruby
59mEmscripten and asm.js: C++'s role in the modern web
33mThe Ruby Racer: Under the Hood
21mWeb Browsers: Om nom nom
46mEmbracing Collaboration with JRuby and JavaScript
30mOpal: The Journey From JavaScript to Ruby
