Funicular: A Browser App Framework Powered by PicoRuby.WASM
summary
PicoRuby.WASM runs a mruby VM with a cooperative task scheduler so Ruby’s sleep/yield work in the browser by stepping VM instructions for ~16ms then yielding with setTimeout, enabling multitasking without threads; a Chrome debugger extension pauses, steps and evals via a WASM fetch hook. A pure-Ruby SPA framework called Funicular implements a Virtual DOM, class components and routing (demoed with Tic‑Tac‑Toe and a Todo) and a keyboard-as-server demo syncs state over dRuby/WebSocket. The full WASM build with Funicular is 470 kilobytes, noticeably smaller than CRuby.WASM.
AI-written summary · about
chapters (13)
- 0:00Introduction and self-intro
- 1:11What is PicoRuby.WASM
- 3:51Why Ruby over JavaScript
- 5:26How sleep works in PicoRuby.WASM
- 9:26CRuby.WASM vs PicoRuby.WASM
- 11:00Debugging PicoRuby.WASM
- 16:27Introducing Funicular framework
- 19:27When to use Funicular
- 20:52Full-Stack Ruby demo
- 24:39Full-Stack Ruby possibilities
- 25:21Why Funicular's name
- 26:05Live demo of Funicular app
- 28:14Closing and call to action
