Some thoughts after (almost) a year of real Xamarin use

Re:Some thoughts after (almost) a year of real Xamarin use by badlogic on Saturday April 04, 2015 @01:43PM (#9321517)

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/ru...

[ Parent | on HN ]

Re:Some thoughts after (almost) a year of real Xamarin use by mwcampbell on Saturday April 04, 2015 @02:21PM (#9321665)

Doesn't seem like a problem to me. The occasional weak reference to break cycles wouldn't hurt anything on Android, would it?

[ Parent | on HN ]

Re:Some thoughts after (almost) a year of real Xamarin use by badlogic on Saturday April 04, 2015 @02:38PM (#9321715)

I guess not. But it's going to be tough to use normal Ruby gems on iOs that aren't aware of the ref counting.

[ Parent | on HN ]