3.1 Development Environments

Before we can dive into the language syntax, we need to answer how to run code. Going into details about the various options is out of scope for this book. Instead, we will provide you with some pointers to various solutions.

The simplest way is to use the Julia REPL. This means starting the Julia executable (julia or julia.exe) and running code there. For example, we can start the Julia REPL and execute some code:

  1. julia> x = 2
  2. 2
  4. julia> x + 1
  5. 3

This works all very well, but what if we want to save the code that we wrote? To save our code, one can write “.jl” files such as “script.jl” and load these into Julia. Say, that “script.jl” contains:

  1. x = 3
  2. y = 4

We can load this into Julia:

  1. julia> include("script.jl")
  3. julia> y
  4. 4

Now the problem becomes that we would like Julia to re-read our script every time before executing code. This can be done via Revise.jl. Because compilation time in Julia is often long, Revise.jl is a must-have for Julia development. For more information, see the Revise.jl documentation or simply Google a bit if you have specific questions.

We are aware that Revise.jl and the REPL requires some manual actions which aren’t super clearly documented. Luckily, there is Pluto.jl. Pluto.jl automatically manages dependencies, runs code, and reacts to changes. For people who are new to programming, Pluto.jl is by far the easiest way to get started. The main drawback of the package is that it is less suitable for larger projects.

Other options are to use Visual Studio Code with various Julia extensions or manage your own IDE. If you don’t know what an IDE is, but do want to manage large projects choose Visual Studio Code. If you do know what an IDE is, then you might like building your own IDE with Vim or Emacs and the REPL.

So, to summarize:

  • Easiest way to get started -> Pluto.jl
  • Larger projects -> Visual Studio Code
  • Advanced users -> Vim, Emacs and the REPL

3.1 Development Environments - 图1 Support this project
CC BY-NC-SA 4.0 Jose Storopoli, Rik Huijzer, Lazaro Alonso