Earlier quoted context omitted.
datetimes, aggregations, etc. pretty much anything non-toy in the modern world requires 64 bit int. like I said. read NEED as in you can certainly hobble around without it (pick an appropriate offset and read your 53 bits in relation to it), but like a fracture in a leg, it's still considered broken.
What exactly do you mean by aggregations here? If you want a good timestamp you probably want a timespec, and that won't fit in 64 bits anyway. I don't see why it's easy to make 128+ bit types be composite, but you can't have 64 bit types be composite. Your database driver can take care of how the bits are packed on the wire. It really shouldn't be a big concern.
RethinkDB is shutting down
421–430 of 457 posts
Re: RethinkDB is shutting down
#422Earlier quoted context omitted.
No, if I'm working at a company that has a blanket policy against using any (A)GPL software, then I can't use it. 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.
No, it's that your company is CHOOSING not to use it.
Re: RethinkDB is shutting down
#423RethinkDB is one of the developer tools that we at Stripe most looked up to.[1] The team had so many good ideas and rigorous, creative thoughts around what a database could be and how it should work. I'm really bummed that it didn't work out for them and have enormous respect for the tenacity of their effort. I'm also excited to have them join us here at Stripe. As we've gotten to know Mike, Slava, and the other Reth…
I secretly (not 'secret' anymore I guess) and irrationally trust Stripe to do good on RethinkDB. Also, TIL: Slava is defmarco. Yeah defmarco, that's how I read it for a long time. I especially love this piece from defmarco http://www.defmacro.org/ramblings/fp.html
Re: RethinkDB is shutting down
#424It seems that unfortunately RethinkDB the company was architected in such a way that the success of their product, in terms of performance and developer experience, led to a decrease in revenue. This shutdown therefore goes a long way to say how talented and ethically correct the team was, something extremely evident in how they put correctness and reliability in front of performance. In short, RethinkDB is a very so…
Re: RethinkDB is shutting down
#425Re: RethinkDB is shutting down
#426Earlier quoted context omitted.
MongoDB has received a huge amount of venture funding: $311M vs $12.2M for RethinkDB. That makes a big difference how far you can grow as a business if you use the money even half-way rationally. Given that the market for document DBMS is pretty small to begin with it's tough to beat a 25x difference in budget unless you have a product that is a complete game-changer. It will be interesting to see Slava's analysis. M…
I originally thought funding would play a big role, but the early, 2-3 year period of funding for both is comparable: RethinkDB, 2009-11 = $4.2MM MongoDB, 2008-2009 = $4.9MM It's true that MongoDB quickly closed on a $6.5MM Series C in Dec of 2010, one year after their Series B. For Rethink, it took them another 2 years to get the last $8MM. There's no question that MongoDB was "better" at raising more money, faster.…
Re: RethinkDB is shutting down
#427Earlier quoted context omitted.
Please dont make excuses for their failure. "Developer experience" and "performance" are never reasons for failure. What does lead to failure is - lack of mass adoption - they didnt solve a problem everyone had - lack of nitch adoption - they didnt solve a problem a few people had badly I can tell you 4 features that I view more important than change subscription - can run in any ecosystem - pouchdb/couchdb and water…
RethinkDB didn't fail because any of those things. As far as we can tell without an actual post mortem, it failed because RethinkDB -- the company -- didn't make enough money. Going by the public information on their website, the only way the company was making money from its product was via support and training. The problem with making money only with training and support is that it falls flat when the product and d…
In all seriousness the OP nailed the issue. The company is not successful because of the "issues" with the product. There is a very direct correlation there, stop trying to make it look like the failure of the company did not have anything to do with the product and that the product is perfect/popular/whatever.
Re: RethinkDB is shutting down
#428Earlier quoted context omitted.
That's an unfortunate license choice. No one will use it.
Not sure about no one but anything with gpl in the license is surely a dead end for some of us.
Re: RethinkDB is shutting down
#429Earlier quoted context omitted.
> Proprietary software is not by definition "user-hostile," Yes, it is: by definition it violates one of the Four Freedoms of users … which is hostile.
I disagree. Most of those are things that most users don't give a damn about in most cases (because they're meaningless unless you have certain unusual skills), which means they don't make for a sensible definition of "hostile".
Re: RethinkDB is shutting down
#430Earlier quoted context omitted.
"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.
No, if I'm working at a company that has a blanket policy against using any (A)GPL software, then I can't use it. 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.