4 ms·
We switched from Python to Julia for numeric code. It's generally much faster (and easier to optimize), and has slightly better syntax for mathy code. It's wor
by SatvikBeri 2y ago
We switched from Python to Julia for numeric code. It's generally much faster (and easier to optimize), and has slightly better syntax for mathy code.
It's worth noting that Julia is very similar to go, despite superficial differences. They're both small languages with big libraries, use the same concurrency model, use a mark-and-sweep GC with an emphasis on making it easy for the programmer to reduce garbage/allocations, and both use structs + functions rather than classes.
- blt 2y agoJulia looks like a great language, but has the "time to first plot" issue been fixed yet? I don't want a REPL-centric workflow.
- SatvikBeri 2y agoIt's vastly faster than it was before (~5s compared to ~40s for the Plots package, and much less for most workflows) but it can never drop to 0, since it's compiling each function the first time you use it. Though honestly if you don't want a REPL or notebook-centric workflow, I would probably recommend a different language.