(m)Ruby on small devices
summary
mruby runs on Raspberry Pi class hardware by compiling with GCC and minirake, producing a single embeddable binary and C arrays of bytecode for linking; the interactive mirb ≈1.5MB binary and its mruby.a library show far fewer dependencies than MRI. At runtime memory drops from Ruby ≈6MB to values that can fit sub‑2MB targets in theory, but cross‑compiling for production POS hardware remains unfinished. Microbenchmarks show fib(32) at roughly mRuby ~10s vs Ruby ~4s, and boot/load times are noticeably different.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 0:45What is mRuby
- 2:39Why use emRuby
- 3:28Lightweight
- 4:08Small devices
- 5:54FBOs
- 7:31Company
- 7:53Embedding
- 8:46Linking
- 10:40Compile
- 10:51Debugger
- 11:38Embedding bytecode
- 12:38Generating bytecode
- 13:49Compile code
- 14:03MRuby
- 15:41Lua
- 17:09Lua example
- 18:26IM Ruby
- 19:20Announcements
- 20:18Demo session
- 22:56Dependencies
- 23:36Size and Memory
- 29:41Load time
- 34:26Monitoring
related talks
40mmmm..mruby, or why yet another Ruby implementation
36mmruby: AltRuby
35mmRuby meets iOS and RTOS
29mWhat's happening when initializing mruby?
34mEmbedding Ruby into your Daily Life
26mmruby: a Packaging Story Filled with Freedom
33mmruby/c: Running on Less Than 64KB RAM Microcontroller
35mmruby: a Packaging Story Filled with Freedom