'Pluto.jl vs Jupyter Notebook
What is the difference between Pluto.jl and Jupyter Notebooks?
How do I decide which I should prefer for teaching students?
Is there a performance difference?
I only found https://www.reddit.com/r/Julia/comments/kxdjzh/pluto_vs_jupyter_notebook/, which does not include many details.
Solution 1:[1]
From Pluto.jl github page:
A Pluto notebook is made up of small blocks of Julia code (cells) and together they form a reactive notebook. When you change a variable, Pluto automatically re-runs the cells that refer to it. ...
The main difference between using Pluto.jl and Jupyter Notebooks with Julia is that Pluto.jl is dynamic. It re-runs all the above cells according to the last cell. Whereas outputs of Jupyter Notebook only change when the code blocks that created them change
Solution 2:[2]
I find the largest pro of Pluto to be, that by design notebooks the same resuts. In Jupyter it is quite easy to create results that are dependent on the cell-execution order, which is hard to do in Pluto.
In jupyter you can chose to execute cells one-by-one, which can be beneficial, if you have large calculations going. This can not be done in Pluto, but one learns to take this into consideration, when writing notebooks.
Support for slides is very good for Jupyter. For Pluto only proof of concepts exist as far as I am aware.
Both are performant.
For teaching students I personally prefer Pluto. Some of the restrictions imposed make it much simpler to debug these notebooks (results do not depend on cell execution order). Also the notebook is basically a standard Julia source code file, which can be manipulated easily using any text editor. Pluto's Reactivity is also great in an educational setting, as it encourages students to play around with the notebooks. Lastly, there is the MIT course Introduction to Computational Thinking, which uses these notebooks for lectures and exercises and they are a great inspiration on how to use Pluto notebooks for teaching. I hope these insights are what you were looking for.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | osbm |
| Solution 2 | Martin Möddel |