# New Julia versions, higher Pluto loading times

**URL:** <https://discourse.julialang.org/t/new-julia-versions-higher-pluto-loading-times/135187>\
**Category:** General Usage\
**Tags:** ttfx\
**Created:** [January 21, 2026, 1:09pm UTC](https://discourse.julialang.org/t/new-julia-versions-higher-pluto-loading-times/135187 "2026-01-21T13:09:38Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![j-fu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/j-fu/32/11373_2.png) [@j-fu](https://discourse.julialang.org/u/j-fu)\
**Post date:** [January 22, 2026, 9:18am UTC](https://discourse.julialang.org/t/new-julia-versions-higher-pluto-loading-times/135187/15 "2026-01-22T09:18:32Z")

</div>

As far as marimo is concerned: this in fact [was inspired by Pluto](https://news.ycombinator.com/item?id=40327543). It’s main advantage nowadays however is that notebooks can be deployed via wasm with zero installation efforts for the user, but this would be another [thread](https://discourse.julialang.org/t/jupyterlab-lite-and-status-of-julia-running-wasm/129957).

I see the loading time issue as critical. Extrapolating the time between 1.6 and 1.10, we are now 9 months away from another LTS release (1.13 ?) which would have e.g. `public`, and `[sources], [workspaces]` in the project files with the potential to significantly improve the sustainability of the package ecosystem. As far as I remember, SciML was quite quick to require 1.10 as minimal Julia version, and the additions I mentioned are good reasons to perform a similar quick transition for the next lts. Sticking to 1.10 for package loading time issues then would hold back the whole package ecosystem.

---

_[View the full topic](https://discourse.julialang.org/t/new-julia-versions-higher-pluto-loading-times/135187)._