# About Julia's development policy regarding Windows

**URL:** <https://discourse.julialang.org/t/about-julias-development-policy-regarding-windows/128011>\
**Category:** General Usage\
**Tags:** windows\
**Created:** [April 12, 2025, 7:29pm UTC](https://discourse.julialang.org/t/about-julias-development-policy-regarding-windows/128011 "2025-04-12T19:29:51Z")\
**Posts on this page:** 1\
**Showing post:** 67

<div class="post-metadata">

**Author:** ![uwestoehr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/uwestoehr/32/216201_2.png) [@uwestoehr](https://discourse.julialang.org/u/uwestoehr)\
**Post date:** [April 22, 2025, 10:58pm UTC](https://discourse.julialang.org/t/about-julias-development-policy-regarding-windows/128011/67 "2025-04-22T22:58:57Z")

</div>

> [@uwestoehr](#):
>
> Take the case of _PackageCompiler_. Since Julia 1.11 one cannot use more than one thread. This reduces the compilation speed a lot (for me by about 40%).

I have to correct my self:

Julia 1.11.5 using a single thread compiles on Windows a simple module via PackageCompiler about 60 % slower than Julia 1.10.9. See my [detailed test in this thread](https://discourse.julialang.org/t/packagecompiler-hangs-while-compiling-nonincremental-system-image-on-julia-v1-11/128099/52).

Maybe this is not the case on Linux, but this is why I opened the discussion.

Allow me to make another proposal:

- all pinned projects in `https://github.com/JuliaLang/` are treated as core components.
- before a release is made all these projects are tested with the new Julia on Windows, Linux and MacOS.
- If they work the first beta can be released.
- If they work, but there is a major performance issue, the release of the beta gets information about this.

I think this will not block a beta release but a wide audience is then aware of issues and can help, test, develop patches.

---

_[View the full topic](https://discourse.julialang.org/t/about-julias-development-policy-regarding-windows/128011)._