From Server to Client: Ruby on Rails on WebAssembly
summary
A minimal Rails app compiles into a single Wasm module and runs entirely in the browser, demonstrated by a Run Ruby Dev playground and a wasm-fire rails toolkit that packages Ruby and gems. Networking uses a service worker acting as the HTTP server and the DB uses a sqlite adapter via a JS shim to call out to browser storage. File storage uses the File System APIs or Origin Private File System; image processing uses wasm ports; offline sync options include ElectricSQL/Pite or CouchDB replication. Mobile Safari stack limits remain an issue.
AI-written summary · about
chapters (13)
- 0:00Rails on WebAssembly intro
- 1:52Ruby’s WASM support
- 3:19Rails architecture & WASM
- 6:33Live Rails in browser
- 8:44How Rails-to-WASM works
- 10:07Database adapters & SQLite
- 11:34Web server via service workers
- 13:18Storage & background tasks
- 14:48Performance & bundle size
- 16:15Why build this & next steps
- 17:19Browser-based Rails use cases
- 19:08Closing thoughts & future
- 19:36Q&A
related talks
25mThe future of Rails begins in the browser
16mBuilding interactive Ruby gem tutorials with Wasm
22mWebAssembly beyond the browser
31mThere Is No Server
50mWeb Assembly
24mWasm Workers Server: Portable Serverless Apps with WebAssembly
29mWhat is Web Assembly and Why Should you Care?
30mWhy Should You Consider JavaScript on WebAssembly?