redshirt
awesome-wasm-runtimes
Our great sponsors
| redshirt | awesome-wasm-runtimes | |
|---|---|---|
| 3 | 8 | |
| 1,418 | 1,267 | |
| - | - | |
| 0.0 | 1.9 | |
| about 1 year ago | about 2 months ago | |
| Rust | ||
| GNU General Public License v3.0 only | - |
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.
redshirt
-
Web Assembly OS guidance
As seen in this projects : redshirt, Kwast wasmachine.
- The redshirt operating system is an experiment to build some kind of operating-system-like environment where executables are all in Wasm and are loaded from an IPFS-like decentralized network.
-
An OS made from Rust other than Redox
Have you seen https://github.com/tomaka/redshirt
awesome-wasm-runtimes
-
Extism Makes WebAssembly Easy
Firecracker is a fine technology, but serverless companies have started taking advantage Wasm's faster start-up times for use cases of running Wasm on the server (https://www.youtube.com/watch?v=yqgCxhPAao0). The deny by default security policy makes Wasm a great choice to run your code in isolation, particularly for maximizing hardware resources in the multi-tenant environments these serverless companies operate.
In the past few years, we have seen more use cases of Wasm emerge outside of the browser. JavaScript engines are now just a fraction of the total number of runtimes available. Wasmtime, Wasmer, WasmEdge, wazero are popular ones for non-browser use cases like blockchain, serverless, and edge computing (although Cloudflare uses V8's Wasm engine). WAMR is a popular one for cyber physical/IoT devices. There's a nice list here: https://github.com/appcypher/awesome-wasm-runtimes
-
I think [...] the "future of computing" is going to be [...] CISC. I’ve read of IBM mainframes that have [hardware instructions for] parsing XML [...]; if you had garbage collection, bounds checking, and type checking in hardware, you’d have fewer and smaller instructions that achieved just as much.
There's plenty of other ways to interact with Wasm, most of which are secure. (Wasmtime is the one I'm most familiar with, which is why I linked to it.)
-
Lunatic is an Erlang-inspired runtime for WebAssembly
Yeah, this is one of many non-browser runtimes, e.g. see https://github.com/appcypher/awesome-wasm-runtimes
Lunatic is more opinionated than most of these or node, though, in that it's trying to emulate a particular concurrent system design pattern borrowed from Erlang/BEAM.
-
Web Assembly OS guidance
There's an overview of different WASM runtimes with features: https://github.com/appcypher/awesome-wasm-runtimes
- Wasmer – The Universal WebAssembly Runtime
-
What to learn in 2022
Now, the creation Bytecode Alliance, the development of multiple WebAssembly runtimes and the work of the W3C WebAssembly Community Group is why I belive it will get popular, but the capability-based security model is why I want it to get popular.
-
Ho Ho Ho, WasmEdge 0.9.0 is here!
⚖ I think it's really cool that a plugin author could compile their C++ to .wasm such that a single plugin binary can run on either Linux or Windows (don't need an x86 .dll, x64 .dll, x86 .so, x64 .so...) and in a sandbox (no arbitrary syscalls or Win32 calls, just the interfaces given to it), while still getting near native AOT speed. Though, it's hard to judge which one to choose from now with all the wasm engines that are available (https://github.com/appcypher/awesome-wasm-runtimes), with wasmtime or inNative being two others I've considered for my project. I'll definitely look into this one though, given it supports many of the newer proposals.
-
Why WebAssembly is innovative even outside the browser
Numerous native runtimes for webassembly already exist[0], with the current popular choices apparently being Wasmer[1] and Wasmtime[2].
All one would need to do (AFAIK) is ship a client for all major platforms, as is done with Electron (and web browsers themselves, and everything else.)
What are some alternatives?
rust-libp2p - The Rust Implementation of the libp2p networking stack.
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
kerla - A new operating system kernel with Linux binary compatibility written in Rust.
Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
rust-raspberrypi-OS-tutorials - :books: Learn to write an embedded OS in Rust :crab:
Odin - Odin Programming Language
aft - aft - advanced file transfer.
wasm-micro-runtime - WebAssembly Micro Runtime (WAMR)
aWsm - WebAssembly ahead-of-time compiler and runtime. Focuses on generating fast code, simplicity, and portability.
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
mork - Application for sending files p2p written in rust
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).