sage

RETHINKDB: - There is a recent discussion about whether or not RethinkDB is dead here: https://github.com/rethinkdb/rethinkdb/issues/6747 - Judging by new PR's and commits, Rethinkdb development slowed down substantially in Jan 2016. SAGEMATH: - SageMath development is still very active; maybe more so, due probably to strong Europe grant support (OpenDreamKit): https://github.com/sagemath/sage/graphs/contributors SAGEMATHCLOUD: What this blog post is "really" about. - We renamed it "CoCalc" -- https://cocalc.com - I rewrote everything that depended on RethinkDB using PostgreSQL. Though it was months of work, this was obviously a VERY good decision in retrospect! - I rewrote all the realtime sync functionality to not depend on the database at all (just use a custom protocol over websockets), which is obviously a much more scalable approac

I started Sage, and worked on it a huge amount 2004-2012, but less so recently (due to working mostly on CoCalc). Actual contributions to and work on Sage by the community have gone UP a lot since 2012, as this plot (https://github.com/sagemath/sage/graphs/contributors) at Github shows. Much of that work is from research mathematicians that are adding large swaths of important functionality (e.g., in differential manifolds) to Sage. But there's also a very welcome push for quality, e.g., the number one recent contributor, fchapoton, has been fixing every little detail in the codebase revealed by https://lgtm.com/ and other tools, and there's also been a lot of work to fully transition Sage to Python 3 (which is difficult since so much is written in Cython and make nontrivial use of comparisons). I would have likely made Sage pip-in