. .

podcastAAC

IM 164: Mobile Smalltalk (AAC)

March 2, 2014 20:11:41.058

Welcome to episode 164 of Independent Misinterpretations - a Smalltalk and dynamic language oriented podcast with James Robertson and David Buck.

This week James and David talk about Smalltalk for mobile devices - david has been building an implementation for Android (with some thoughts towards eventual IO support as well). You can read more about Dave's work in progress over on his site

You can subscribe to the podcast in iTunes (or any other podcatching software) using this feed directly or in iTunes with this one.

To listen now, you can either download the mp3 edition, or the AAC edition. The AAC edition comes with chapter markers. You can subscribe to either edition of the podcast directly in iTunes; just search for Smalltalk and look in the Podcast results. You can subscribe to the mp3 edition directly using this feed, or the AAC edition using this feed using any podcatching software. You can also download the podcast in ogg format.

If you like the music we use, please visit Josh Woodward's site. We use the song Troublemaker for our intro/outro music. I'm sure he'd appreciate your support!

If you have feedback, send it to jarober@gmail.com - or visit us on Facebook - you can subscribe in iTunes using this iTunes enabled feed.. If you enjoy the podcast, pass the word - we would love to have more people hear about Smalltalk!

Tags: ,

Enclosures:
[im164.m4a ( Size: 20136083 )]

posted by James Robertson

Comments

Re: IM 164: Mobile Smalltalk (AAC)

[anonymous] March 3, 2014 13:02:17.510

Is there not still an IOS restriction against deploying both interpreted code, as well as background garbage collectors?

Re: IM 164: Mobile Smalltalk (AAC)

[David Buck] March 3, 2014 18:28:32.811

In iOS, you can deploy interpreted code so long as all the code is delivered as part of the application and isn't dynamically downloaded.

See [link 1]

As for garbage collection, the restriction seems to be less on garbage collection and more on background processes. Garbage collection (especially generation scavenging) is normally done as a foreground process. Allowing processes to run while background garbage collection is running is a much more sophisticated algorithm and one I may not implement.

If I'm mistaken about either of these points, I would appreciate being corrected. My reading of the license agreement is that neither of these is intrinsically a problem.

[1 http://www.gamasutra.com/blogs/KerryJones/20130604/193593/iOS_interpreted_code.php]

 Share Tweet This