> I don't get why you want to use this over an IDE. All you get is cached intermediate variables and being able to print them, am I right?
You get more than that from Jupyter. Especially with Python, but for Go also.
Jupyter is for exploration and prototyping. Think of Jupyter as being a massive improvement on the command line shell, rather than an IDE downgrade. If you're developing large structured programs, yes the IDE is definitely the way to go. But if you're doing interactive coding and you want to run the code line by line or in small groups, you'd use the shell, or better yet Jupyter. Jupyter is between an IDE and a shell.
Jupyter gives you inline images & plots. It's made with visual results and interactive plotting in mind. Most IDE's don't have anything like that. You can also compare Jupyter to Maple or Matlab or Mathematica.
Jupyter lets you add readable formatted markdown between code blocks, and you can export your notebook in presentation formats like PDF or HTML.
Notebooks show the results of the program run, so someone you share with can see what happened before they run the code.
And I don't know about the Go kernel, but with Python at least, Jupyter most often installs a sandbox environment that includes several powerful Python libraries. What this means in practice is that sharing notebooks is vastly easier for the recipient of a notebook.
1. That's very misleading, because what PyCharm did was add support for jupyter notebooks. Without iPython/Jupyter there would be no "interactivity and cell based execution" in PyCharm.
2. And AFAIK it's just Python, does it support the few dozens other jupyter kernels?
1. No, it's not. In regular python files you can create cells using #%% and run them separately. Yes, there is also notebook support but it requires Jupyter.
You get more than that from Jupyter. Especially with Python, but for Go also.
Jupyter is for exploration and prototyping. Think of Jupyter as being a massive improvement on the command line shell, rather than an IDE downgrade. If you're developing large structured programs, yes the IDE is definitely the way to go. But if you're doing interactive coding and you want to run the code line by line or in small groups, you'd use the shell, or better yet Jupyter. Jupyter is between an IDE and a shell.
Jupyter gives you inline images & plots. It's made with visual results and interactive plotting in mind. Most IDE's don't have anything like that. You can also compare Jupyter to Maple or Matlab or Mathematica.
Jupyter lets you add readable formatted markdown between code blocks, and you can export your notebook in presentation formats like PDF or HTML.
Notebooks show the results of the program run, so someone you share with can see what happened before they run the code.
And I don't know about the Go kernel, but with Python at least, Jupyter most often installs a sandbox environment that includes several powerful Python libraries. What this means in practice is that sharing notebooks is vastly easier for the recipient of a notebook.