not-yet-awesome-embedded-rust
fantoccini
| not-yet-awesome-embedded-rust | fantoccini | |
|---|---|---|
| 5 | 4 | |
| 114 | 1,444 | |
| 0.0% | - | |
| 0.0 | 7.2 | |
| over 1 year ago | 5 days ago | |
| Rust | ||
| Creative Commons Attribution Share Alike 4.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
not-yet-awesome-embedded-rust
-
Rust – Are We Game Yet?
And a list of things missing: https://github.com/rust-embedded/not-yet-awesome-embedded-ru...
-
Tips on switching careers from embedded C to Rust
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.
-
James Web Space Telescope runs on C++ code.
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)
-
What libraries do you miss from other languages?
Not Yet Awesome Embedded Rust
-
Things you can’t do in Rust (and what to do instead)
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.
fantoccini
-
Looking for Selenium Crates that Only Require Chrome Driver Binary Path
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):
-
"Day in the Life" of open-source development in Rust [video]
Look at how much easier the code is to read (and how much less error-prone it is) with the diff though!
-
Hey Rustaceans! Got a question? Ask here! (26/2022)!
You'll need a web driver to parse and execute the client-side JS scripts. I would recommend fantoccini for a web driver API.
-
What libraries do you miss from other languages?
https://github.com/jonhoo/fantoccini is inspired by Puppeteer.
What are some alternatives?
not-yet-awesome-rust - A curated list of Rust code and resources that do NOT exist yet, but would be beneficial to the Rust community.
thirtyfour - Selenium WebDriver client for Rust, for automated testing of websites
tlaplus - TLC is a model checker for specifications written in TLA+. The TLA+Toolbox is an IDE for TLA+.
cloudscraper - A Python module to bypass Cloudflare's anti-bot page.
wg - Coordination repository of the embedded devices Working Group
rust-headless-chrome - A high-level API to control headless Chrome or Chromium over the DevTools Protocol. It is the Rust equivalent of Puppeteer, a Node library maintained by the Chrome DevTools team.
ceres-solver - A large scale non-linear optimization library
sea-query - 🔱 A dynamic SQL query builder for MySQL, Postgres and SQLite
rusthunter - RustHunter is a modular incident response framework based on Rust and Ansible to build and compare environmental baselines.
Ink - 🌈 React for interactive command-line apps
shiplift - 🐳 🦀 rust interface for maneuvering docker containers