I did bet on it and so far I'm happy as long as it continues to work. Sure, I would like it to be developed further, but what I have now is great and works well.
As for progress, it slowed down to non-existent during the handover period, and now seems to be picking up.
Great to hear that! Is there any issues close to being show-stoppers or any "it would have been immensely helpful to have this but I can work around it" features? Also, what would be the thing that RethinkDB is really good at that makes you keep using it?
1. It's distributed. I can elastically add/remove nodes. I need this not so much for scalability, as for reliability, and I want to be future-proof.
2. Changefeeds. Nothing else even comes close, and my entire application is built around them.
I have no show-stoppers. The thing works. Sure, I'd love to see some things done differently (ReQL looks nice at a first glance, but has many limitations in practice, causing code that ends up being quite complex), but overall even if it were to stay exactly the way it is now, I'd continue using it.
As for progress, it slowed down to non-existent during the handover period, and now seems to be picking up.