# Compiling and leaving it alone until we decide to change?

**URL:** https://discourse.julialang.org/t/compiling-and-leaving-it-alone-until-we-decide-to-change/63246
**Category:** New to Julia
**Created:** [June 20, 2021, 5:07pm UTC](https://discourse.julialang.org/t/compiling-and-leaving-it-alone-until-we-decide-to-change/63246 "2021-06-20T17:07:23Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)
#### Post date: [June 30, 2021, 12:10pm UTC](https://discourse.julialang.org/t/compiling-and-leaving-it-alone-until-we-decide-to-change/63246/5 "2021-06-30T12:10:57Z")

</div>

> [@skypuppy](#):
>
> Seems to me that JIT EVERY time one starts a program is an enormous waste of user time just so we can call Julia “dynamic,”

Certainly Julia will cache more compiled code in the future, as well as other techniques to decrease load time. Implementing this takes time because Julia’s dynamic nature makes it tricky, but the Julia developers are well aware of the desire to improve load times and are steadily making things better with each release.

This has been heavily discussed (e.g. see [Roadmap for a faster time-to-first-plot?](https://discourse.julialang.org/t/roadmap-for-a-faster-time-to-first-plot/22956)) and it probably isn’t productive to discuss it again. Meanwhile, see this post for how Julia users typically avoid it now simply by using long-running interactive sessions: [Time to first plot clarification - #2 by stillyslalom](https://discourse.julialang.org/t/time-to-first-plot-clarification/58534/2)

---

_[View the full topic](https://discourse.julialang.org/t/compiling-and-leaving-it-alone-until-we-decide-to-change/63246)._