# V1.10 appreciation thread
**URL:** https://discourse.julialang.org/t/v1-10-appreciation-thread/108103
**Category:** Community
**Created:** [December 27, 2023, 4:16pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103 "2023-12-27T16:16:15Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)
#### Post date: [December 27, 2023, 4:16pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/1 "2023-12-27T16:16:15Z")
I just want to say thanks for this release. I’ve been using it locally for months now, and going back to v1.9 just to test… man this is a major step forward.
- Load times are drastically better (order of magnitude for what I do with SciML)
- Parser messages are clearer
- Stack traces are no longer infinitely long! They are good and legible!
- VS Code auto-complete stuff is snappier and more predictive (I believe this has something to do with the parser change?)
Overall really solid release. Nicely done everyone involved!
---
### Author:  [@sob](https://discourse.julialang.org/u/sob)
#### Post date: [December 27, 2023, 6:35pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/2 "2023-12-27T18:35:18Z")
Agreed. rc2 started working very well on my side and I haven’t looked back.
---
### Author:  [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)
#### Post date: [December 27, 2023, 6:51pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/3 "2023-12-27T18:51:44Z")
> [@ChrisRackauckas](#):
>
> VS Code auto-complete stuff is snappier and more predictive (I believe this has something to do with the parser change?)
Unless @pfitzseb has done some secret work, I can’t think of anything that would have made any change on that front 🙂 The new parser in base is not used (yet) by the VS Code extension.
---
### Author:  [@yewalenikhil65](https://discourse.julialang.org/u/yewalenikhil65)
#### Post date: [January 3, 2024, 3:49pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/4 "2024-01-03T15:49:41Z")
Completely agree… For someone like me who started with Julia 1.4.0 , getting irritated with loading DiffEq.jl Plots.jl after +20 or +30 seconds or even more on my laptop …to now ~1 or ~2 seconds on same machine with Julia 1.10.0
Its a relief.
At some point i was seriously considering going back to Python for exactly this time to first load. It use to feel bad for seeing instant `import numpy` or `import matplotlib` but huge timelag for `using DifferentialEquations` or `using Plots.jl`
Also there is something satisfying about seeing parallel precompilation on htop application for mang packages
---
### Author:  [@JonasWickman](https://discourse.julialang.org/u/JonasWickman)
#### Post date: [January 3, 2024, 3:56pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/5 "2024-01-03T15:56:13Z")
Just adding on my appreciation too. Together, 1.9 and 1.10 have made such an enormous difference to the overall feel of working in Julia.
---
### Author:  [@Wen-Wei\_Tseng](https://discourse.julialang.org/u/Wen-Wei_Tseng)
#### Post date: [January 3, 2024, 4:24pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/6 "2024-01-03T16:24:13Z")
Same here. I noticed running Literate notebooks (using Plots.jl , DifferentialEquations.jl, Catalyst.jl, and ModelingToolkit.jl) on GitHub actions becomes significantly faster.
1.9.4: [4m7s](https://github.com/ntumitolab/mmsb-bebi-5009/actions/runs/7224815926/job/19686918954)
1.10.0: [1m52s](https://github.com/ntumitolab/mmsb-bebi-5009/actions/runs/7375899364/job/20068011691)
The workflow also showed a trick (hack?) that using [GitHub - abelsiqueira/jill: Command line installer of the Julia Language.](https://github.com/abelsiqueira/jill) to install Julia executable will not invalidate the precompiled cache, while using the standard `setup-julia` action will. The behavior is also demonstrated in [GitHub - sosiristseng/julia-precompile-test: Julia precompile tests for GitHub actions](https://github.com/sosiristseng/julia-precompile-test). AFAIK the issue will be resolved in Julia 1.11. ([relevant thread](https://github.com/JuliaLang/julia/issues/50667#issuecomment-1817882297))
---
### Author:  [@ianshmean](https://discourse.julialang.org/u/ianshmean)
#### Post date: [January 4, 2024, 6:55am UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/7 "2024-01-04T06:55:58Z")
Thanks. Your post made me realize we can fix `julia-actions/setup-julia` so we can get this fixed on all releases before 1.11
>
>
> A bit of a hack to get julia installed with original mtimes to help https://gith…ub.com/JuliaLang/julia/issues/50667
>
> The comments explain the reasoning.
>
> Also should be a bit faster as it avoids the \`cp\` action.
>
> You can see here that 1.10.0 has the release mtimes
> \`\`\`
> StatStruct("/Users/runner/hostedtoolcache/julia/1.10.0/x64/share/julia/stdlib/v1.10/MbedTLS\_jll/src/MbedTLS\_jll.jl"
> size: 2169 bytes device: 16777220 inode: 7005911 mode: 0o100644 (-rw-r--r--) nlink: 1 uid: 501 (runner)
> gid: 20 (staff) rdev: 0 blksz: 4096 blocks: 8
> mtime: 2023-12-25T20:50:13+0000 (9 days ago) ctime: 2024-01-04T06:25:27+0000 (8 seconds ago))
> \`\`\`
>
> Closes https://github.com/julia-actions/setup-julia/pull/100
> Closes https://github.com/julia-actions/setup-julia/pull/165
---
### Author:  [@ianshmean](https://discourse.julialang.org/u/ianshmean)
#### Post date: [January 5, 2024, 7:10pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/8 "2024-01-05T19:10:54Z")
That’s now released in [Release v1.9.5: Maintain mtime of julia build to avoid re-precompilation · julia-actions/setup-julia · GitHub](https://github.com/julia-actions/setup-julia/releases/tag/v1.9.5)
So to get nice caching all you need is something like [GitHub - julia-actions/cache: A shortcut action to cache Julia artifacts, packages, and registries.](https://github.com/julia-actions/cache#usage)
---
### Author:  [@Wen-Wei\_Tseng](https://discourse.julialang.org/u/Wen-Wei_Tseng)
#### Post date: [January 6, 2024, 12:42pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/9 "2024-01-06T12:42:56Z")
Thank you. That patch totally fixed the precompile cache invalidation issue. Now, the standard workflow runs as fast as the jill workflow. ([GitHub actions run](https://github.com/sosiristseng/julia-precompile-test/actions/runs/7431551247))
---
### Author:  [@ianshmean](https://discourse.julialang.org/u/ianshmean)
#### Post date: [January 6, 2024, 1:06pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/10 "2024-01-06T13:06:53Z")
Great, thanks for checking
---
### Author:  [@xiaoxi](https://discourse.julialang.org/u/xiaoxi)
#### Post date: [January 6, 2024, 4:19pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/11 "2024-01-06T16:19:04Z")
Is there any chance that Julia 1.10 will become the next LTS?
Is there any time frame to know what the next LTS will be?
---
### Author:  [@adienes](https://discourse.julialang.org/u/adienes)
#### Post date: [January 6, 2024, 7:50pm UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/12 "2024-01-06T19:50:28Z")
I have no authority on the matter, but my understanding is that the answer is basically “there is a chance, but no promises”
as for time frame, if it is declared LTS that will happen around (and not before) the release of 1.11
---
### Author:  [@sob](https://discourse.julialang.org/u/sob)
#### Post date: [February 26, 2024, 12:17am UTC](https://discourse.julialang.org/t/v1-10-appreciation-thread/108103/13 "2024-02-26T00:17:18Z")
> **[Julia v1.10 Improves Performance, and Gnuplot Gets Pie Charts - Slashdot](https://developers.slashdot.org/story/24/02/25/1916251/julia-v110-improves-performance-and-gnuplot-gets-pie-charts)**
>
> Julia 1.0 was released in 2018 — after a six-year wait.
>
> And there's now another update. LWN.net gets you up to speed, calling Julia "a general-purpose, open-source programming language with a focus on high-performance scientific computing."
>
> Some...