Wakari (by the continuum folks) seems to be more of a web notebook ontop of python, where you run the python code
the oxdata stuff seems to be more of "interact with a hadoop cluster via a restful api via R" kinda thing.
the 0xdata stuff seems to be less easily extensible because of that strong separation / siloing. (though it looks like they have some really smart interesting folks on board!)
[edit: I'm working on building some scalable extensible numerical / data analysis tools myself, and whenever I see that partitioning between the tools for extending vs the tools for using, it just screams "wrong" to me. That said, the more everyone else focuses on businesses where that partitioning is normal, the more left for me :) ]
Thanks for clarification! How do they approach interactivity with "big data"/hadoop(Hbase I presume)? Apache Drill is still draft/wip, Impala is not that fast from what I hear (for interactive)... unless they pre-calculate some use cases, but how would that constitute (semi)real-time interaction with hadoop. MR by its nature is not very real-timey.
As far as I can tell, this is a different vision than that of Wakari. This effort seems to be about building a souped up parellel ML-oriented calculator around Hadoop. There is an R binding, there is a nascent Python binding (that "doesn't include the Python scientific frameworks because [they] are not that familiar with them"[1].
Wakari is an infrastructure for doing repeatable, collaborative analytics with Python. Our existing tools include a simple browser-based environment for code editing, IPython notebook, and sharing of plots and workflows. Our goal is to support multiple applications on that infrastructure, and not necessarily all written by Continuum.
