For me, it used to be Jupyter Notebook. For reasons I cannot pinpoint, I never got convinced to JupyterLab. Sometimes I use Google Colab, primarily for sharing and using GPU for deep learning. Now, when I run it locally, I do it in Visual Studio Code (https://code.visualstudio.com/docs/datascience/jupyter-noteb...), since I don't need to jump back and forth between it and the rest of the code.
The vscode version, for me, has tended to be a better experience, with fewer random disappointments [0], than the pycharm version. Which is a shame, because the pycharm version, if it got at least as good as pycharm generally, would probably be better imo. But I hear that the new jetbrains notebook ide is the one getting the love
[0]:
- random unusable scrolling with vim mode
- gg scrolls to top of notebook rather than top of cell
- seemingly more-limited refactoring
- ipykernel headaches when I’ve already specified the project interpreter
- randomly cell contents get erased on cell execution
- wsl headaches (allowing firewall exceptions for each new project)
- windows jupyter headaches (having to manually terminate jupyter sometimes to quit the ide)
- sometimes the debugger gets stuck fetching variables before displaying them
- some kind of incompatibility between non-pycharm-created notebooks possibly related to nb format version so they can’t be read
- removal of (ui affordances for?) the cell mode for scripts?
I repeatedly ran into bugs and unpleasant behaviours in the VSC version, so I stick with browser notebooks. I did not find the lab version to be an improvement either.
For me, it used to be Jupyter Notebook. For reasons I cannot pinpoint, I never got convinced to JupyterLab. Sometimes I use Google Colab, primarily for sharing and using GPU for deep learning. Now, when I run it locally, I do it in Visual Studio Code (https://code.visualstudio.com/docs/datascience/jupyter-noteb...), since I don't need to jump back and forth between it and the rest of the code.