4 ms·
It does not have a tracing JIT, and its speed is by far not the only benefit. See link below It can precompile very fast code before runtime. Python will requ
by whyrt12 10y ago
It does not have a tracing JIT, and its speed is by far not the only benefit. See link below
It can precompile very fast code before runtime.
Python will require an interpreter and or hefty runtime.
https://discourse.julialang.org/t/julia-motivation-why-werent-numpy-scipy-numba-good-enough/2236/10?u=mikeinnes https://discourse.julialang.org/t/julia-motivation-why-weren...
- fnord123 10y agoForgive me, it's not a tracing JIT but just LLVM's JIT. Precompiling in Julia is extremely not-straight-forward. You would think you just use --compile and it would work; but it doesn't at all. Also, at ~850kb, Python's runtime is not that hefty. It's intended to be embedded and while it's quite a bit larger than lua's 200kb, but smaller than libjulia's 16mb.
- statsmatscats 10y agoRight, It can currently precompile to some extent, but full source-to-binary-blob-compilation is on the roadmap. See here: http://juliacomputing.com/blog/2016/02/09/static-julia.html http://juliacomputing.com/blog/2016/02/09/static-julia.html Julia's runtime includes its compiler and full huge standard lib, but of which are eventually going to be split off, IIUC. The former because of static compilation potential and the latter into modules that can be included piecemeal.