[stared]

I am curious how do you use Jupyter?

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.

[tempaccount420]

Same here - VS Code or Google Colab if I need an Nvidia GPU. I wish I could get Google Colab's GPU in VS Code, like Paperspace lets you do: https://docs.paperspace.com/gradient/notebooks/notebooks-rem....

[pizza]

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?

[macleginn]

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.

[d0mine]

I use jupyter using org-babel inside emacs.

https://github.com/emacs-jupyter/jupyter#org-mode-source-blo...