# Juliaup: a modest suggestion

**URL:** <https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465>\
**Category:** Internals & Design\
**Created:** [April 27, 2025, 4:59pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465 "2025-04-27T16:59:56Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![isaacsas](https://avatars.discourse-cdn.com/v4/letter/i/f6c823/32.png) [@isaacsas](https://discourse.julialang.org/u/isaacsas)\
**Post date:** [April 29, 2025, 4:34pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/42 "2025-04-29T16:34:55Z")

</div>

I just want to second having GUI install options. Teaching classes that use Julia it is quite a leap for some students to tell them to run something from the command line. Many have no idea about what a terminal even is on Mac/Windows (and few students use Linux on their personal computers in my experience). So I end up just having them download the non-Juliaup binaries. This is a place where a Juliaup GUI installer would be very helpful to have (and more generally, having a GUI for managing it too would be nice, i.e. for selecting the active release and updating).

---

<div class="post-metadata">

**Author:** ![greatpet](https://avatars.discourse-cdn.com/v4/letter/g/e495f1/32.png) [@greatpet](https://discourse.julialang.org/u/greatpet)\
**Post date:** [April 29, 2025, 5:53pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/43 "2025-04-29T17:53:48Z")

</div>

> [@isaacsas](#):
>
> having a GUI for managing it too would be nice, i.e. for selecting the active release and updating

Certainly would be nice, and there also needs to be a GUI for `pkg.instantiate()`, `Pkg.generate()` and `Pkg.dev()` etc., if one really wants to avoid the command line. Until there’s a full GUI wrapper for everything, you can only delay the inevitable eventual task of learning to use the command line.

However, for devil’s advocate, I’d argue that basic familiarity with Bash and Git is more important than learning any programming language, Julia included.

---

<div class="post-metadata">

**Author:** ![GHTaarn](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ghtaarn/32/216007_2.png) [@GHTaarn](https://discourse.julialang.org/u/GHTaarn)\
**Post date:** [April 29, 2025, 7:55pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/44 "2025-04-29T19:55:55Z")

</div>

> [@greatpet](#):
>
> Certainly would be nice, and there also needs to be a GUI for `pkg.instantiate()`, `Pkg.generate()` and `Pkg.dev()` etc., if one really wants to avoid the command line. Until there’s a full GUI wrapper for everything, you can only delay the inevitable eventual task of learning to use the command line.

Delaying the inevitable can make a lot of sense sometimes, professional pilots do eventually need to fly a real airplane with passengers in it, but it makes sense to start their training in a flight simulator. I trust that @isaacsas has made a similar judgement about when to expose his students to the commandline.

---

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [April 29, 2025, 9:58pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/45 "2025-04-29T21:58:36Z")

</div>

> [@GHTaarn](#):
>
> Delaying the inevitable can make a lot of sense sometimes, professional pilots do eventually need to fly a real airplane with passengers in it,

Delaying makes sense when the potential consequences are very, very bad. Usually, the command line of a personal computer is comparatively low risk.

Nothing against GUIs, mind you.

---

<div class="post-metadata">

**Author:** ![GHTaarn](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ghtaarn/32/216007_2.png) [@GHTaarn](https://discourse.julialang.org/u/GHTaarn)\
**Post date:** [April 30, 2025, 7:06am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/46 "2025-04-30T07:06:48Z")

</div>

> [@DNF](#):
>
> Delaying makes sense when the potential consequences are very, very bad. Usually, the command line of a personal computer is comparatively low risk.

“Very, very bad consequences” is another way of saying “very, very high costs”. In general, the sequence in which things are taught should be done in such a way as to either reduce the cost or increase the quality or some combination of these. I can easily see a GUI installer being an advantage in this context.

---

<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:** [April 30, 2025, 9:02am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/47 "2025-04-30T09:02:31Z")

</div>

> [@greatpet](#):
>
> Until there’s a full GUI wrapper for everything, you can only delay the inevitable eventual task of learning to use the command line.

And there is unlikely to be a GUI wrapper for everything, or even the majority of tasks, since GUIs are orders of magnitude more expensive to write and maintain than command line tools. It is not an accident that innovation happens in the command line and GUI wrappers usually arrive for mature tools only, sometimes years later.

I honestly can’t imagine a use scenario for Julia where, at the same time, the programmer can avoid the command line altogether.

An exception may be learning Julia as part of a course on programming. But then a TA or university IT should be able to help students set it up on their own computer if necessary.

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [April 30, 2025, 2:12pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/48 "2025-04-30T14:12:59Z")

</div>

For a new user of Julia the difficulties are not over when Julia is installed. They have only just begun!

So, no, I don’t think it is critical to have a GUI installer. There should be an installer that works no matter what administrative privileges the user has and no matter where the Julia folder and the depot should be. I think we have that for all OSs. IMO, that is all we need right now.

---

<div class="post-metadata">

**Author:** ![TimG](https://avatars.discourse-cdn.com/v4/letter/t/82dd89/32.png) [@TimG](https://discourse.julialang.org/u/TimG)\
**Post date:** [April 30, 2025, 2:26pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/49 "2025-04-30T14:26:04Z")

</div>

> [@Tamas\_Papp](#):
>
> I honestly can’t imagine a use scenario for Julia where, at the same time, the programmer can avoid the command line altogether.

I use Julia in VS-Code on Windows. I think the only time I ever use the command line at work is for juliaup.

---

<div class="post-metadata">

**Author:** ![isaacsas](https://avatars.discourse-cdn.com/v4/letter/i/f6c823/32.png) [@isaacsas](https://discourse.julialang.org/u/isaacsas)\
**Post date:** [April 30, 2025, 2:39pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/50 "2025-04-30T14:39:17Z")

</div>

> [@greatpet](#):
>
> Certainly would be nice, and there also needs to be a GUI for `pkg.instantiate()`, `Pkg.generate()` and `Pkg.dev()` etc., if one really wants to avoid the command line. Until there’s a full GUI wrapper for everything, you can only delay the inevitable eventual task of learning to use the command line.

Learning Git and bash and package creation/management are indeed exceptionally useful skills, but not needed for many classes, where Julia may only be used to explore mathematical or scientific concepts via notebooks. This is a different use case than writing scripts or packages, for which I certainly agree knowing such skills is important. But one only has so much time in a given semester, and spending time in a science-focused class teaching about programming dev practices can mean having to not cover more core class material. Thankfully [julialang.org](http://julialang.org) still distributes stand alone GUI installers that students can be pointed to, and package management can be completely abstracted away from students by using Pluto (or writing some package loading code in a Jupyter notebook and just telling students to run it).

Also, none of those function calls above are “command line” shell-based interactions that require the usage of a terminal. They are just normal function calls within Julia. (And as I said, I usually give such code anyways in notebooks, so students don’t really need to understand it.)

---

<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:** [April 30, 2025, 2:43pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/51 "2025-04-30T14:43:00Z")

</div>

Couldn´t the VSCode extension provide an interface for installing julia(up) ?

---

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [April 30, 2025, 4:41pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/52 "2025-04-30T16:41:31Z")

</div>

> [@isaacsas](#):
>
> Thankfully [julialang.org](http://julialang.org) still distributes stand alone GUI installers that students can be pointed to,

Aleluia. Let’s just hope that never goes away.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [May 1, 2025, 1:43am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/53 "2025-05-01T01:43:17Z")

</div>

Doesn’t it already?

---

<div class="post-metadata">

**Author:** ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)\
**Post date:** [May 1, 2025, 2:39am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/54 "2025-05-01T02:39:16Z")

</div>

I’ve never heard of it.

---

<div class="post-metadata">

**Author:** ![gcv](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gcv/32/11086_2.png) [@gcv](https://discourse.julialang.org/u/gcv)\
**Post date:** [May 3, 2025, 9:26am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/55 "2025-05-03T09:26:25Z")

</div>

The closest thing to “the right” solution, at least for Mac and Linux, is to use Devbox with a project-specific dependency on the specific version of Julia the project needs (`julia@1.10` or `julia@1.11`). The nixpkgs versions of Julia (that Devbox uses) seems to work for me (so far…). This approach has the considerable virtue of unifying dependency management for other tools and languages. Having a different tool like `rustup` and `juliaup` managing individual toolchains for every language gets unwieldy. Combined with direnv and an appropriate editor plugin, path setup becomes a nonissue: each project just sets itself up.

This definitely doesn’t help with the problem of students, or Windows users…

---

<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:** [May 3, 2025, 4:15pm UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/56 "2025-05-03T16:15:10Z")

</div>

> [@Tamas\_Papp](#):
>
> I honestly can’t imagine a use scenario for Julia where, at the same time, the programmer can avoid the command line altogether.

I can easily imagine such a scenario. A lot of people use notebooks as the primary/the only way of writing code, and for both jupyter (+vscode) and pluto one doesn’t typically need to reach for command line.

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [May 4, 2025, 1:26am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/57 "2025-05-04T01:26:10Z")

</div>

Really? Please show me how to setup a Pluto server without using command line.

---

<div class="post-metadata">

**Author:** ![slumpy](https://avatars.discourse-cdn.com/v4/letter/s/a88e4f/32.png) [@slumpy](https://discourse.julialang.org/u/slumpy)\
**Post date:** [May 4, 2025, 6:04am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/58 "2025-05-04T06:04:09Z")

</div>

runpluto.jl :

```julia
#!/usr/bin/env julia

import Pkg
Pkg.add(“Pluto”)

import Pluto
Pluto.run()

```

Assuming jl files are associated with an installed julia if running on windows 🙂

That being said, assuming personal devices where installing software is not an issue, how hard and scary is it to run a couple of commands in the terminal for students who are about to spend ~50 hours in class and likely at least the same amount at home, on a science class?

It’s not that different from typing into the browser (or browser ide like vscode). The terminal is also a gui application after all.

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [May 4, 2025, 7:27am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/59 "2025-05-04T07:27:41Z")

</div>

I am not against command line. On the contrary, in my course teaching Julia, the first thing I want students to learn is the command line.

I am specially reply to this quote

> [@aplavin](#):
>
> A lot of people use notebooks as the primary/the only way of writing code, and for both jupyter (+vscode) and pluto one doesn’t typically need to reach for command line.

To use Pluto, command line is inevitable.

---

<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:** [May 4, 2025, 7:51am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/60 "2025-05-04T07:51:48Z")

</div>

> [@liuyxpp](#):
>
> To use Pluto, command line is inevitable.

How so? See @slumpy’s post above, it doesn’t require typing anything in the terminal.

> [@slumpy](#):
>
> It’s not that different from typing into the browser (or browser ide like vscode). The terminal is also a gui application after all.

I generally agree! Was surprised myself when I saw that typing anything in the terminal is perceived very differently from typing code in a script file or in a notebook – by a significant number of people. Somehow the terminal is considered scary and low-level 🙂

---

<div class="post-metadata">

**Author:** ![liuyxpp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/liuyxpp/32/9870_2.png) [@liuyxpp](https://discourse.julialang.org/u/liuyxpp)\
**Post date:** [May 4, 2025, 8:02am UTC](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465/61 "2025-05-04T08:02:57Z")

</div>

> [@aplavin](#):
>
> it doesn’t require typing anything in the terminal.

Obviously, to run the script, you have to type a command in a command line.

[Previous page](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465.md?page=2)

[Next page](https://discourse.julialang.org/t/juliaup-a-modest-suggestion/128465.md?page=4)
