I get this even less: -- For 1, that's analogous to having every python package via pip/conda, and the same for other juypter langs. -- For 2, this is scary/h

I get this even less: -- For 1, that's analogous to having every python package via pip/conda, and the same for other juypter langs. -- For 2, this is scary/hard for traditional notebook usecases. IPython gives the user control, so there is no fear of beach balling & unintentional outside effects. I do appreciate the intent however :) -- For 3, a notebook is just a json file and shareable. In fact, you can share a python notebook with a js app and it'd still work. With maybe 50loc, you can even keep the require syntax. -- For 4, we're doing this within juypter just fine, and bokeh as well. We recently went through a similar decision making process, and, when thinking about the above and more, decided it'd be better for the community for us to add features to Juypter than make yet another notebook. I don't think Juypter is the end-all (though for none of the reasons above), so I'm still confused here.