everyone is different. I also recommend users take time to understanding every tool they use as much as time allows. We don't always have the luxury of time, but I see no point recommending laziness.
I'm probably insane, since I also spend time reading papers on CRDT, paxos, query compilers, machine learning and other topics I find fun. on the topic of multiple incompatible API's I recommend you look at SqlServer and Sybase. Most of the legacy RDBMS have multiple incompatible API. Though in some cases, it is/was unavoidable. On Wed, Jan 21, 2015 at 4:47 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Wed, Jan 21, 2015 at 9:19 AM, Peter Lin <wool...@gmail.com> wrote: > >> >> I consistently recommend new users learn and understand both Thrift and >> CQL. >> > > FWIW, I consider this a disservice to new users. New users should use CQL, > and not deploy against a deprecated-in-all-but-name API. Understanding > non-CQL *storage* might be valuable, understanding the Thrift interface to > storage is anti-valuable. > > Despite the dissembling public statements regarding Thrift "not going > anywhere" it is obvious to me that no other databases exist with two > non-pluggable and incompatible APIs for a reason. The pain of maintaining > these two APIs will eventually become not worth the backwards > compatibility. At this time it will be deprecated and then shortly > thereafter removed; I expect this to happen at latest by EOY 2018. [1] > > =Rob > [1] If anyone strongly disagrees, I am taking $20 cash bets, with any > proceeds donated to the Apache Foundation. > >
