# 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:** 25

<div class="post-metadata">

### Author: ![FedericoStra](https://avatars.discourse-cdn.com/v4/letter/f/76d3ee/32.png) [@FedericoStra](https://discourse.julialang.org/u/FedericoStra)
#### Post date: [November 24, 2020, 11:25am UTC](https://discourse.julialang.org/t/will-julia-ever-fix-its-using-latency-problems/50659/25 "2020-11-24T11:25:43Z")

</div>

Pluto.jl is nice, but it has its own limitations (you cannot sequentially modify a variable like you would in a script) and is not suitable for developing a package. Here I was talking about the workflow of developing a module, in the old fashioned way of writing in a text editor and experimenting in an interactive terminal session. For that, Revise is not enough and I keep having to restart the session whenever I touch a `struct` or a global constant. I don’t even know why they are treated differently from functions; it seems to me that it should be more difficult to update/delete functions. When working on a script, `Revise.includet` is pretty useless: it doesn’t redefine any data, it only updates functions, so you have to use `include` anyway.

---

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