Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Introduction to RubyMotion

Introduction to RubyMotion

Presented to bentonville.rb Ruby Group in Bentonville, AR on 21 May 2013

Addam Hardy

May 21, 2013
Tweet

More Decks by Addam Hardy

Other Decks in Technology

Transcript

  1. iOS

  2. Alright, so what is it? RubyMotion • Fork of MacRuby

    • Ruby implementation on the Objective-C Runtime • Ruby 1.9 compliant • Unified Runtime ( Objective-C Runtime + RubyMotion Runtime) • 0 performance compromises • Custom garbage collection (much like ARC) • Statically compiled. (Ruby -> LLVM Bitcode -> Assembly)
  3. Laurent Sansonetti 7 years at Apple Mac OSX MacRuby Gnome

    iLife RubyCocoa Left Apple and disappeared for a while... came back with RubyMotion @lrz
  4. Alright, so what isn’t it? RubyMotion • A bridge •

    An HTML5 solution • A wrapper • An excuse to not learn Objective-C (not exactly anyway)
  5. Why should I use RubyMotion? • Were you ever going

    to learn Objective-C? • Ruby Community • Ease of use and rapid development
  6. Why should I use RubyMotion? • Were you ever going

    to learn Objective-C? • Ruby Community • Ease of use and rapid development RUBY Reason Numero Uno:
  7. MOAR Reasons for RubyMotion • Better tools (Use what you’ve

    always used) • Templates for OS X and Cocos2D games • Command line toolchain • _Much_ easier to learn • Full REPL • Less boilerplate (seems like 60% of iOS coding usually) • Easier testing! • Rake
  8. Nothing Is Perfect™ • $$$$ • Costs $199 for a

    license • Works forever but $99 annual fee for support and updates • No require • cannot require files at runtime. Must be available at build time • No eval • Regular gems do not work