# Why is juliaup emphasized as the installation mechanism?

**URL:** <https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844>\
**Category:** Tooling\
**Created:** [January 2, 2026, 4:49pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844 "2026-01-02T16:49:50Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 6, 2026, 4:29pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/42 "2026-01-06T16:29:58Z")

</div>

> [@GeorgeGkountouras](#):
>
> If you are teaching a course, you can set up your own set of packages the same way Jumbo does. Then it will be consistent within the course and easy to deploy. Of course, it won’t run arbitrary Julia code.

Oh, for organizing courses that might make sense.

I had a different scenario in mind: I have a Julia application that I want others to use (non-Julia-devs). Currently, I just refer potential users to the “manual installers” page, specifying to install the latest LTS for their OS.  
Compare this to potential juliaup-based instructions in this scenario… It would be quite a sequence of steps: (1) install Juliaup (2) remove whatever Julia version it installed by default (3) install the required version (4) make it the default. Why would anyone prefer this for endusers? 🙂

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [January 6, 2026, 4:32pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/43 "2026-01-06T16:32:22Z")

</div>

At least if you’re using VS Code then we can automate most of this for you. Put `julia +1.10` (or whatever channel you need) into the workspace settings and it should basically be a one-click installation of juliaup and the required channels.

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 6, 2026, 4:33pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/44 "2026-01-06T16:33:42Z")

</div>

You mean, asking potential app users to also install a fancy IDE + extension?..

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [January 6, 2026, 4:37pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/45 "2026-01-06T16:37:11Z")

</div>

Apparently not? “Julia application” can mean whole lot of things, and installing an IDE to run a project in might be appropriate in some of them.

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 6, 2026, 4:42pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/46 "2026-01-06T16:42:59Z")

</div>

IME, directing users to the “manual installer” page works quite well. The only issue I saw is that sometimes somebody installs a wrong Julia version by accident – and the failure mode is quite bad, the terminal gets overloaded with long scary error messages. But otherwise things have been going smoothly.

That’s why my suggestion above ([Why is juliaup emphasized as the installation mechanism? - #24 by aplavin](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/24)) to streamline the install page.

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [January 6, 2026, 7:00pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/47 "2026-01-06T19:00:44Z")

</div>

OK, I’m starting to understand this better now. I was initially rather confused about your user-vs-dev breakdown, but I think I’m now getting it. Rather than thinking about who’s at the keyboard, I think it might be more helpful to think about the use-case — and the places where folks seem to struggle the most with with `juliaup` is when they _just want to run some `.jl` file_. Or perhaps even worse, double-click something that happens to execute `julia script.jl`. Or run some Pluto notebook.

And so this is _precisely_ how rustup and juliaup diverge. It’s not so much about distribution of Julia itself as it is about distribution of an “executable” (or script or notebook or something) that depends upon `julia`. The expectations of those two use-cases are wildly different.

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 6, 2026, 7:45pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/48 "2026-01-06T19:45:26Z")

</div>

Yes, sorry for the potential confusion 🙂 I really mean this distinction as “someone who writes Julia code” vs “someone who runs Julia code, but doesn’t really write it”.  
And (arguably?) we want the latter group to grow over time.

---

<div class="post-metadata">

**Author:** ![Zentrik](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zentrik/32/35409_2.png) [@Zentrik](https://discourse.julialang.org/u/Zentrik)\
**Post date:** [January 7, 2026, 12:00am UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/49 "2026-01-07T00:00:41Z")

</div>

Isn’t Juliaup installable through the windows store, [Julia - Free download and install on Windows | Microsoft Store](https://apps.microsoft.com/detail/9njnww8pvkmn?hl=en-GB&gl=GB) (perhaps the install page should make this more obvious?). Is this not the simplest way to install for non technical windows users? Maybe I missed someone discussing it earlier in the thread.

---

<div class="post-metadata">

**Author:** ![mihalybaci](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mihalybaci/32/13528_2.png) [@mihalybaci](https://discourse.julialang.org/u/mihalybaci)\
**Post date:** [January 7, 2026, 4:16pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/50 "2026-01-07T16:16:19Z")

</div>

Lots of companies disable access to the Windows Store on their networks/computers, even if employees have non-admin install permissions. So other easy, reliable options must exist.

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [January 7, 2026, 4:45pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/51 "2026-01-07T16:45:45Z")

</div>

Just to remind participants this is not the first hot debate on this topic:

> [@A graphical Julia installer for Windows](https://discourse.julialang.org/t/a-graphical-julia-installer-for-windows/128413):
>
> As Windows user I need a graphical installer where I can select at least: the Julia version I want to install the install location All larger projects I know provide a graphical installer for Windows and a way to use it without the Microsoft store. And that’s why I chose the graphical installer for Julia. I cannot understand to hear in [this thread](https://discourse.julialang.org/t/about-julias-development-policy-regarding-windows/128011/) that just because I need a graphical installer I made a mistake. As I wrote installers for 2 lager projects ([lyx.org](http://lyx.org) and [freecad.org](http://freecad.org)) with over t…

> [@Challenges with installing Julia on Windows](https://discourse.julialang.org/t/challenges-with-installing-julia-on-windows/128133):
>
> 3 issues from my side: the most severe is that you cannot install Julia for all users of a computer. To be able to use Julia with all its features (e.g. PackageCompiler), the julia.exe must be in the PATH environment variable of Windows. By running the installer as administrator, the path to the julia.exe is not added to the system-wide PATH, but to the PATH of the admin user. Therefore any other user of the PC does not have Julia in the PATH. Sure, you can tell all other users to manually ad…

---

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [January 7, 2026, 4:48pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/52 "2026-01-07T16:48:06Z")

</div>

> [@mihalybaci](#):
>
> Lots of companies disable access to the Windows Store on their networks/computers, even if employees have non-admin install permissions. So other easy, reliable options must exist.

> [@Challenges with installing Julia on Windows](https://discourse.julialang.org/t/challenges-with-installing-julia-on-windows/128133/5):
>
> You can also do a system install by running the following command from a shell: msiexec /i \<PATH\_TO\_JULIA\_MSI\> ALLUSERS=1

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 7, 2026, 5:05pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/53 "2026-01-07T17:05:52Z")

</div>

> [@Eben60](#):
>
> Just to remind participants this is not the first hot debate on this topic

Indeed, thanks for linking!  
Although note that at least some key points from those messages do exist already:

> [@A graphical Julia installer for Windows](https://discourse.julialang.org/t/a-graphical-julia-installer-for-windows/128413/1):
>
> As Windows user I need a graphical installer where I can select at least:
> 
> - the Julia version I want to install
> - the install location

This is literally the current standalone installer 🙂  
That’s why I was really surprised to see that the standalone installer is heavily advised against, according to the official Julia install webpage (haven’t really read that page in a while). It’s clearly the easiest option for the most basic – and arguably the most common – scenario.  
_And I’m saying this as a juliaup user: it’s a nice tool, but for more advanced usecases._

---

<div class="post-metadata">

**Author:** ![nhavt](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nhavt/32/16356_2.png) [@nhavt](https://discourse.julialang.org/u/nhavt)\
**Post date:** [January 8, 2026, 12:54pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/54 "2026-01-08T12:54:13Z")

</div>

Just my 2 cent: for Windows users who can’t install **juliaup** through the Microsoft Store (e.g. if your organization blocks access to it), you can try installing it with **Scoop** instead: [Scoop](https://scoop.sh/#/apps?p=1&q=juliaup)

---

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [January 8, 2026, 7:10pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/55 "2026-01-08T19:10:15Z")

</div>

> [@nhavt](#):
>
> you can try installing it with **Scoop** instead

I am not a Windows user, but I am wondering it it would make sense to mention that in the README of juliaup:

> **[GitHub - JuliaLang/juliaup: Julia installer and version multiplexer](https://github.com/JuliaLang/juliaup)**
>
> Julia installer and version multiplexer

Please consider making a PR.

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [January 31, 2026, 8:50pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/56 "2026-01-31T20:50:33Z")

</div>

> [@aplavin](#):
>
> Maybe the installation page can look like this? 🙂
> 
> ![image](https://global.discourse-cdn.com/julialang/original/3X/8/3/83f559bbc6f3835c385609e446e79faf49574929.png)

This suggestion got quite some support here, judging by reactions – so I opened a PR to the actual julialang website, [draft: change recommended installation method · Pull Request #2430 · JuliaLang/www.julialang.org](https://github.com/JuliaLang/www.julialang.org/pull/2430). Got no response for over two weeks, but maybe someday… 🙂

---

<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:** [February 1, 2026, 2:04pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/57 "2026-02-01T14:04:49Z")

</div>

Maybe put the standalone installer/Juliaup as the titles and remove the User/Developer distinction? I don’t think I agree with those categories, my experience with Juliaup has been great for both.

---

<div class="post-metadata">

**Author:** ![aplavin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/aplavin/32/222056_2.png) [@aplavin](https://discourse.julialang.org/u/aplavin)\
**Post date:** [February 1, 2026, 2:24pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/58 "2026-02-01T14:24:07Z")

</div>

Maybe…  
But I see this question of actually providing all-familiar download links at the download page ended up quite controversial (see the PR link), to my surprise. I don’t think I have the energy to argue for this further, so probably won’t happen anyway.

---

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [February 5, 2026, 6:51am UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/59 "2026-02-05T06:51:40Z")

</div>

> [@benz0li](#):
>
> For courses with many students, a [JupyterHub](https://jupyter.org/hub) setup (plus containerised [JupyterLab](https://jupyter.org) + [code-server](https://github.com/coder/code-server) + Julia) could also be considered.

I support this setting, altought the tradeoff is that then students leave with nothing on their own pc.. it makes easier to manage the course but harder for them to apply the knowledge gained in their own then after the course..

 ![Screenshot_2026-02-05-07-45-09-221_org.mozilla.firefox](https://global.discourse-cdn.com/julialang/original/3X/4/4/44609a89b73d08389fc7d452cc8c964a8aaa26cb.jpeg)

 ![Screenshot_2026-02-05-07-47-42-094_org.mozilla.firefox](https://global.discourse-cdn.com/julialang/original/3X/e/d/ed0706ea24777c4e6fe6682cddb6a8953f3be09d.jpeg)

---

<div class="post-metadata">

**Author:** ![benz0li](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/benz0li/32/37040_2.png) [@benz0li](https://discourse.julialang.org/u/benz0li)\
**Post date:** [February 5, 2026, 8:05am UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/60 "2026-02-05T08:05:43Z")

</div>

> [@sylvaticus](#):
>
> the tradeoff is that then students leave with nothing on their own pc.

If the container images are publicly available (e.g. [GitHub - b-data/jupyterlab-julia-docker-stack: (GPU accelerated) Multi-arch (linux/amd64, linux/arm64/v8) JupyterLab Julia docker images. Please submit Pull Requests to the GitLab repository. Mirror of](https://github.com/b-data/jupyterlab-julia-docker-stack)) a student

1. can download the courses’ code to their pc/laptop
2. run the container locally using Docker or Podman

---

<div class="post-metadata">

**Author:** ![sylvaticus](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sylvaticus/32/203883_2.png) [@sylvaticus](https://discourse.julialang.org/u/sylvaticus)\
**Post date:** [February 5, 2026, 8:44pm UTC](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844/61 "2026-02-05T20:44:16Z")

</div>

There is a very large share of researchers that have no idea what a container or docker is ..

[Previous page](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844.md?page=2)

[Next page](https://discourse.julialang.org/t/why-is-juliaup-emphasized-as-the-installation-mechanism/134844.md?page=4)