RETHINKDB: - There is a recent discussion about whether or not RethinkDB is dead here: https://github.com/rethinkdb/rethinkdb/issues/6747 https://github.com/re

RETHINKDB: - There is a recent discussion about whether or not RethinkDB is dead here: https://github.com/rethinkdb/rethinkdb/issues/6747 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 https://github.com/sagemath/sage/graphs/contributors SAGEMATHCLOUD: What this blog post is "really" about. - We renamed it "CoCalc" -- https://cocalc.com 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 approach to this problem. RethinkDB (and anything like it) is totally the wrong tool for implementing realtime sync for file editing. - Development on CoCalc is very active: https://github.com/sagemathinc/cocalc/graphs/contributors https://github.com/sagemathinc/cocalc/graphs/contributors Disclaimer: I wrote this blog post and started Sage and CoCalc. I didn't repost this here, and just happened to notice it while scanning HN.