mlatu VS wain

Compare mlatu vs wain and see what are their differences.

wain

WebAssembly implementation from scratch in Safe Rust with zero dependencies (by rhysd)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
mlatu wain
4 3
157 396
0.6% -
2.9 6.6
about 1 month ago 5 months ago
Rust Rust
GNU General Public License v3.0 or later MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

mlatu

Posts with mentions or reviews of mlatu. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-25.
  • Advantages of Functional Programming
    2 projects | /r/programming | 25 Nov 2021
    Caden Haustein has used the code for Kitten as the starting point for a language called Mlatu, which looks cool. I haven’t been writing about my PL work much, but I’ve still been doing stuff that’s related—although it may end up under a new name, not sure what I want to do with that yet.

wain

Posts with mentions or reviews of wain. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-24.
  • Take More Screenshots
    24 projects | news.ycombinator.com | 24 Jul 2022
    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...

What are some alternatives?

When comparing mlatu and wain you can also consider the following projects:

wasmi - WebAssembly (Wasm) interpreter.

flexible-vectors - Vector operations for WebAssembly

rust-wasm - A simple and spec-compliant WebAssembly interpreter

kitten - A statically typed concatenative systems programming language.

riscv-v-spec - Working draft of the proposed RISC-V V vector extension

learn-fpga - Learning FPGA, yosys, nextpnr, and RISC-V

Lifeslice - Automatically take webcam pics, screenshot, and other metrics throughout the day.

astro - A fun safe language for rapid prototyping and high performance applications

tropy - Research photo management

SATySFi - A statically-typed, functional typesetting system

wai - a wasm interpreter written by rust

reason - Simple, fast & type safe code that leverages the JavaScript & OCaml ecosystems