# A graphical Julia installer for Windows

**URL:** <https://discourse.julialang.org/t/a-graphical-julia-installer-for-windows/128413>\
**Category:** General Usage\
**Tags:** windows\
**Created:** [April 23, 2025, 9:29pm UTC](https://discourse.julialang.org/t/a-graphical-julia-installer-for-windows/128413 "2025-04-23T21:29:00Z")\
**Posts on this page:** 1\
**Showing post:** 19

<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:** [April 26, 2025, 10:41am UTC](https://discourse.julialang.org/t/a-graphical-julia-installer-for-windows/128413/19 "2025-04-26T10:41:41Z")

</div>

First, disclaimer - my opinion, just as (almost) every opinion here, is just that - a private opinion, not representing that semi-mythical community.

@uwestoehr, it looks like you are starting 4½ quite large projects at once:

1. Learning Julia, it’s ecosystem and tools (Terminal, CLI tools, git, GitHub, packages etc.).
2. Creating your specific application as a part of a commercial product.
3. Establishing a workflow to integrate Lazarus GUI with Julia in a compiled executable or library.
4. Creating a GUI installer for Windows from the scratch.

- And teaching the Julia community (whatever it is) how to organize the development processes.

It’s quite a lot, and in open source biting too much to swallow would regularly result in wasted effort and abandoned projects.

Now, let me tell what I think of your nos. 3 and 4.

Having an established way to integrate a Julia backend with some GUI in a shippable package is what is your actual need (in no.2), and it may find a lot of similar applications.

But as concerning a graphical installer for Windows - I mostly agree with the said in the post above:

> [@goerz](#):
>
> But let’s not kid ourselves. It’s a _programming language_. It caters to developers. Knowledge of version schemes, IDEs, REPLs, and, for that matter, Git/GitHub and the command line are pretty much table stakes.

I’d only add one more pre-requisite which is the knowledge of English language (as you mentioned translations).

I do not think there is a real need in one more installer. `juliaup` does it’s job. Unfortunately, MS Store is not accessible to everyone, and the juliaup MSIX App Installer has been [reported to have some issues](https://discourse.julialang.org/t/how-to-create-standalone-applications-for-windows-with-a-g-ui-in-julia-1-11-or-1-12/127823/66). Still I assume getting that installer to work should be much easier than to write a Julia version manager from the scratch.

Furthermore, should you even get your installer working, it will be not an easy thing to get it accepted. Though one can easily experiment with one or another _Julia package_, I’d definitely be reluctant to experiment with a _Julia installer_. I have `juliaup` on all my computers, and I’m not going to risk an alternative installer messing up my system. Futhermore, juliaup usage is the same on all OSes, whereas you probably lack resources and experience to get it work on macOS and Linux.

Probably you could help the juliaup people to find out what is wrong with their installer? That would be great!

---

_[View the full topic](https://discourse.julialang.org/t/a-graphical-julia-installer-for-windows/128413)._