mos VS windows-rs

Interesting! I wrote an assembler for the 6502 a while ago that works along the same lines. It supports running unit tests from the command-line, has a built-in 6502 emulator, uses the language server protocol to allow refactoring and syntax highlighting in VS Code and even hooks the VS Code debugger up to Vice.

Still working on mos, my 6502 assembler + toolchain. I've spent some evenings getting up to speed with the Debug Adapter Protocol, which allows me to provide a debugger in supported IDEs (like Visual Studio Code). Currently I'm wiring up the VICE emulator to this.

I've just released version 0.2.0 of MOS, my assembler for 6502 CPUs. Apart from spending some additional time on docs, I've spent most of my time on building a Language Server and an initial VSCode extension that supports things like syntax highlighting, find definition, formatting, etc.

That CPU is still going strong. In fact, I'm currently building an assembler for the 6502 in Rust.

https://mos.datatra.sh

I just released version 0.1.0 of my 6502 assembler/formatter called MOS! Really happy about it, since it's the first side-project I've actually managed to get to this state in a VERY long time.

Having said that, you're welcome to follow the repo on GitHub.

I'd say Rust does have that big ticket ecosystem push. Microsoft has been embracing Rust lately, with things like official Windows bindings [1].

The bigger problem is just inertia: large game engines are enormous.

[1]: https://github.com/microsoft/windows-rs

It's a shame that, unlike with Win32, using WinUI places pretty harsh restrictions on which programming languages and environments you can use. Only C# and C++ are supported, the latter only with Microsoft compilers. For everything else, including Rust[1], Python and MinGW C/C++, there is no answer for OP's question, and the effect of this on the visual consistency of the Windows desktop is obvious - there is none. Every third-party app uses a different toolkit with a different look and feel, because the library providing the standard look and feel simply isn't available to the majority of developers.

[1]: https://github.com/microsoft/windows-rs/pull/1836

[0] https://github.com/microsoft/windows-rs

On Windows you'd need to call the LoadLibraryEx method. You'd also need a crate to call Win32 functions, I suggest windows-rs.

windows-rs, Microsoft's crate wrapping the Windows API, already includes the WDK, the special sdk for creating kernel code.

On windows, I'll probably use https://github.com/gabdube/native-windows-gui or https://github.com/microsoft/windows-rs both of them seem pretty solid.

*nod* It's an official Microsoft thing generated from official Microsoft API definition files. (The repo is at microsoft/windows-rs on GitHub.)

Microsoft offers official "bindings" to Win32 APIs through win32metadata. However, until recently, it did not include metadata for kernel-level functions or WDK. In early 2021, an issue was raised through windows-rs regarding this limitation, but progress was slow until now. Microsoft has finally released official metadata for WDK, which can be found on the wdkmetadata repository. The latest comment on the issue thread can be found here:

Is something wrong with https://github.com/deviceplug/btleplug or you haven't found it? You could also use bindings to platform libraries like https://github.com/microsoft/windows-rs and https://github.com/rust-mobile/ndk if btleplug doesn't have something fundamental to you.