Nextjournal - Seamless data science for teams

@nikgraf All that's open source currently is our notebooks that build the environment images https://nextjournal.com/nextjour... (and follow the links to e.g. the Python environment https://nextjournal.com/nextjour...). Our larger open source strategy is still undecided, we're not sure what parts we will open source or under what license. At the moment we're using a monorepo for development, so open sourcing parts would have some overhead and we're focusing on delivering a useful product for the moment. A third option we're considering is moving more and more platform code into Notebooks on the platform, effectively bootstrapping Nextjournal. Like I've written above this is already the case for all environment images but we're expanding that to runtime code and more. But it's too early to tell to what extent that will work.

@sidazhang starting out our code evaluation was quite a bit different than Jupyter, it was more a data flow model between cells but today we're more in line with how cells work in Jupyter. We did realise over time that interop with Jupyter and RStudio is critical and have added Jupyter import and kernel support.

@mengxilu Nextjournal is not built on top of Beaker or Jupyter. It’s a fully integrated system designed from the ground up to enable automatic versioning of the notebook, data and the full computational environment (as Docker image). We support importing Jupyter notebooks however and we can also run Jupyter kernels. By default, though, we us our own runtime protocol. In its simplest form our protocol only depends on bash, whereas Jupyter needs a full Python installation in the container. This allows you to install any library or package in a Nextjournal notebook.