In response to

State of the Debugger Usage Hi there, I just wanted to ask about the state of the debugger in Julia. I am coming from Matlab and the debugger there is quite important for me to see where something is going wrong. For example, using NLsolve is a bit of a black box for me. If it does not work, I don’t know where to start to look for the problem. In contrast, in the meantime I copied the code to Matlab and could stop during the the execution of fsolve and check what is going wrong. Now it works in Matlab, but still it does n…

I thought I might write a little post about the rough priorities of the compiler team:

Julia 1.0 introduced a new compiler and there were inevitably various bugs and issues, so the first order of business is fixing those.

Multithreading is the next highest priority because we want to merge the new parallel runtime as soon as possible and allow people to start writing and using threaded package code before things get too far along. Ecosystems for single-threaded languages tend to start to bake that assumption in very deep if they’re around for too long. Julia’s package ecosystem is small enough and young enough that if we introduce proper multithreading soon, it will adapt quickly.

Compile-time latency is clearly a huge pain point for all Julia users, so that’s quite important.