4 ms·
As mentioned, we have had collaborative editing with full history for Jupyter notebooks since 2014 in https://cocalc.com https://cocalc.com, which is open sourc
by williamstein 9y ago
As mentioned, we have had collaborative editing with full history for Jupyter notebooks since 2014 in https://cocalc.com https://cocalc.com, which is open source by the way. We've written and rewritten this functionality 3 times now, culminating most recently with a complete front and backend rewrite of Jupyter from scratch for CoCalc. See http://blog.sagemath.com/jupyter/2017/05/05/jupyter-rewrite-for-smc.html http://blog.sagemath.com/jupyter/2017/05/05/jupyter-rewrite-... for more details. We also still support collaborative editing using Classical Jupyter.
- j_s 9y agoNice! How much of this made it back into Jupyter proper? I'm always interested in the "rubber meets the road" aspects of commercialized open source development. Your project looks perfect for helping people learn how to code.
- williamstein 9y agoI'm in close communication with many Jupyter developers, got a lot of help and feedback from them, and I hope I influence their direction in some cases. We view CoCalc Jupyter as another Jupyter client in the Jupyter ecosystem (much like nteract, Google Collaboratory, etc.); the implementation framework of CoCalc Jupyter is React.js, so the main code sharing is with Nteract, rather than classical Jupyter. Regarding commercialized open source, Nteract is another Jupyter client who development is funded by a company (currently mainly Netflix).