A dummy question from a rainy sunday morning…
I use Julia for two different kinds of work:
- Heavy Computations (as a replacement for C++/Fortran…)
- Light Computations (as a replacement for Python/Matlab…)
That is great to have a single expressive language to do both ! My “mental load” is much lower
I must confess that, coming from C++, I am already very satisfied with the Julia language and the compiler state (perf and speed). I wait serenely PARTR to be released and I already wrote that the ability to produce Julia dynamic libraries would be great to incorporate in C++ applications.
Long start-up times for light computing (e.g. casual plotting) are not too problematic for my usual workflow, but I see that it is an annoying problem for a lot of Julians.
If I understand correctly, the path taken to reduce this start-up time (compile time?) is to compile faster or to cache more compiled parts. I naïvely wonder why it is not possible to go the other way and have a fully interpreted mode with no compilation at all (Python?) for light computations (plots). Or an automatic compilation starting when a repetitive computation happens to be long enough for the compilation being amortized (Java?).