# Where is Julia heading? Lack of clarity about priorities, long-term direction and governance

**URL:** <https://discourse.julialang.org/t/where-is-julia-heading-lack-of-clarity-about-priorities-long-term-direction-and-governance/133734>\
**Category:** Community\
**Tags:** question, roadmap\
**Created:** [November 7, 2025, 2:14pm UTC](https://discourse.julialang.org/t/where-is-julia-heading-lack-of-clarity-about-priorities-long-term-direction-and-governance/133734 "2025-11-07T14:14:04Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![bvdmitri](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bvdmitri/32/22935_2.png) [@bvdmitri](https://discourse.julialang.org/u/bvdmitri)\
**Post date:** [November 7, 2025, 5:20pm UTC](https://discourse.julialang.org/t/where-is-julia-heading-lack-of-clarity-about-priorities-long-term-direction-and-governance/133734/26 "2025-11-07T17:20:15Z")

</div>

> [@rkube](#):
>
> Another point is static compilation. I can play around with it, and probably find some cool use for it. But it’s not production ready. Should I keep working with it, waiting for the situation get better? Or will it be abandoned? Without a roadmap for this feature, I’d probably just don’t touch it and move on to another language.

You touched on the exact pain point that might have started this entire discussion 😄

That’s _precisely_ the kind of problem I’m facing right now — compilation is painful, and deployment is even more so.

One day I see something new called juliac. Naturally, I get curious and start digging in — I watch videos, read forum threads and pull requests, even experiment with it myself using its unstable API. But after all that, I still can’t find a clear explanation, direction, or instructions on how to actually use it (despite it being prominently mentioned in the Julia changelog). So, I finally have to ask: _what’s the plan?_

 ![Screenshot 2025-11-07 at 18.02.20](https://global.discourse-cdn.com/julialang/original/3X/c/b/cb63e521ec3b31e5cd6ced49704eb55c813b4612.png)

Apparently, juliac isn’t meant to replace PackageCompiler and isn’t an improvement at this stage — that’s fine and clear. But then I read [this discussion](https://discourse.julialang.org/t/about-julias-development-policy-regarding-windows/128011/78), and see that PackageCompiler itself isn’t a core component and might or might not be maintained consistently.

So again, there seems to be a lack of cohesive vision — and that raises so many questions:  
• How should Julia projects be compiled today — with PackageCompiler or juliac?  
• Will one eventually replace the other?  
• Should developers start migrating, or stay put?  
• What’s the long-term plan? Why does Julia need two separate tools for binary compilation?

I tried searching through issues and discussions to find these answers, but they’re scattered or missing altogether. It feels like all of this could be clarified through a centralized proposal for juliac — one that lays out the motivation, roadmap, and relationship with existing tools.

---

_[View the full topic](https://discourse.julialang.org/t/where-is-julia-heading-lack-of-clarity-about-priorities-long-term-direction-and-governance/133734)._