Depends a bit. More traditional tools like static analysis/Debuggers/full fledged IDEs are somewhat lacking compared to your standard static programming language. Although there’s very good progress being made with JETLS on the static analysis part, and the VSCode extension is very mature.
replyBut, on the other hand, you rarely need those kind of tools with Julia. The REPL+Revise in Julia is most often all you need. If you really want to jump into running code debugger style you have Infiltrator.jl
And in the year of our lord 2026, I’ll say that agents are very effective in debugging Julia, especially paired with persistent sessions/daemons like DaemonicCabal.jl or JuliaDaemon.jl.
While I agree that agents can do pretty much all the coding, I still would love to learn to work with the language myself --- Julia was supposed to be a human-friendly/human-first programming language, with elegant syntax and all that, so it would be a pity not to try it as a human programmer.
replyOh yeah absolutely. One of my favourite ways to interact with agents is to spin up an interactive common session where both me and it can run commands in a shared environment. You can ask the agent to setup a MWE for you to play with and further explore in the REPL for example.
replyI used it for a few hobby projects in VSCode. It's not 100% smooth, e.g. I couldn't compile and run my code with a single shortcut. It's supposed to be possible to show graphs in VSCode but I couldn't make that work.
replyDebugging worked quite good. I didn't look for static analysis.
But I find programming in any language in VSCode less polished, compared to e.g. programming C++ with Visual Studio, which works out of the box.
What type of programs have you been writing?
replyI wouldn't call them experimental. They just suck IMO, and that's my biggest gripe with using Julia, as language alone is nice, especially with slowly improving AOT. Of course you will also get replies with completely opposing views, so there is no other way than trying it yourself.
reply