[argd678]

Mainly, am I going to spend hours fussing with the basics of the language. For example in R, it’s too slow, so I had to write Rcpp, only to discover there’s no real way to debug it from RStudio, down into the rabbit hole, lldb, Rinside, everything that can crash does, terse errors messages with out line numbers, opaque SEXP types XCode can’t decode etc. So basically are the normal everyday use cases fraught with quirks you need to know more about the internals of Julia or can you just be a user? If that makes sense.

[endoftime5]

“Writes like Python runs like C” is one tagline I’ve seen them use. Julia gives you a lot of control over how fast you want your code to be. You can write some code without really thinking too much and it’ll be fast and work just fine. If you get to a point where it’s not fast enough then there’s a whole host of tools to help you speed it up.

At any stage you can call @code_{warntype, lowered,...} and inspect exactly what code has been produced by the compiler to find bottlenecks.

I’ve not written much R before but in my experience I’ve never had to go to those lengths to debug Julia code! (Although the error messages can sometimes be a bit of a mouthful, I think because it uses LLVM)