Re: [MacRuby-devel] MacRuby-devel Digest, Vol 37, Issue 51
On 31 mars 2011, at 05:56, <macruby-devel-request@lists.macosforge.org> Bryan Harrison <bryan@bryanharrison.com> wrote:
Message: 6 Date: Wed, 30 Mar 2011 20:43:27 -0700 From: Bryan Harrison <bryan@bryanharrison.com> To: macruby-devel@lists.macosforge.org Subject: [MacRuby-devel] Tyro Needs Ruby vs. O-C Advice Message-ID: <F3D5A990-D053-45A7-91FC-E29FBD6DF66A@bryanharrison.com> Content-Type: text/plain; charset="windows-1252"
I've decided to use an upcoming sabbatical to teach myself OS X and iOS programming. My background includes OS X systems administration and web development, mostly using the Apache/MySQL/PHP model. I'm familiar with OOP concepts and have trifled with any number of languages from C to AppleScript, but am not fluent in any object oriented language. I've been exploring Xcode 4 for a week and feel conversant with the IDE if not yet able to accomplish anything with it.
So? I understand that Cocoa is a given, but today's million dollar question is Objective-C or MacRuby? I'm a blank slate with regard to both and so could use some good advice. For example?
What are the advantages of MacRuby over Objective-C?
What are the advantage of O-C over Ruby?
Is Xcode's support for O-C significantly better than it's handling of Ruby? Do I care?
At this point I'm primarily interested in OS X development, but iOS clearly needs to run a close second. What's the current status of Ruby development for iOS and is it likely to go anywhere in the nearish future?
Any thoughts on the longer-term prospects of either language?
Any thoughts from anybody will be much appreciated.
Thanks, Bryan
I will be blunt: stay away from MacRuby and go with Objective-C. Before I get burned at the stake on this list, let me explain why. This stems from an assumption I made from you question about your goal: Assumption: your goal is to become proficient in Cocoa [touch] programming as fast as possible, starting from basically zero. If that assumption is wrong, then the conclusion might be too. MacRuby is very good already, but it's a far less treaded route. As a result, you will have to load your brain with additional burden, always a difficult proposition when learning: - Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out. - So you will need to translate every example and snippet from Objective-C to Ruby. This means you will effectively need to learn two languages instead of one at the same time, together with Cocoa. - You will need to translate every one of your question from Ruby to Objective-C when posting to stackoverflow or Apple's forum, or risk getting no answer. Sure you can stay in this list, but that's one less resource. - Every time you face a difficult roadblock, you will necessarily have to wonder "Is this me? Or is this MacRuby?". To answer that question for certain, you will then port your code to Objective-C to make sure. - You will face less understanding development tools. When you have an issue with them, the official answer will be "MacRuby development is not supported". With Xcode 4 being immature by itself, you probably don't want to add an immature MacRuby to the mix. Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it. On the practical details, what has been said still applies, with two small corrections: - You also have ahead of time compilation with MacRuby. But arguably, you don't care about that when learning. - The job market for iOS programming is thriving, and for Mac programming is getting a lot better. Sure, Ruby programmers are also in demand, but it's not clear to me which market is actually better. One thing is for sure: demand for iOS Ruby programmers is zero. Jean-Denis
Jean-Denis Muys wrote:
Bryan Harrison <bryan@bryanharrison.com> wrote:
I've decided to use an upcoming sabbatical to teach myself OS X and iOS programming. [...] [T]oday's million dollar question is Objective-C or MacRuby? [...]
I will be blunt: stay away from MacRuby and go with Objective-C. [...] One thing is for sure: demand for iOS Ruby programmers is zero.
+1 -- http://josephholsten.com
Well put, sir. Well put. Met vriendelijke groet, Eloy Durán On Mar 31, 2011, at 10:26 AM, Jean-Denis Muys wrote:
I will be blunt: stay away from MacRuby and go with Objective-C.
Before I get burned at the stake on this list, let me explain why. This stems from an assumption I made from you question about your goal:
Assumption: your goal is to become proficient in Cocoa [touch] programming as fast as possible, starting from basically zero.
If that assumption is wrong, then the conclusion might be too.
MacRuby is very good already, but it's a far less treaded route. As a result, you will have to load your brain with additional burden, always a difficult proposition when learning:
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out. - So you will need to translate every example and snippet from Objective-C to Ruby. This means you will effectively need to learn two languages instead of one at the same time, together with Cocoa. - You will need to translate every one of your question from Ruby to Objective-C when posting to stackoverflow or Apple's forum, or risk getting no answer. Sure you can stay in this list, but that's one less resource. - Every time you face a difficult roadblock, you will necessarily have to wonder "Is this me? Or is this MacRuby?". To answer that question for certain, you will then port your code to Objective-C to make sure. - You will face less understanding development tools. When you have an issue with them, the official answer will be "MacRuby development is not supported". With Xcode 4 being immature by itself, you probably don't want to add an immature MacRuby to the mix.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
On the practical details, what has been said still applies, with two small corrections:
- You also have ahead of time compilation with MacRuby. But arguably, you don't care about that when learning. - The job market for iOS programming is thriving, and for Mac programming is getting a lot better. Sure, Ruby programmers are also in demand, but it's not clear to me which market is actually better. One thing is for sure: demand for iOS Ruby programmers is zero.
Jean-Denis
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away from MacRuby. All those ruby dev who like me are most likely coming from webdevelopment, dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
Well it would appear that Macruby is just not ready for real development. I for one have some faith that Macruby is good enough now and will be language of choice in the future. There are no barriers to you mixing external frameworks or adding objc classes. Ruby as a language has many features that you can grow into that objc doesn't ( meta programming). If you use a standard version of ruby there is nothing to stop even a c hacker using 'the latest' libraries and putting a simple wrapper on. Ruby has become an umbrella for all my work from admin support to web development. And now with macruby I have desktop apps for Mac. Not forgetting jruby of course for any java fans and others like ruinous. So yes on a serious note I would recommend everyone go learn c as a minimum. But if you just want to have some serious fun go mad with ruby/macruby. The learning will come by doing. Terry Moore On 31/03/2011, at 11:41 PM, "Thomas R. Koll" <info@ananasblau.com> wrote:
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away from MacRuby.
All those ruby dev who like me are most likely coming from webdevelopment, dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On Mar 31, 2011, at 11:41 AM, Terry Moore wrote:
Well it would appear that Macruby is just not ready for real development.
I for one have some faith that Macruby is good enough now and will be language of choice in the future.
There are no barriers to you mixing external frameworks or adding objc classes.
Ruby as a language has many features that you can grow into that objc doesn't ( meta programming).
This has come up more than once today. ObjC is capable of a lot more meta-programming than people are giving it credit for. The Objective-C runtime is, afterall, what MacRuby is built on. However, Ruby's meta-programming support is significantly simpler, making it easier to both use and abuse :)
If you use a standard version of ruby there is nothing to stop even a c hacker using 'the latest' libraries and putting a simple wrapper on.
Ruby has become an umbrella for all my work from admin support to web development. And now with macruby I have desktop apps for Mac.
Not forgetting jruby of course for any java fans and others like ruinous.
So yes on a serious note I would recommend everyone go learn c as a minimum. But if you just want to have some serious fun go mad with ruby/macruby. The learning will come by doing.
Terry Moore
On 31/03/2011, at 11:41 PM, "Thomas R. Koll" <info@ananasblau.com> wrote:
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away from MacRuby.
All those ruby dev who like me are most likely coming from webdevelopment, dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
I for one would like to see some examples of objc meta programming. Standard ruby is built with c are you saying c has some meta programming capabilities because of this. An example like attr_accessor. I know objc 2 now has properties. I also know some aspects of ruby are scary 'eval' and re opening classes but can you load objc source compile and run it aka 'eval'. All I'm trying to say here is that ruby has a place and with the macruby implementation you have nothing to lose by trying some ruby. Mix it up a little and have some fun too. Terry Moore On 1/04/2011, at 7:59 AM, Matt Massicotte <massicotte@apple.com> wrote:
On Mar 31, 2011, at 11:41 AM, Terry Moore wrote:
Well it would appear that Macruby is just not ready for real development.
I for one have some faith that Macruby is good enough now and will be language of choice in the future.
There are no barriers to you mixing external frameworks or adding objc classes.
Ruby as a language has many features that you can grow into that objc doesn't ( meta programming).
This has come up more than once today. ObjC is capable of a lot more meta-programming than people are giving it credit for. The Objective-C runtime is, afterall, what MacRuby is built on. However, Ruby's meta-programming support is significantly simpler, making it easier to both use and abuse :)
If you use a standard version of ruby there is nothing to stop even a c hacker using 'the latest' libraries and putting a simple wrapper on.
Ruby has become an umbrella for all my work from admin support to web development. And now with macruby I have desktop apps for Mac.
Not forgetting jruby of course for any java fans and others like ruinous.
So yes on a serious note I would recommend everyone go learn c as a minimum. But if you just want to have some serious fun go mad with ruby/macruby. The learning will come by doing.
Terry Moore
On 31/03/2011, at 11:41 PM, "Thomas R. Koll" <info@ananasblau.com> wrote:
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away from MacRuby.
All those ruby dev who like me are most likely coming from webdevelopment, dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
On Mar 31, 2011, at 12:47 PM, Terry Moore wrote:
I for one would like to see some examples of objc meta programming.
Here's a good place to start looking. http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ObjCR... In particular, there are functions you can use for generating classes and methods at runtime, including modifying classes already present. Though, that's often done much more easily using categories. You can even do method_missing-style magic, but not nearly as nicely as in Ruby.
Standard ruby is built with c are you saying c has some meta programming capabilities because of this.
An example like attr_accessor. I know objc 2 now has properties.
I also know some aspects of ruby are scary 'eval' and re opening classes but can you load objc source compile and run it aka 'eval'.
All I'm trying to say here is that ruby has a place and with the macruby implementation you have nothing to lose by trying some ruby. Mix it up a little and have some fun too.
Terry Moore
On 1/04/2011, at 7:59 AM, Matt Massicotte <massicotte@apple.com> wrote:
On Mar 31, 2011, at 11:41 AM, Terry Moore wrote:
Well it would appear that Macruby is just not ready for real development.
I for one have some faith that Macruby is good enough now and will be language of choice in the future.
There are no barriers to you mixing external frameworks or adding objc classes.
Ruby as a language has many features that you can grow into that objc doesn't ( meta programming).
This has come up more than once today. ObjC is capable of a lot more meta-programming than people are giving it credit for. The Objective-C runtime is, afterall, what MacRuby is built on. However, Ruby's meta-programming support is significantly simpler, making it easier to both use and abuse :)
If you use a standard version of ruby there is nothing to stop even a c hacker using 'the latest' libraries and putting a simple wrapper on.
Ruby has become an umbrella for all my work from admin support to web development. And now with macruby I have desktop apps for Mac.
Not forgetting jruby of course for any java fans and others like ruinous.
So yes on a serious note I would recommend everyone go learn c as a minimum. But if you just want to have some serious fun go mad with ruby/macruby. The learning will come by doing.
Terry Moore
On 31/03/2011, at 11:41 PM, "Thomas R. Koll" <info@ananasblau.com> wrote:
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away from MacRuby.
All those ruby dev who like me are most likely coming from webdevelopment, dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Greetings, Yeah, I remember being shocked when I poked at a 'method_missing' kind of thing on Objective C and realized that it was totally doable... I had a little fun with it, before punting and going back to a language where it's easy. :) Check out: http://goo.gl/bz50U -- Morgan On Thu, Mar 31, 2011 at 1:23 PM, Matt Massicotte <massicotte@apple.com>wrote:
On Mar 31, 2011, at 12:47 PM, Terry Moore wrote:
I for one would like to see some examples of objc meta programming.
Here's a good place to start looking.
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ObjCR...
In particular, there are functions you can use for generating classes and methods at runtime, including modifying classes already present. Though, that's often done much more easily using categories. You can even do method_missing-style magic, but not nearly as nicely as in Ruby.
Standard ruby is built with c are you saying c has some meta programming
capabilities because of this.
An example like attr_accessor. I know objc 2 now has properties.
I also know some aspects of ruby are scary 'eval' and re opening classes
but can you load objc source compile and run it aka 'eval'.
All I'm trying to say here is that ruby has a place and with the macruby
implementation you have nothing to lose by trying some ruby. Mix it up a little and have some fun too.
Terry Moore
On 1/04/2011, at 7:59 AM, Matt Massicotte <massicotte@apple.com> wrote:
On Mar 31, 2011, at 11:41 AM, Terry Moore wrote:
Well it would appear that Macruby is just not ready for real
development.
I for one have some faith that Macruby is good enough now and will be
language of choice in the future.
There are no barriers to you mixing external frameworks or adding objc
classes.
Ruby as a language has many features that you can grow into that objc
doesn't ( meta programming).
This has come up more than once today. ObjC is capable of a lot more meta-programming than people are giving it credit for. The Objective-C runtime is, afterall, what MacRuby is built on. However, Ruby's meta-programming support is significantly simpler, making it easier to both use and abuse :)
If you use a standard version of ruby there is nothing to stop even a c
hacker using 'the latest' libraries and putting a simple wrapper on.
Ruby has become an umbrella for all my work from admin support to web
development. And now with macruby I have desktop apps for Mac.
Not forgetting jruby of course for any java fans and others like
ruinous.
So yes on a serious note I would recommend everyone go learn c as a
minimum. But if you just want to have some serious fun go mad with ruby/macruby. The learning will come by doing.
Terry Moore
On 31/03/2011, at 11:41 PM, "Thomas R. Koll" <info@ananasblau.com>
wrote:
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away
from MacRuby.
All those ruby dev who like me are most likely coming from
webdevelopment,
dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
Interesting... a nice reference for all those bridgesupport method parameters :) Its nice but not what hit me about ruby... especially this http://mislav.uniqpath.com/poignant-guide/ persevere until dwemthy's array. classes inhereting from a functions gave me a headache :) I have gone from being hunched up and worried about types etc. to being very relaxed and froody... I'm not even sure I could go back to adding semi colons to the end of a line :) Terry On 1/04/2011, at 9:23 AM, Matt Massicotte wrote:
On Mar 31, 2011, at 12:47 PM, Terry Moore wrote:
I for one would like to see some examples of objc meta programming.
Here's a good place to start looking.
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/ObjCR...
In particular, there are functions you can use for generating classes and methods at runtime, including modifying classes already present. Though, that's often done much more easily using categories. You can even do method_missing-style magic, but not nearly as nicely as in Ruby.
Standard ruby is built with c are you saying c has some meta programming capabilities because of this.
An example like attr_accessor. I know objc 2 now has properties.
I also know some aspects of ruby are scary 'eval' and re opening classes but can you load objc source compile and run it aka 'eval'.
All I'm trying to say here is that ruby has a place and with the macruby implementation you have nothing to lose by trying some ruby. Mix it up a little and have some fun too.
Terry Moore
On 1/04/2011, at 7:59 AM, Matt Massicotte <massicotte@apple.com> wrote:
On Mar 31, 2011, at 11:41 AM, Terry Moore wrote:
Well it would appear that Macruby is just not ready for real development.
I for one have some faith that Macruby is good enough now and will be language of choice in the future.
There are no barriers to you mixing external frameworks or adding objc classes.
Ruby as a language has many features that you can grow into that objc doesn't ( meta programming).
This has come up more than once today. ObjC is capable of a lot more meta-programming than people are giving it credit for. The Objective-C runtime is, afterall, what MacRuby is built on. However, Ruby's meta-programming support is significantly simpler, making it easier to both use and abuse :)
If you use a standard version of ruby there is nothing to stop even a c hacker using 'the latest' libraries and putting a simple wrapper on.
Ruby has become an umbrella for all my work from admin support to web development. And now with macruby I have desktop apps for Mac.
Not forgetting jruby of course for any java fans and others like ruinous.
So yes on a serious note I would recommend everyone go learn c as a minimum. But if you just want to have some serious fun go mad with ruby/macruby. The learning will come by doing.
Terry Moore
On 31/03/2011, at 11:41 PM, "Thomas R. Koll" <info@ananasblau.com> wrote:
Am 31.03.2011 um 10:26 schrieb Jean-Denis Muys:
I will be blunt: stay away from MacRuby and go with Objective-C.
I say, if you don't know either Ruby or Objective-C yet, stay away from MacRuby.
All those ruby dev who like me are most likely coming from webdevelopment, dive into this new world of desktop applications. It's a fascinating world.
- Less applicable resources for learning: less examples, less books, less blog posts, less people to help you out.
Which is great if you are able and willing to fill those gaps. Open Source is not only about using what exists but also to add something new to it. Over time you will get deeper and more profund understanding.
Now the MacRuby journey might taste a lot better, depending on you. And if for you "the reward is the _journey_", you might consider it.
+1
- One thing is for sure: demand for iOS Ruby programmers is zero.
Which might be subject to change. Don't forget, the only two things keeping MacRuby from iOS is the lack of a garbage collector and the App Store policy about programming languages. Both in the hands of Apple, just like MacRuby itself.
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
participants (7)
-
Eloy Durán
-
Jean-Denis Muys
-
Joseph Anthony Pasquale Holsten
-
Matt Massicotte
-
Morgan Schweers
-
Terry Moore
-
Thomas R. Koll