We haven’t abandoned Ruby support @gottlike. The lack of it in the intro is something we should address.
We put the 2.0 beta out hoping to get some feedback, but we didn’t have much feedback or many downloads. We’ve had it in a bit of a holding pattern since the 1.x downloads and interest have been higher. Thanks for letting us know you’re interested in seeing 2.0 through to GA.
You haven’t abandoned it but you haven’t put anything out for the MRI engine in over 2 years. I really do not know anyone who uses JRuby and I am involved in a few Ruby groups. This is really making me reconsider our choice to use couchbase on our platform. Not updating the sdk in over 2 years is abandoning in my book. These times we live in move fast and if you are not moving forward, it sure feels like you are abandoned cause catching up is no fun.
I should say I am sold on couchbase, the direction, the release pattern your vision of the server, everything. Everything except your support for Ruby. Using a gem built for 1.x is not good when you have a community release of 4.0.
It is a real shame we couldn’t come together on this
Is there any update on Ruby SDK to support Couchbase 4.5?
Actually without partial update, the overhead of database access is too high for production. I have used Couchbase with Ruby on Rails for two years and we are considering to move to mongoDB, as there is simply no active development on Ruby SDK.
Oh my… Until now I’ve never doubted my choice of our user profile database, which is Couchbase. I have posted a open case of a segmentation fault issue with Couchbase 1.3.14 gem but no one seems to care. I guess I should start to look for alternatives to migrate.
it’s the first time I learn about a NoSQL database and I chose Couchbase because I like the features it presents, but since I’m a RoR developer, I feel sad to see no support for the ruby sdk. RoR is more present in the web than Python and Go, but you threat it like a second degree citizen, which really sad thing. I am really questioning my choice because of this.
Throwing in our two cents here as well. We’ve been using the Ruby SDK pretty actively for a couple years now, and in production. There are some very nice elements to Couchbase, and it would be great to see both the straight SDK and the model classes continue to grow and development. Count us as a vote for an actively maintained Ruby SDK with or without Rails.