Windows native SDK support
I read the Modular page, Mojo page, specifically the "Get started with Mojo" page, and the "Roadmap & sharp edges" page. I cannot find any details on this. I also checked the various channels on this server and searched the mojo-chat forum by OS, Windows, etc.....
.
Approximately when (I realize no one has a crystal ball) does the dev team feel that the first (even available beta) Mojo SDK will be ready for Windows (not WSL2) native support.
.
Why I am asking. We are currently planning to shift from Python3 to Crystal which now has Windows native support, i.e. not just WSL2, although it is still not Tier 1, but frankly the compiler and VS Code extension are working very nicely. Python3 is solid, but it is too slow (even with NumPy) and at least for now Python does not ship default with Windows so we want a native binary .exe to ship our apps that does not require the client to join the Python3/PIP ecosystem...for various IT gatekeeper, etc. reasons.
.
We would really like to try out Mojo beyond the Jupiter notebook, web playground; i.e., get our hands dirty on the Windows native SDK with VS Code Extension.
.
If the timing is 2-3 months we can wait, if it is a year we cannot.
.
Thanks for any information that could be provided.
.
Approximately when (I realize no one has a crystal ball) does the dev team feel that the first (even available beta) Mojo SDK will be ready for Windows (not WSL2) native support.
.
Why I am asking. We are currently planning to shift from Python3 to Crystal which now has Windows native support, i.e. not just WSL2, although it is still not Tier 1, but frankly the compiler and VS Code extension are working very nicely. Python3 is solid, but it is too slow (even with NumPy) and at least for now Python does not ship default with Windows so we want a native binary .exe to ship our apps that does not require the client to join the Python3/PIP ecosystem...for various IT gatekeeper, etc. reasons.
.
We would really like to try out Mojo beyond the Jupiter notebook, web playground; i.e., get our hands dirty on the Windows native SDK with VS Code Extension.
.
If the timing is 2-3 months we can wait, if it is a year we cannot.
.
Thanks for any information that could be provided.
