• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Whats the verdict on Cocoaruby from others ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Whats the verdict on Cocoaruby from others ?


  • Subject: Re: Whats the verdict on Cocoaruby from others ?
  • From: Sherm Pendley <email@hidden>
  • Date: Mon, 17 Jul 2006 17:08:28 -0400

On Jul 17, 2006, at 3:50 PM, Jakob Olesen wrote:

On 17/07/2006, at 2.47, CoLo0LoGo wrote:

I found this while learning ruby on rails
http://rubycocoa.sourceforge.net

From the notes, it uses the full Garbage collection of Ruby, and the
full spectrum of Cocoa's Objects and other items

Has anyone tried it out for anything ?

I haven't tried it myself, but on general principle I say the more bridges are available, the better off we as developers are. Choices are a good thing.


I have tried it and ended up writing my own Ruby bridge. Not because rubycocoa is bad, but it is intended for a different purpose than mine.

Rubycocoa is intended for writing a Ruby application that uses Cocoa. For this it works very well.
I wanted to write a Cocoa app that uses Ruby for scripting. For this it works not so well.

It's a young project. Give 'em time. That sounds quite similar to my first CamelBones release too. Basic message forwarding came first, then runtime integration later.


Oh, and it is LGPL.

I'm curious - are you saying that's a pro or a con? I chose the LGPL for my CamelBones bridge too. I made the choice of LGPL over the GPL specifically to limit the "viral" aspects of the license to the bridge code itself. It will not "infect" your app. I want my code to stay free, but your code is your business - maybe literally! :-)


I'm not asking this to get into a flamewar. If my choice of LGPL is limiting my potential audience, I'd certainly consider changing it - it's a pragmatic issue for me, not a religion.

Something like pyobjc for Python seems a lot more mature.

Pyobjc is *way* more mature than either RubyCocoa or CamelBones. It dates back to pre-Apple NeXT days.


sherm--

Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Whats the verdict on Cocoaruby from others ?
      • From: Jakob Olesen <email@hidden>
References: 
 >Whats the verdict on Cocoaruby from others ? (From: CoLo0LoGo <email@hidden>)
 >Re: Whats the verdict on Cocoaruby from others ? (From: Jakob Olesen <email@hidden>)

  • Prev by Date: Re: KVO and the observeValueForKeyPath bottleneck
  • Next by Date: Re: Whats the verdict on Cocoaruby from others ?
  • Previous by thread: Re: Whats the verdict on Cocoaruby from others ?
  • Next by thread: Re: Whats the verdict on Cocoaruby from others ?
  • Index(es):
    • Date
    • Thread