1. 9
  1.  

  2. 1

    I’ve written Rust for fun, and C# professionally. This thing is awesomely bizarre. I feel like I want to try it, even though I have no idea what I could practically use it for.

    Rust is mostly good for CLI apps. It doesn’t connect very well with any UI frameworks that I know of. It makes a pretty decent web server, but doesn’t interact that well with any other servers. I guess you could connect it to ASP.NET, but I don’t really see the point. It might be interesting to try to use WinForms from Rust to create a native UI though.

    C# is mostly good for Windows desktop apps and ASP.NET web servers. It’ll do for CLI apps too. It’s mostly pretty fast. I’m having trouble thinking of something you’d want to pull Rust in for. Maybe a bit of extra speed somewhere?

    Maybe one of the better things to do would be to be able to use some weird proprietary .NET library from some vendor in a Rust app. God knows there’s enough of those out there.

    It’d also be an interesting challenge to try and connect the .NET Task/async/await system to the Rust Future/async/await system somehow. They sound so similar, but they operate in very different ways. I still haven’t entirely figured out Rust Futures. Maybe the integration would look like the .NET Task executor and green thread system taking the place of Tokio?

    1. 1

      My understanding is that he’s using rust, generating llvm bytecode and transpiling to .net CLR? Is that correct?

      1. 1

        CLR is Common Language Runtime. “Converting LLVM bitcode to CIL generally works” (Common Intermediate Language). Just read the thing, it’s quite accessible.