Nine Rules for Running Rust on the Web and on Embedded

I recommend Rust when you want the speed of C++ and the memory-safety of Python. On top of that, with Rust you can build on more than 100,000 <a href="https://crates.io/" rel="noopener ugc nofollow" target="_blank">software libraries</a>. In addition, Rust offers the potential of running your code not just on a conventional computer, but also inside a web page or even on a robot. Running “almost everywhere”, however, comes with complications. This article is for Rust programmers who want to mitigate these complications. (It may also be of interest to those who want to see Rust’s “run almost everywhere” story.) First complication: Web pages and the embedded processors of robots don’t support general file IO. If your project is mostly about reading and writing files, it’s not a good candidate for running on a robot, other embedded processor, or a web page. Second complication: Porting code to run almost everywhere requires many steps and choices. Navigating these choices can be time consuming. Missing a step can lead to failure. This article aims to reduce this second complication by offering these nine rules, which we’ll later explore in detail <a href="https://towardsdatascience.com/nine-rules-for-running-rust-on-the-web-and-on-embedded-94462ef249a2">Website</a>