Good: Jupyter will hopefully stick around for a long time. I just spent a ton of working writing a new separate implementation of the whole compatible Jupyter

Good: Jupyter will hopefully stick around for a long time. I just spent a ton of working writing a new separate implementation of the whole compatible Jupyter stack for CoCalc, and Kyle Kelly at Netflix has similarly written another implementation for their use (see nteract). Ugly: My impression is that the current “jupyter extension” API is actually being deprecated in favor a completely different presumably better API that JupyterLab will use. I think the Jupyter devs have a vision that involves everybody rewriting all their extensions against a new API... Regarding extensions, CoCalc also can’t possibly work with Classical Jupyter notebook extensions, so I personally plan to rewrite several popular extensions for CoCalc (I’ve done some already). Bad: The Jupyter project seems to be very heavily funded and reliant on Moore/Sloane/NSF. I know that Fernando Perez put a huge amount of effort into helping to get some of these grants, which are I think well over 10million total by now, and I think these grants fund numerous fulltime positions. I’m personally also worried that the grants will run out, not get extended, and the project will be in major trouble as a result. Fortunately, at least soem developers like Jason Grout and Chris Colbert are fulltime at companies (e.g., Bloomberg, maybe Continuum Analytics), so they have more stable funding. Also, CoCalc (my company) isn’t dependent on grants, and we will be around for a long time.