33 ms·
That's mostly because Julia doesn't have yet an interpreter (outside of the debugger), only a JIT compiler. Thankfully the "time to first plot" is the new prior
by ddragon 7y ago
That's mostly because Julia doesn't have yet an interpreter (outside of the debugger), only a JIT compiler. Thankfully the "time to first plot" is the new priority for the compiler team since the multithreading is already working.
- BubRoss 7y agoI hope it goes well, this has been a common complaint for half a decade now.
- krastanov 7y agoThis is a rather unfair statement given that the first stable version of Julia was released only a year ago.
- BubRoss 7y agoThere has been a lot of other work over the last five years with a constant stream of new people talking about iteration and start up times with constant promises that it will be fixed soon.
- reikonomusha 7y agoMost Common Lisp compilers survive well with incremental compilation. Build-times and development are very fast, with no interpreter in sight.
- ddragon 7y agoThere are many approaches they could go, they could improve the live session approach (for example saving between sessions), which could also help people who repeatedly run scripts on the bash (for example with a --save-session flag). It wouldn't solve the very first plot but it would help all "first plot within the current run", which is probably most of the complaints. The one that people would probably appreciate the most would be an AoT alternative (allowing you to create a runnable/linkable binary with a function/module without embedding the compiler, at the cost of the dynamic features such as eval).
- 6thaccount2 7y agoYea, but common lisp is also missing nearly all the numerical libraries I need like sparse matrices. Yes, I'm sure someone has a wrapper somewhere, but Julia has native support for all of that and is really nice. It also has much better support for a lot of things like plotting.
- elcomet 7y agoThat's nice, thanks for the information !