Building a PC optimized for "time to first plot"

[anon56330260]

@Krastanov

I am surprised you are saying this as if there is a gotcha in the claim. I would have thought that “package has broken precompilation” is certainly included by everyone in the list of what makes a package “broken and/or unreliable”. This is probably the root of our misunderstanding.

No, No. I would not be surprised that you guys broadly accept this claim, in order to rule out those “strange packages” and to pave way for static compilation. But still, people need to fight for precompilation problems, as some packages cease to precompile and segfaults, even if they work pretty fine in the absence of precompilations. And don’t forget that precompilation is a rather opaque and only recently documented feature.

@Krastanov

You are now also raising an unrelated point: that rebuilding is not incremental / separate. Sure, it is annoying that you need to rebuild your sysimage, but that seems pretty normal: I do recompile my C/C++/Rust code when I change it for instance. But things are even better for Julia’s future: that type of recompilation would not be necessary for much longer as a set of developers (e.g. Keno) have prototypes for incremental sysimage (re)builds and another set of developers (e.g. Tim and Valentin) have prototypes that cache precompiled code much better even without a sysimage.

And I also make a prototype on incremental compilation in Julia, BuildSystem.

And I have only one question : why do you believe that any of these solutions can address the latency problems and maybe achieve something better than static languages, which is well-tested and deployed in large-scale? Do you try any of the prototype and indeed observe a huge speedup, or you get the conclusion from some theoretical reasonings?