Hacker News Reader

Comment by jampekka | Hacker News Reader

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.

View on HN

I 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)!

I'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.

In 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.

What do you do with it? Especially that benefits from Revise?

For example these: https://timholy.github.io/Revise.jl/stable/limitations/#Limi...

> 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).

A Pluto.jl notebook is also a regular file. You need to use a package for precompilation caching though.

Reply on news.ycombinator.com