Re: [Rubycocoa-talk] Ruby on the iPhone?

[Timothy P. <ti...@ge...>]

Whilst I don't want to discourage you (as you seem quite dead set on this),
I would certainly question the ROI in time and potential financial
implications of what your looking at doing... Lets review:

1. You want to create a bespoke ruby compiler for a closed platform which
you have no internal knowledge of or access to the internal OS.

2. You'd have to rebuild an entire ruby language parser - you point to
Jruby. Bear in mind that Jruby has scores of very talented programmers
contributing and its taken a good few years to get to this point where its
reasonably usable. 

3. Your looking at doing this on your own.

4. Its highly possible that you will loose a lot of what makes ruby flexible
by having a code -> compile -> deploy workflow.

5. Id imagine there would be several difficulties (just as there are with
the ruby-cocoa bridge) of mapping duck typed ruby to statically typed obj-c

So, IMO, for the time you would have to sink into this (were talking years,
not months) would it not just be easier to bite the bullet and write obj-c.
Its not that difficult after all...

Just some thoughts.

Tim

PS: Based on Apple's strategy elsewhere with application development, id say
its *very* unlikely that the iPhone runs any kind of VM. Not to mention
performance / resource issues on a device that size.


On 11/03/2009 08:44, "Steven D. Arnold" <st...@ar...> wrote:

> Yeah.  I agree without Apple's permission, loading the Ruby runtime
> into the iPhone would violate the EULA.  I do think there is a chance
> they could be talked into allowing this, but short of that, any
> solution would have to generate and link .o files in the same way
> Objective-C does.  It would be a Ruby compiler down to the bare metal,
> not a VM as the environment in which Ruby currently runs.
> 
> For all I know, Apple already has a bytecode-driven VM in the iPhone.
> If that is true, then the compiler could just compile to that bytecode
> and the problem is no different than the problems of, say, the Jruby
> project.  It's very similar with ARM, too, you just have to think of
> ARM's commands as the bytecode to use. :-)
> 
> On Mar 11, 2009, at 3:20 AM, Axel M. Roest wrote:
> 
>> At 23:21 -0400 10-03-2009, Steven Arnold wrote:
>>> Disclaimer: IANAL, and for that reason this will be my last post on
>>> the legal side of this issue.  My reading of the iPhone SDK agreement
>>> below is my opinion only.
>> 
>> I think it is more this part that's bothering us:
>> 3.3.2 <stuff deleted>. No interpreted code may be downloaded and used
>> in an Application except for code that is interpreted and run by
>> Apple's Published APIs and built-in interpreter(s).
>> 
>> As ruby is neither built-in, nor supported in the API, you're on
>> your own.
>> 
>> just my 0.02...
>> 
>> Axel
>> -- 
>> _________________________
>> Axel Roest
>> axelloroestello@{AIM/MSN} - Skype:axellofono - XOIP: 084-8749988
>> 
>> 
----------------------------------------------------------------------------->>
-
>> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM)
>> are
>> powering Web 2.0 with engaging, cross-platform capabilities. Quickly
>> and
>> easily build your RIAs with Flex Builder, the Eclipse(TM)based
>> development
>> software that enables intelligent coding and step-through debugging.
>> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
>> _______________________________________________
>> Rubycocoa-talk mailing list
>> Rub...@li...
>> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
> 
> 
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>