IDE-ntity Crisis: Choosing the Right Tool for Me
summary
Compares JupyterLab, VS Code and Positron by concrete features: notebooks and widget compatibility in JupyterLab; VS Code’s extensions and %%-powered interactive window; Positron’s iPython console with line‑by‑line Command+Enter, support for running Python 3.11 and 3.13 side‑by‑side, and a data explorer that opens CSV/Parquet without installs and scales to millions of rows and columns. Highlights the Data Wrangler for hundreds‑to‑thousands of rows, the convert to code export, multiple virtual environments, and rename refactor that actually saves time.
AI-written summary · about
chapters (11)
- 0:00IDE selection for data scientists
- 1:48IDE soulmate quiz
- 3:35JupyterLab for notebooks
- 5:26VS Code with extensions
- 6:54Positron’s Python console
- 8:02Data exploration with small datasets
- 9:30Data explorers for large datasets
- 10:37Virtual environments management
- 12:05Quarto document authoring
- 14:14Breaking the one-IDE mindset
- 15:54Q&A
related talks
49mBest tools for Jupyter notebooks
21mEnd-to-end data science with the Positron IDE
01h 18mIntroducing Positron, a new data science IDE
40mJupyterLab: The Evolution of the Jupyter Notebook
40mJupyterLab: Building Blocks for Interactive Computing
30mNotebooks in VS Code
07mJupyter Notebooks in Visual Studio Code
25mOvercoming 5 Hurdles to Using Jupyter Notebooks for Data Science, by the JetBrai...