3 ms·
> I never needed speed when printing out stuff. > REPL should be much faster (especially importing libraries), and I'm not a fan of 1 based indexing, but every
by sam0x17 7y ago
> I never needed speed when printing out stuff.
> REPL should be much faster (especially importing libraries), and I'm not a fan of 1 based indexing, but everything else is awesome if you need great performance.
Then don't you want fast printing / string ops? REPLs heavily rely on that.
- taeric 7y agoSpeed on a repl is as much from not printing things as it is in printing them fast. At the least, always accept an interrupt to stop printing.
- kristofferc 7y agoIO and strings in Julia are very fast. The comment here in the blog post is about the (currently) 130ms overhead in starting up Julia.
- sam0x17 7y agoYeah regarding that, I do think start-up speed is important, especially in a data-driven workflow where you run binaries on a dataset.
- kristofferc 7y ago> run binaries on a dataset. That's not how (barely) anyone actually works with Julia when they do data-analysis though.
- staticfloat 7y agoThe implicit assumption in much of the Julia world is that the work being done on the dataset will dwarf the startup time; if your workload takes less than 100ms, it’s probably not worth spending tens of milliseconds on compiling your code in the first place, and you should run it with an interpreter. (Incidentally Julia does support that, but it requires a command-line flag, and can come with a heavy performance penalty if you are running numérica-heavy code)