astro
wain
astro | wain | |
---|---|---|
2 | 3 | |
734 | 401 | |
0.4% | - | |
0.0 | 6.2 | |
9 months ago | 8 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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.
astro
-
What’s an actual use case for Rust
Some people tried using Rust to implement programming languages, right now I do not know any bigger language with compiler written in Rust but there was an attempt with astro. Match statements make parsing in Rust pretty comfortable.
-
First batch of PRs
I have tried figuring out what the project even was - it was in Astro. After some googling and reading I figured out.... I better not go deeper. It's some kind of a niche language, which may even be fun and great, but isn't used most of the time and isn't even finished. So even if I have learned it (which would be hard, considering no documentation), I wouldn't be able to transfer my skills as easily to another project, since chances are - it's not in Astro.
wain
- Wain: WebAssembly implementation from scratch in Safe Rust with 0 dependencies
-
Take More Screenshots
I think SIMD was a distraction to our conversation, most code doesn't use it and in the future the length agnostic, flexible vectors; https://github.com/WebAssembly/flexible-vectors/blob/master/... are a better solution. They are a lot like RVV; https://github.com/riscv/riscv-v-spec, research around vector processing is why RISC-V exists in the first place!
I was trying to find the smallest Rust Wasm interpreters I could find, I should have read the source first, I only really use wasmtime, but this one looks very interesting, zero deps, zero unsafe.
16.5kloc of Rust https://github.com/rhysd/wain
The most complete wasm env for small devices is wasm3
20kloc of C https://github.com/wasm3/wasm3
I get what you are saying as to be so small that there isn't a place of bugs to hide.
> “There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” CAR Hoare
Even a 100 line program can't be guaranteed to be free of bugs. These programs need embedded tests to ensure that the layer below them is functioning as intended. They cannot and should not run open loop. Speaking of 300+ reimplementations, I am sure that RISC-V has already exceeded that. The smallest readable implementation is like 200 lines of code; https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...
I don't think Wasm suffers from the base extension issue you bring up. It will get larger, but 1.0 has the right algebraic properties to be useful forever. Wasm does require an environment, for archival purposes that environment should be written in Wasm, with api for instantiating more envs passed into the first env. There are two solutions to the Wasm generating and calling Wasm problem. First would be a trampoline, where one returns Wasm from the first Wasm program which is then re-instantiated by the outer env. The other would be to pass in the api to create new Wasm envs over existing memory buffers.
See, https://copy.sh/v86/
MS-DOS, NES or C64 are useful for archival purposes because they are dead, frozen in time along with a large corpus of software. But there is a ton of complexity in implementing those systems with enough fidelity to run software.
Lua, Typed Assembly; https://en.wikipedia.org/wiki/Typed_assembly_language and Sector Lisp; https://github.com/jart/sectorlisp seem to have the right minimalism and compactness for archival purposes. Maybe it is sectorlisp+rv32+wasm.
If there are directions you would like Wasm to go, I really recommend attending the Wasm CG meetings.
https://github.com/WebAssembly/meetings
When it comes to an archival system, I'd like it to be able to run anything from an era, not just specially crafted binaries. I think Wasm meets that goal.
https://gist.github.com/dabeaz/7d8838b54dba5006c58a40fc28da9...
-
Making wasm executables with rust?
Hello guys i was looking at this project https://github.com/rhysd/wain and saw the c example from readme gif that converted c code to a wasm file and ran it. I tried reproducing that code in rust and when compiler and ran with wain it didnt print anything. Any suggestion on what im doing wrong? I created a cdylib and compiling to wasm32-unknown-unknown. Here is the c and rust code:
What are some alternatives?
serde-wasm-bindgen - Native integration of Serde with wasm-bindgen
wasmi - WebAssembly (Wasm) interpreter.
biowasm - WebAssembly modules for genomics
flexible-vectors - Vector operations for WebAssembly
awesome-wasm-langs - 😎 A curated list of languages that compile directly to or have their VMs in WebAssembly
rust-wasm - A simple and spec-compliant WebAssembly interpreter
devprotocol.xyz - Dev Protocol Website 2.0 🚀 Check our issue tracker for beginner-friendly issues
mlatu - A declarative concatenative programming language
WebsiteVue - The 7TV Web App with the Vue framework
riscv-v-spec - Working draft of the proposed RISC-V V vector extension
King-of-the-Garbage-Hill - Game in Discord - Six players get random characters with unique stats and abilities, each player can attack a selected target or defend. Victories give players points by moving them up the table. The leading player wins after ten rounds.
learn-fpga - Learning FPGA, yosys, nextpnr, and RISC-V