# Juliac and PackageCompiler

**URL:** https://discourse.julialang.org/t/juliac-and-packagecompiler/124683
**Category:** Internals & Design
**Tags:** package-compiler, sysimage, compiler
**Created:** [January 11, 2025, 10:06pm UTC](https://discourse.julialang.org/t/juliac-and-packagecompiler/124683 "2025-01-11T22:06:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![wujinq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/wujinq/32/22221_2.png) [@wujinq](https://discourse.julialang.org/u/wujinq)
#### Post date: [January 11, 2025, 10:06pm UTC](https://discourse.julialang.org/t/juliac-and-packagecompiler/124683/1 "2025-01-11T22:06:24Z")

</div>

It seems that `juliac` is currently [being developed](https://www.youtube.com/watch?v=MKdobiCKSu0) to compile Julia code into binary, which does not impose the constraints in [static compilation](https://github.com/tshort/StaticCompiler.jl). I’m however curous about the relation between `juliac` and [Package Compiler](https://github.com/JuliaLang/PackageCompiler.jl/tree/master/src): are they in competition with each other? I read the source code of `PackageCompiler.jl` and it seems to be comparable to [`juliac.jl`](https://github.com/JuliaLang/julia/blob/master/contrib/juliac.jl), and I’m curious about the future of both `juliac` and `PackageCompiler.jl`.

---

<div class="post-metadata">

### Author: ![jeff.bezanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeff.bezanson/32/48_2.png) [@jeff.bezanson](https://discourse.julialang.org/u/jeff.bezanson)
#### Post date: [January 13, 2025, 2:35pm UTC](https://discourse.julialang.org/t/juliac-and-packagecompiler/124683/2 "2025-01-13T14:35:50Z")

</div>

Correct, they are similar. In fact the goal is for `juliac` to be a command-line-style interface to PackageCompiler, so they will be the same thing plus a couple new features.