4 ms·

Not quite. PackageCompiler isn't automagic. The sysimage doesn't get automatically updated in the REPL. You have to create one manually (and this requires traci

Not quite. PackageCompiler isn't automagic. The sysimage doesn't get automatically updated in the REPL. You have to create one manually (and this requires tracing instead of static type inference which Julia can do). So the workflow isn't zero-friction. And StaticCompiler hasn't been updated in over a year. The problem with Julia tooling in general is that they feel 90% done. And tooling is, in my opinion, more important than the language itself.

eigenspace 5y ago
> So the workflow isn't zero-friction. And StaticCompiler hasn't been updated in over a year. There's much more recent work here: https://github.com/tshort/StaticCompiler.jl/pull/46 https://github.com/tshort/StaticCompiler.jl/pull/46 and apparently some more is still ongoing privately. That said, yeah. I would not recommend Julia currently for people who truly believe they need AOT compilation, and that they need to trigger AOT compilation very often and with low friction. That definitely needs more work, but it's happening. That said, a lot of people overestimate how much they actually need AOT compilation. Julia has some fantastic tooling in other areas though. Especially the package management and interactive analysis tools.