# Will Julia ever fix its "using ..." latency problems?

**URL:** <https://discourse.julialang.org/t/will-julia-ever-fix-its-using-latency-problems/50659>\
**Category:** Performance\
**Created:** [November 23, 2020, 11:57pm UTC](https://discourse.julialang.org/t/will-julia-ever-fix-its-using-latency-problems/50659 "2020-11-23T23:57:55Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [November 24, 2020, 11:26am UTC](https://discourse.julialang.org/t/will-julia-ever-fix-its-using-latency-problems/50659/26 "2020-11-24T11:26:40Z")

</div>

> [@Volker\_Weissmann](#):
>
> This makes Julia nearly unusable.

I don’t think that Julia will replace completely scripting languages, because those will be always faster if the loading time is the critical part of the script.

At the same time, maybe you know these details already and people have mentioned them, but sometimes the problems are mostly about finding a good workflow. I have recently posted this in another thread, it is basic stuff and might be useful:

> [@Julia REPL flow coming from Matlab](https://discourse.julialang.org/t/julia-repl-flow-coming-from-matlab/50499/5):
>
> As Elrod mentioned, there is no such thing as a “clear”, but you can redefine you variables at will: data = [1, 2, 3] f(data) data = [2, 3, 4] f(data) Assuming that your data is constant, as you described initially, you could very directly just load a script repeatedly with the analysis and plotting/report functions, as you fiddle with the analysis functions, something as: include("set\_data.jl") include("analyze.jl") include("report.jl") #--- change something in "analyze.jl" include("anal…

---

_[View the full topic](https://discourse.julialang.org/t/will-julia-ever-fix-its-using-latency-problems/50659)._