mRuby meets iOS and RTOS
summary
MobiRuby ports mruby into iOS so Ruby code can call Cocoa classes and ship native apps — a small game already made it to the App Store — but mruby omits most stdlib, keyword args and C extensions so gems don’t work; mruby binary is tiny compared to CRuby. On embedded side mruby runs on TOPPERS RTOS and an FM3 Cortex‑M3 board, offering a serial REPL and a higher‑priority LED blink task; footprint is cut by config macros, symbol-table tweaks and removing the stdlib and the system actually runs. MobiRuby: ~406 KB mruby vs >2 MB CRuby FM3 Cortex‑M3: 128 KB RAM, 1 MB flash TOPPERS/ASP RTOS for real‑time priorities
AI-written summary · about
chapters (11)
- 0:00Introduction to Mobile Ruby
- 3:53Understanding mRuby
- 5:51Cocoa Bridge and Future Plans
- 8:33Mobile Ruby Components
- 11:46Future Development Roadmap
- 13:43Current Status and Q&A
- 18:00mRuby on Embedded Systems
- 20:05Demo: mRuby on Microcontroller
- 24:18Technical Implementation
- 27:23Real-time Operating System
- 30:15Memory Optimization Techniques
related talks
36m(m)Ruby on small devices
40mmmm..mruby, or why yet another Ruby implementation
36mmruby: AltRuby
29mmake mruby more portable: Why and How
33mmruby/c: Running on Less Than 64KB RAM Microcontroller
26mmruby: a Packaging Story Filled with Freedom
27mROM: the final frontier of mruby
34mEmbedding Ruby into your Daily Life