wasm-astar
xtensa-rust-quickstart
wasm-astar | xtensa-rust-quickstart | |
---|---|---|
1 | 4 | |
416 | 340 | |
- | - | |
0.0 | 4.0 | |
about 1 year ago | about 2 years ago | |
Rust | Rust | |
MIT License | GNU General Public License v3.0 or later |
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.
wasm-astar
-
Rust Is for Professionals
A few years back I chose Rust as the language I was going to build side projects with. I started out building a wasm A* pathfinding demo [1] to get a better hang of it.
A little bit later I wrote a CLI task runner [2] which is defined by a simple markdown file. I find Rust to be perfectly aligned with the goals of a CLI utility: single deployable binary and very low startup cost.
Most recently I launched a side project [3] (a jigsaw puzzle website) using Rust as my backend API service. I've been slowly building up a server framework over the years and finally was able to put it to use! Yes, it took me much longer to ship something in Rust versus other languages I'm more familiar with. But after learning Rust for a few years now, it doesn't take me much more time to build a feature than it would in another language.
Early on, I ran into a lot of borrower issues and got stuck many times. But after I got over those problems, I realized that for any future hurdles I would face, I just needed to keep pushing and eventually I would find a solution. I have found that with game development or heavily stateful apps, I tend to run into borrower issues more often. But for an API service with a simple input and output, I almost never run into borrower issues.
[1]: https://github.com/jakedeichert/wasm-astar
xtensa-rust-quickstart
-
I have an ESP8266 and I want to learn how to program on bare metal using only Rust. Will I need to interoperate with C?
I made some experiments few months ago, with mild success. I cannot remember exactly what documentation/guide I followed, but it was probably the Xtensa Rust quickstart (or at least that should be a good start). I was able to compile a project that used pins, but I could not make wifi work (and I am using ESP8266 exactly because I need wifi).
-
Are there situations where it's better to use C++?
Xtensa. They've got a fork of LLVM that supports it that they're working toward getting upstreamed. The community has a fork of rustc that uses it (and a quickstart crate) while we wait for it to get upstreamed.
-
Can I write Watchy apps in Rust?
In theory yes, the watchy has a standard esp32, and rust works on the esp32. https://github.com/MabezDev/xtensa-rust-quickstart https://mabez.dev/blog/posts/esp32-rust/
- Rust Is for Professionals
What are some alternatives?
mask - 🎠A CLI task runner defined by a simple markdown file
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
tree-sitter - An incremental parsing system for programming tools
drm-fourcc-rs - Provides an enum with every valid Direct Rendering Manager (DRM) format fourcc
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!