Holy shit, my worst nightmare is realized. I LOVE RethinkDB, I use it for EVERYTHING. It has everything I've ever wanted in a database. Relational documents, realtime feeds. Sadness. Someone better be picking up from where they left off.
It really is the best DB I've ever used. Would love to support the project with donations if that were possible.
RethinkDB is shutting down
341–350 of 457 posts
Re: RethinkDB is shutting down
#342Good move by Stripe to pick up these fantastic engineers.
Re: RethinkDB is shutting down
#343Re: RethinkDB is shutting down
#344Loved that they took care of the engineers! Stripe is a great place to work where their expertise is surely welcomed.
Re: RethinkDB is shutting down
#345Much respect for the no-BS announcement.
Re: RethinkDB is shutting down
#346To be clear: As part of shutting down, you guys found new jobs as you could for employees? That's rad!
For the engineers, it seems... Were there any other employees?
I didn't get that vibe from the article, tho.
Re: RethinkDB is shutting down
#347Earlier quoted context omitted.
Just looking at some of the RethinkDB and ReQL stuff, I certainly wouldn't have used it. Two things hit me immediately: - bad performance - a dearth of types (literally only a single numeric type that is a 64-bit float, so that eliminates entire categories that rely on integer/fixed-precision exact arithmetic. Also, time series are seriously hurt by that decision. I've seen DBs have to move to 64-bit longs because of…
> literally only a single numeric type that is a 64-bit float After dealing with JavaScript and Lua, I am ready to call this a complete anti-pattern. To be a good language, it must support at least one size each of machine floats and ints. To be really good, it should be possible for me to choose any size of machine-supported floats and ints. To be great, it should also support rationals, fixed-point and complex numb…
It's just as bad an idea now as it was then.
Re: RethinkDB is shutting down
#348A while ago, I heard how good RethinkDB is and tried to check it out and found this page. https://rethinkdb.com/docs/sql-to-reql/javascript/ The more complex the query becomes I just felt everything was getting less intuitive compared to the SQL version and ended up not actually using it. For anyone who switched from SQL, I'd like to know how it felt to write RethinkDB queries. Did they start to feel fluent later on?
Very. The linear flow of data from left to right made it very easy to reason about complex queries.
Re: RethinkDB is shutting down
#349That is sad. We were considering switching to RethinkDB from MongoDB.
Don't write off RethinkDB yet.
Re: RethinkDB is shutting down
#350Earlier quoted context omitted.
yeah. RethinkDB is AGPL, which means that some people cannot use it (e.g. http://www.theregister.co.uk/2011/03/31/google_on_open_sourc... ). While a very well grounded interpretation says that merely using the AGPL'd service via a public API doesn't force you to release the clients, some companies would prefer buying a commercial license rather than facing the legal risk.
"yeah. RethinkDB is AGPL, which means that some people cannot use it" No, it means some people CHOOSE not to use it. There is nothing stopping them from deciding to use it, other than their own fears.
What the lawyers decide in a company that has 10k+ employees has nothing to do with the fears of anyone but the lawyers and the top management. Everyone else is just following the rules.