3 ms·
Pluto.jl does solve the state problem of notebooks, which is the biggest problem in them. Probably should give it another go. How is the module reloading story
by jampekka 3y ago
Pluto.jl does solve the state problem of notebooks, which is the biggest problem in them. Probably should give it another go.
How is the module reloading story nowadays? Last time I gave up the state of the art was Revise.jl, which was a world of pain.
- staunton 3y ago> Pluto.jl does solve the state problem of notebooks Yes it does, unless you do crazy stuff (which you probably should put in a Julia file and let it precompile). The order of cells and execution order does not matter (unless you do crazy stuff).
- markkitti 3y agoA Pluto.jl notebook is also a regular file. You need to use a package for precompilation caching though.
- tamasgal 3y agoI have no idea what kind of problems you have ;) I use Revise.jl on a daily basis and it works flawlessly. I don't have any comparable workflow in any other language I work with on a daily basis. I wish I could do this style in those as well... Yes, you should give it a go (again)!
- staunton 3y agoI'm not sure how Revise would work with a notebook though... Guess it's only useful in the REPL, which is a different way to work.
- bobbylarrybobby 3y agoIn VSCode, in an ordinary Julia file you can place the magic comments `# %%` at the start of a code cell (needs to be on its own line), and then you can send these “cells” to the REPL to execute. No notebook needed.
- staunton 3y agoWhat do you do with it? Especially that benefits from Revise?
- jampekka 3y agoFor example these: https://timholy.github.io/Revise.jl/stable/limitations/#Limitations https://timholy.github.io/Revise.jl/stable/limitations/#Limi...