Hi Luca,

Any news about supporting Ruby?

Thanks,
Cyprian


On Sunday, 9 November 2014 01:30:58 UTC+1, Lvc@ wrote:
>
> Hi guys,
> We're working with driver authors to pick the most active/well-done to be 
> official. This seems to work pretty well with .NET driver, where the main 
> committers are now working into the official one rather than separate forks.
>
> Now it's the *Ruby* turn! We received a big wave of interest on Ruby 
> recently. Today the situation is quite fragmented between 3 drivers:
>
>    1. The *Adrian Madrid*'s JRuby driver: 
>    https://github.com/aemadrid/orientdb-jruby. I found the *Glenn 
>    Goodrich*'s branch as the most updated: 
>    https://github.com/ruprict/orientdb-jruby/tree/2.0-M1
>    2. The *Ryan Fields*' Ruby (non JRuby) driver: 
>    https://github.com/ryanfields/orient_db_client. I found the *Joshua 
>    Harding*'s fork as the most updated: 
>    https://github.com/jhstatewide/orient_db_client
>    3. The *Darrick Wiebe*'s JRuby driver: 
>    https://github.com/pangloss/pacer-orient, the OrientDB impl of *Pacer* 
>    (https://github.com/pangloss/pacer)
>
> The most updated driver is *Pacer-Orient*, but the most used seems to be 
> *Orientdb-JRuby*. Unfortunately not all Ruby users love/can run their app 
> on JRuby (I don't know why, maybe it's only something against JVM?).
>
> Furthermore, AFAIK, nobody created an *ActiveRecord* implementation for 
> Ruby on Rails. *Aaron Patterson* started something 4 years ago, but the 
> project hasn't never been completed (https://github.com/tenderlove/orient
> ).
>
> We're looking for comments, feedbacks, thoughts to pick one driver as 
> official and try to collect a common effort on it to provide a high quality 
> and updated piece of software.
>
> WDYT?
>
> Thanks,
> Lvc@
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to