Ruby, Opal and WebAssembly
summary
DXOpal ships a playable Ruby-to-JS game framework that runs entirely in the browser (single folder with index.html, main.rb and opal runtime), uses Canvas, WebAudio and Matter.js for physics, and attempts to speed up heavy math by compiling a C triangle‑triangle collision routine to WebAssembly. Benchmarks show JS collision code ~45 ms versus Wasm ~52 ms so no big win; result: Opal + existing JS libraries works well today and WebAssembly helps in some C‑heavy or hard‑to-port cases. DXOpal (Opal game framework) triangle‑triangle collision C→Wasm measured JS ≈ Wasm (45→52 ms)
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 2:12Introducing Opal Ruby
- 5:39Creating dxOpal for browser games
- 9:51Demo of dxOpal in action
- 10:11Adding physics with Matter.js
- 11:39Running games without Ruby installation
- 15:41Opal and WebAssembly overview
- 18:53WebAssembly basics and asm.js
- 24:02WebAssembly benefits and browser support
- 24:50Integrating WebAssembly with dxRuby
- 25:56Performance comparison results
- 26:58Future of Ruby on WebAssembly
- 33:18Conclusion and Opal recommendation
- 35:03Q&A session
related talks
39mJavascript without javascript
27mWebAssembly for Performant Interactivity
21mHit the Ground Running with WebAssembly
28mPatrick Kettner - SeattleJS Conference 2017
50mWeb Assembly
46mA State Of WebAssembly - The Browser is now a real VM
53mWebAssembly
01h 42mWebAssembly: Writing Once and Running Everywhere NG