[alexpopescu]

Still not, but the new protobuf spec (and rewritten existing drivers) should actually make it pretty easy to get one. I've also heard of a couple of people working on Java and Scala drivers (they were following the new protobuf spec branch), but I don't know the status.

alex @ rethinkdb

[traxtech]

So it won't be official and it may break on any server update or lag in features depending on the maintainer boredom. Too bad, your db seems really nice :)

[alexpopescu]

There's no decision made on this yet. So far, as @coffeemug explained in the previous comment we decided to focus all our efforts on improving the server and getting it closer to "production ready" state, instead of spreading our resources thin and creating a lot of drivers that are not as good as we'd want them to be. The initial protobuf spec was complicated and building drivers on top of it would have required a lot of effort (effort that we thought would be better used to improve the spec and the query language, things that everyone would benefit).

[simcop2387]

All of that work improving the spec and the query language should make it that much easier to make a decent driver. I'd say around the time of it being "production ready" as you put it should be where you have a version that keeps the same protocol so that drivers can be written and not have to be updated for every bug fix?

Am I wrong in thinking that?

[coffeemug]

No, you're absolutely right -- when we mark Rethink as production-ready, we'll also freeze the APIs and ABIs and will be much more careful about breaking things for people.