# How do people use Julia nightly?

**URL:** https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685
**Category:** General Usage
**Tags:** nightly, installation, juliaup
**Created:** [June 22, 2023, 7:41am UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685 "2023-06-22T07:41:38Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)
#### Post date: [June 22, 2023, 7:41am UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/1 "2023-06-22T07:41:39Z")

</div>

Hi there,

I keep seeing messages about how 1.10 is gonna be even faster and cooler than 1.9, so of course I wanna do like the cool kids and give it a try.

As far as I can tell, there are two main ways to download it:

- Get the [nightly binary](https://julialang.org/downloads/nightlies/)
- Clone the repo and [build from source](https://github.com/JuliaLang/julia#building-julia)

Then there is the question of how to set the path, which I prefer to handle with [juliaup](https://github.com/JuliaLang/juliaup#using-juliaup). In particular, I think the following command can be handy:

> `juliaup link dev ~/juliasrc/julia` configures the dev channel to use a binary that you provide that is located at `~/juliasrc/julia`.

Until nightlies are fully integrated with juliaup, I see no other option but to either redownload the binary or pull and rebuild regularly. Has anyone found a better workaround?

Related:

> [@Installing Julia Nightly with juliaup](https://discourse.julialang.org/t/installing-julia-nightly-with-juliaup/89749):
>
> I used to use jill.py to manage Julia installation. It supported installing the latest nightly version (i.e. 1.9), but I don’t see how to get juliaup to install it. Is there a way to do so?

---

<div class="post-metadata">

### Author: ![AMJ](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/amj/32/214096_2.png) [@AMJ](https://discourse.julialang.org/u/AMJ)
#### Post date: [June 22, 2023, 9:05am UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/2 "2023-06-22T09:05:45Z")

</div>

Do you need the latest pulls for any specific reason?

If Im looking forward to any specific pull/issue, I just wait till it’s fully merged/all the checks are green, then just download the nightly built version from the site. I find the hassle of building from source unenjoyable 😬.

---

<div class="post-metadata">

### Author: ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)
#### Post date: [June 22, 2023, 9:19am UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/3 "2023-06-22T09:19:33Z")

</div>

No, in this instance I just enjoy the shorter type display in the stack traces. So I don’t care about having only this week’s or even this month’s build, I just want something slightly more recent than the current release, which dates back months

---

<div class="post-metadata">

### Author: ![AMJ](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/amj/32/214096_2.png) [@AMJ](https://discourse.julialang.org/u/AMJ)
#### Post date: [June 22, 2023, 9:30am UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/4 "2023-06-22T09:30:20Z")

</div>

My understanding was that the nightly builds are usually a few days old if there has been a recent merged pull. This is the current one in the site:

 ![Screenshot 2023-06-22 at 12.59.03 PM](https://global.discourse-cdn.com/julialang/original/3X/a/9/a9a5e350945aee1db75d439555429cab6d0d4720.png)

---

<div class="post-metadata">

### Author: ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)
#### Post date: [June 22, 2023, 9:47am UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/5 "2023-06-22T09:47:21Z")

</div>

Even a few weeks old is fine by me. I don’t care about “nightly” as much as “monthly”

---

<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: [June 22, 2023, 12:04pm UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/6 "2023-06-22T12:04:47Z")

</div>

> [@gdalle](#):
>
> so of course I wanna do like the cool kids and give it a try

This is fine, but make sure you have the right [risk tolerance](https://discourse.julialang.org/t/proposed-release-process-and-schedule/15623) for your application.

Eg nowadays I use the latest stable release for “production” (ie to get actual work done, without distractions) because it has gotten so great, unless I have a compelling need for some feature or want t explore something. YMMV.

---

<div class="post-metadata">

### Author: ![Oscar\_Smith](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/oscar_smith/32/25343_2.png) [@Oscar\_Smith](https://discourse.julialang.org/u/Oscar_Smith)
#### Post date: [June 22, 2023, 12:55pm UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/7 "2023-06-22T12:55:51Z")

</div>

I would recommend cloning and building is yourself. that way the update process is just a git pull and make -j

---

<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: [June 22, 2023, 12:58pm UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/8 "2023-06-22T12:58:51Z")

</div>

A further advantage for package developers is that 1.10 has a parallel compiling. For me it reduces the compile time from ~90 sec to ~50 sec.

---

<div class="post-metadata">

### Author: ![tbeason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tbeason/32/15898_2.png) [@tbeason](https://discourse.julialang.org/u/tbeason)
#### Post date: [June 22, 2023, 1:10pm UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/9 "2023-06-22T13:10:46Z")

</div>

Yea it would be cool for juliaup to eventually allow for a nightly channel.

---

<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: [June 22, 2023, 2:54pm UTC](https://discourse.julialang.org/t/how-do-people-use-julia-nightly/100685/10 "2023-06-22T14:54:40Z")

</div>

> [@joa-quim](#):
>
> A further advantage for package developers is that 1.10 has a parallel compiling. For me it reduces the compile time from ~90 sec to ~50 sec.

I was not aware of that, really cool. Really improves the installation time here, which became sort of an annoyance with all the code cashing of 1.9.
