fantoccini VS not-yet-awesome-embedded-rust

You can run the binary yourself. I'm using the following code with https://github.com/jonhoo/fantoccini, but I suspect it would work with thirtyfour too (thirtyfour builds on top of fantoccini):

Look at how much easier the code is to read (and how much less error-prone it is) with the diff though!

You'll need a web driver to parse and execute the client-side JS scripts. I would recommend fantoccini for a web driver API.

https://github.com/jonhoo/fantoccini is inspired by Puppeteer.

And a list of things missing: https://github.com/rust-embedded/not-yet-awesome-embedded-ru...

Building a portfolio is a great idea. Also you can find various areas to contribute to Rust. That would give you great exposure. Check out the not yet awesome rust repo (https://github.com/rust-embedded/not-yet-awesome-embedded-rust) for ideas. Also take a look at the rust foundation grant program, it’s open for applications now. There’s also the “this week in Rust” newsletter (https://this-week-in-rust.org) where job openings relative to Rust are also listed. Lastly, you can check my bio for a link where I provide a list of project ideas for different areas in embedded including Rust.

See Not Yet Awesome Embedded Rust for some ongoing work to build out the ecosystem, it's not ready yet. (this is a play on various "Awesome XYZ Rust" lists that have resources for different topics)

Not Yet Awesome Embedded Rust

Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.