Compare with ActiveRecord/DataMapper, i really have no love on Core Data.
If MacRuby could run all those ActiveRecord/DataMapper adapters, there are few
reason to use a Core Data wrapper (much like ruby dev will not ever normally
use mysql/postgres gem directly). Certainly if such wrapper follo
tl;dr: I propose getting tutorials and code under one structured collection, and
to create classes that wrap Core Data in the same way HotCocoa wraps NSViews.
I agree with the sentiments about "setting ourselves apart". How do we do that?
Please allow me to pontificate. I apologize for the length.
While i totally agree the points here, a more pressing need, IMHO, is fixing
bugs and incompatibility of MacRuby such that what works on other
implementation just works in MacRuby,
For instance, require_relative is not implemented which breaks a lot of 1.9
ruby code. (http://www.macruby.org/tra
On 6 Apr 2012, at 00:06, Matt Aimonetti wrote:
> Many of you have been wondering what is going on with the MacRuby project
> given the lack of up-to-date releases and overall communication.
> I feel we owe you some explanation.
>
Matt, as someone trying to ship a product based on MacRuby, I'd
On 7/04/2012, at 11:24 PM, Francis Chong wrote:
> Automatic Reference Counting implements automatic memory management for
> Objective-C objects and blocks. If you read MacRuby source code, you will
> found that the VM is not even written in Objective-C!
This is why a one page description of h
01:36 +0200
>> From: Eloy Duran
>> To: "MacRuby development discussions."
>>
>> Subject: Re: [MacRuby-devel] The future of MacRuby
>> Message-ID:
>> Content-Type: text/plain; charset="windows-1252"
>>
>>> Can you import before
: Re: [MacRuby-devel] The future of MacRuby
> Message-ID: (mailto:d10916e5-8078-4c70-87df-9b05e593f...@gmail.com)>
> Content-Type: text/plain; charset="windows-1252"
>
> > Can you import before it's open? I just assumed it wasn't accessible at all
> > unt
