About RubyObjC.
Why Ruby and Objective-C?
Ruby and Objective-C are two great languages for software development that have complementary strengths and weaknesses. They also have some special characteristics that allow them to work together well. That might be because they have a common ancestor, but let's look forward instead. Forward to the start of a beautiful friendship.
RubyObjC allows software developers to have the best of both worlds.
With RubyObjC, Ruby programmers get a structured way to build high-performing subsystems and access to a rich library of components. Objective-C programmers get an interpreted environment for interacting with their code, an amazingly clear and concise way of expressing their designs, and another huge library of reusable code.
RubyObjC is a completely new bridge between Ruby and Objective-C. Written in late 2006, it was designed to take advantage of recent improvements in the Objective-C runtime and its author's experience documenting and evaluating RubyCocoa, an open-source Ruby/Objective-C bridge begun in 2001.
RubyObjC uses Ruby all over. Documentation is generated with RDoc, testing is managed with Test::Unit, and RubyObjC is distributed as a Ruby gem. RubyObjC also includes a Rake task that can be used to build a Cocoa application. When an application is written with Ruby code only, it can be built with no compilation or linking. When the application includes Objective-C code, that code is automatically compiled and linked into the executable. This allows Cocoa applications to be easily built from the command line or your favorite text editor.
Licensing.
RubyObjC is released under the terms of the Ruby license. For details, see the RubyObjC LICENSE file.
Get started.
Install the gem. Use the rubyapp command to generate a skeletal application. Build it with Rake, then explore RubyObjC with its built-in interpreter. Download and run some examples. To learn more, see the RubyObjC guides.