The First Notebook War
summary
A public spat claims notebooks break basic software engineering—modularity and code reuse—while proponents show concrete fixes: JupyterLab as an IDE, Jupytext to pair scripts and notebooks, Binder and Google Colab to launch reproducible environments (Colab offering free GPUs), nbdime for notebook diffs, and R Markdown as a plain‑text alternative friendly to version control. The argument produces tooling, examples of pipelines and paired script workflows, and no clear winner—practice and tooling decide.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:31Origin of the war
- 5:04What are Jupyter Notebooks
- 6:32Criticism of Jupyter
- 9:01JupyterLab advantages
- 10:48R Markdown alternative
- 11:52Why use notebooks
- 13:20Notebook tools and platforms
- 15:53Working with scripts
- 16:37Better Python modules
- 19:54Project structure and deployment
- 20:56Q&A
related talks
17mNotes on Notebooks: Is Jupyter the Bringer of Jollity?
33mSignificant Roadblocks to Usefulness for Jupyter Notebooks and a Recipe to Fix them
28mUnlock the Full Potential of Jupyter Notebooks
25mOvercoming 5 Hurdles to Using Jupyter Notebooks for Data Science, by the JetBrai...
49mBest tools for Jupyter notebooks
40mJupyterLab: The Evolution of the Jupyter Notebook
28mCollaborate with your team using data science notebooks
41mBetter Code for Data Science
