3 ms·
Well they bring in the language and its runtime to windows development via WinRT. They don't bring WinRT to Rust. This is the windows team writing adapters for
by oaiey 6y ago
Well they bring in the language and its runtime to windows development via WinRT. They don't bring WinRT to Rust. This is the windows team writing adapters for their COM API surface. They do the same for C++, C#, JS and now Rust.
- Spivak 6y agoFor people who have not lived in the Windows world this would be like GNOME writing Rust Glib bindings.
- kyriakos 6y agoJS? can you point me to that?
- oaiey 6y agoSearch WinJS. However, i agree with the sibling comment that this is a maintenance only story.
- ptx 6y agoDidn't they remove the JavaScript WinRT projection? The docs[1] describing how to call a WinRT component from JS say: Universal Windows Platform (UWP) projects are not supported in Visual Studio 2019. See JavaScript and TypeScript in Visual Studio 2019. To follow along with this section, we recommend that you use Visual Studio 2017. See JavaScript in Visual Studio 2017. [1] https://docs.microsoft.com/en-us/windows/uwp/winrt-components/walkthrough-creating-a-basic-windows-runtime-component-in-cpp-and-calling-it-from-javascript-or-csharp https://docs.microsoft.com/en-us/windows/uwp/winrt-component...
- contextfree 6y agoSort of, it was/is built in to Chakra (the JS engine in IE9+, old Edge, and the original UWP WebView based on those browser engines) and hasn't been ported to the new Chromium-based Edge or the WebView2 based on it. There's also a separate NodeRT projection for generating Node/Electron modules: https://github.com/NodeRT/NodeRT https://github.com/NodeRT/NodeRT