Announcing RethinkDB 2.3.6: the first release under community governance

Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?

Re: Announcing RethinkDB 2.3.6: the first release under community governance

#5

Post by dis-sys » Tue, Jul 18, 2017, 9:23 AM UTC

skrebbel wrote: post #4

Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?

well, you can have a quick look at how many commits in the last 3 months vs total number of commits they had so far.

not trying to judge anything as I no longer follow the project, but I think those numbers do tell the story.

Re: Announcing RethinkDB 2.3.6: the first release under community governance

#6

Post by bartvanH » Tue, Jul 18, 2017, 9:28 AM UTC

dis-sys wrote: post #5

skrebbel wrote: post #4

Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?

well, you can have a quick look at how many commits in the last 3 months vs total number of commits they had so far. not trying to judge anything as I no longer follow the project, but I think those numbers do tell the story.

Looking at the graphs on github you could say development has slowed down, but i'd like to argue that since there is no commercial incentive anymore the project seems to be much more focussed on stability. And when bugfixing you write less lines while spending the same amount of time.

To me focus on stability is the most important thing in a database so this makes me happy as an ops person, get it stable first and then if needed add more features. though i think rethinkdb is already quite feature complete.

Re: Announcing RethinkDB 2.3.6: the first release under community governance

#7

Post by tracker1 » Tue, Jul 18, 2017, 10:18 AM UTC

I'm really happy to see progress again. Hopefully we'll see more... I appreciate everyone that worked to make this possible.

side note: the node driver in npm still hasn't been re-published with the license type in the package.json, so doesn't show the license. Only noting as this can cause issues in some organizations.

Re: Announcing RethinkDB 2.3.6: the first release under community governance

#8

Post by jwr » Tue, Jul 18, 2017, 10:49 AM UTC

skrebbel wrote: post #4

Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?

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.

Re: Announcing RethinkDB 2.3.6: the first release under community governance

#9

Post by egeozcan » Tue, Jul 18, 2017, 12:03 PM UTC

jwr wrote: post #8

skrebbel wrote: post #4

Anyone got an insight into how well this is going? Compared to when the company was active, how fast is progress? Would you bet on Rethink in this day and age?

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?

Re: Announcing RethinkDB 2.3.6: the first release under community governance

#10

Post by williamstein » Tue, Jul 18, 2017, 12:11 PM UTC

bartvanH wrote: post #6

dis-sys wrote: post #5

Earlier quoted context omitted.

well, you can have a quick look at how many commits in the last 3 months vs total number of commits they had so far. not trying to judge anything as I no longer follow the project, but I think those numbers do tell the story.

Looking at the graphs on github you could say development has slowed down, but i'd like to argue that since there is no commercial incentive anymore the project seems to be much more focussed on stability. And when bugfixing you write less lines while spending the same amount of time. To me focus on stability is the most important thing in a database so this makes me happy as an ops person, get it stable first and th…

In my personal opinion (based on heavily using RethinkDB for two years), many of the core issues of RethinkDB are related to performance, not bugs. I had bet on where RethinkDB would end up performance wise, had development continued with people who really understand how it works doing fulltime development.