[pdeffebach]

Plenty of people use the REPL in terminal and sublime text or vim or whatever. I also dislike browser-based tooling and think Julia has done a good job avoiding Rstudio-style dependencies.

But if your point is the inability to do `julia script.jl` , yeah thats a pain point. Fortunately there has been some tooling to make running many jobs in a row easier: https://github.com/dmolina/DaemonMode.jl

[leephillips]

How is it that I do `julia script.jl` all the time? Or by “inability” do you mean that it’s slow because of the startup time? If you need a utility that starts up instantly, create a sysimage.

[snicker7]

In contrast to interpreted languages, creating a sysimage is yet another step (in addition to installing a third party package).

In contrast to AOT-compiled languages, PackageCompiler.jl doesn't statically analyze your code. So you need a "precompile script" that hopefully hits all callable methods (such a script will have to be made manually). The resulting "binary" is also massive.

[pdeffebach]

Yeah people in python are used to doing `python script.py` all the time, and that's not very convenient in julia.

sysimages are great, as is daemonmode. But really just do Revise at the REPL.

[nerdponx]

Right.

I was also a bit harsh; you can at least do `julia -e 'using Pluto' -e 'Pluto.run()'`.

[Bootvis]

What do you mean by “RStudio-style dependencies”?

[pdeffebach]

Just that there seems to be an expectation of using Rstudio when using things in R that seem generic.

One pain point is that Rmarkdown uses a different pandoc installation when executed by Rstudio than from the terminal.