Again, it is not me but the community that should decide what is part of the core functionality. I don’t understand why the community should not do this, I think Julia is a community project. There is an annual conference, you can held even elections there, form a governing body for the Julia project or whatever. Many projects have such a structure, I like for example how KDE and the Wikipedia are governed.
I read the announcement:
New option --trim creates smaller binaries by removing code that was not proven to be reachable from entry points. Entry points can be marked using Base.Experimental.entrypoint (#55047).
This thread is about the development policy. And my opinion is that the development should have all the time all 3 major OSes in mind. A feature that is announced as new should have been tested under all OSes - directly when the PRs are reviewed and merged. So after a merge the new feature should work under all OSes. Sure, it might have bugs, but it should work somehow, or call it “basically”. --trim is an example that does not work at all under Windows in the beta1.
And when it is known that a new feature does not work under all 3 OSes, then there should be a note/warning in the release notes about this.
One should also consider features that are experimental not to announce as if they will become stable features with the final release. And I got the impression that --trim will not be stable when 1.12 final will be released.
I also stated that my intention is not to blame anybody, but to give an impulse that the development policy is changed/improved to have all the time different OSes in mind.
Yes and when I started to give Julia a try, I tried Juliaup. That time the Download page gave me the impression that I have to use the Microsoft store, which is not possible (many companies have disabled the store for legal reasons).
So I directly downloaded Juliaup, but on executing the Juliaup.exe nothing happened.
And this is another example on how a changed policy would help. I simply did not undestand that I have to execute juliaup from a console.
Most Windows users like me don’t know a console. Also my clever colleagues holding a PhD in biology don’t know about a console. And why should they? But they are the target audience of Julia.
Personally, I developed a lot in my life and cannot use a console because whenever I had to I just copy/pasted something I found in docs or a forum and that occurred few times a year. I cannot memorize commands and i am a chamption in making typos. 
This thread is also about Windows and Windows users have other needs.
Portion manually split into A graphical Julia installer for Windows
As Windows user I need a graphical installer where I can select at least:
- the Julia version I want to install
- the install location
All larger projects I know provide a graphical installer for Windows and a way to use it without the Microsoft store. And that’s why I chose the graphical installer for Julia.
I cannot understand to hear in this thread that just because I need a graphical installer I made a mistake.
As I wrote installers for 2 lager projects (lyx.org and freecad.org) with over the time surely a million of installations, I could also write one for Julia but I have the feeling that there is not much interest.