Michel

I think it displays a really specific thing you can do with RethinkDB -- occasional aggregation on your data. So I don't think we should remove it. We shouldn't call...

We should probably write about `using`/`disposer` -- https://github.com/petkaantonov/bluebird/blob/master/API.md#promiseusingpromisedisposer-promise-promisedisposer-promise--function-handler---promise I have to tests a few things, but I should be able to provide some snippets.

Just pasting a snippet I used (with `bind`). ``` js r.connect({}).bind({}).then(function(conn) { this.conn = conn; return query.run(this.conn); }).then(function(result) { // do things with result }).error(function(err) { // handle error }).finally(function()...

It's a bit more tricky when we change the syntax of a command or change the behavior. Like when we replace `upsert` with `conflict` in `insert`. We have a page...

The project is basically community driven now (as any other RethinkDB projects) cc @marshall007 @KittyBot

Thinky's save command run a query and return a promise, so you can't have it inside `r.branch`. You have to manually do it with Reql at the moment.

Yup, that's probably possible, but I don't think `lib64ncurses5-dev` would work on a 32 bit system.

I could have swear that @coffeemug opened a pull request for that (and that it was merged with 1.13), but I somehow cannot find it -_-

Removing the "bug" label and reassigning to myself. I'll quickly spin up some 32 and 64 bits debian vm and test the instructions

I'm not sure what's going on, but `lib64ncurses5-dev` doesn't exist on Debian 64 bits, but does on Debian 32bits