Well, I do all of my projects in Rust now. Even little scripts I’d usually write in Python I often find myself grabbing Rust for. I’m comfortable with using Rust for pretty much any project at this point, that I decided that for a long-ish term stream project (ultimately a snapshot fuzzer for NT), I would want to do this in Rust.
The very first thought that comes to mind is to just build a MIPS executable from Rust, and just… run it. Well, that would be great, but unfortunately there were a few hiccups.
Imagine that – running Rust code on Windows NT 4.0 on MIPS led to some hiccups.
The author likes exotic, if you have to read the compiler code to figure out what the target and then have to write your own ELF loader you might be pretty far of the reservation. 🙂
He is pretty clear that this is more driven by enjoyment than practicality. It is probably not the case that legions of devs will end up using Rust to create applications targeting Windows NT 4.0–especially not on MIPS.
That said, it seems like the end result is going to be quite a functional Rust implementation that would allow the rest of us mere mortals to write somewhat normal looking Rust code that should more or less just work. That is kind of exciting even if it is target few of us care about.
The really amazing thing is that his driving objective appears to be using Rust to test Windows NT 4.0 on MIPS itself and to uncover bugs in the operating system. It is hard to understand what the practical motivation for that could be beyond fun and learning. It is not like Microsoft is going to be excited to receive a bunch of bug reports against Windows NT 4.0 on MIPS!!
You have to admit though–cool stuff. Also, as deep a dive as this is, I am quite impressed it was not much, much harder. It reflects really well on Rust.