Judging by the docs [1], RubyMotion does indeed not seem to use a GC on iOS but instead relies on ref counting, reusing auto-release pools. That means cyclic re

Judging by the docs [1], RubyMotion does indeed not seem to use a GC on iOS but instead relies on ref counting, reusing auto-release pools. That means cyclic refs are an issue. You have to explicitely use weak references throughout your code. They are not on Android, where RubyMotion uses the Dalivk/ART GC. So, your cross-platform Ruby code has to deal with two different types of memory management systems. I'm not sure this qualifies as a better option to what Xamarin provides. [1] http://www.rubymotion.com/developers/guides/manuals/cocoa/runtime/ http://www.rubymotion.com/developers/guides/manuals/cocoa/ru...