tool-conventions
wagi
tool-conventions | wagi | |
---|---|---|
3 | 14 | |
287 | 867 | |
2.4% | 0.0% | |
5.6 | 1.8 | |
10 days ago | almost 2 years ago | |
Rust | ||
Artistic License 2.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.
tool-conventions
-
Isolates, MicroVMs, and WebAssembly (In 2022)
> Better interoperability
AFAIK, the examples you give all target a basic C ABI [0] or can be made to target the same ABI. In Rust, it means targeting wasm32-unknown-emscripten
The Rust team is also working on a "WASM ABI"[1] which would be useful in taking advantage of stuff like multi-value returns, and other compilers could just choose to target that. More likely, the C ABI on WASM will be updated to account for missing features, and that'll be the standard for interoperability in the WASM ecosystem.
[0]: https://github.com/WebAssembly/tool-conventions/blob/main/Ba...
[1]: https://github.com/rust-lang/lang-team/blob/master/design-me...
-
Features of a dream programming language: 2nd draft.
C ABI: Compatible with the C language Application Binary Interface (ABI). So code in the language is usable from other languages. Inspired by Zig. Since compiling to WASM is desirable, WASM's C ABI could probably be used, instead of a separate implementation towards the C ABI.
-
Crates for (mutable) statics with non const initialization.
There is maybe a solution. From what I found the linker will glue constructor functions and they have an associated priority. (look https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md here for the "linking meta data section"). I explored the ldd/wasm source code directory and it looks like there are also destructor functions. I have not found out in which sections such functions should be placed (after 1h of exploration). Would you like to pursue? I am ok to receive pushes or even share owner ship of the repository.
wagi
-
Reminiscing CGI Scripts
WAGI and WCGI are the WASM based spiritual successors.
https://github.com/deislabs/wagi
https://wasmer.io/posts/announcing-wcgi
-
A simple web server written in Awk
Compile a CGI program in any language to WASI, then use https://github.com/deislabs/wagi to run it.
-
Running WASI binaries from your HTML using Web Components
Yeah of course! They've got STDIN/STDOUT/STDERR and I've built a Virtual Filesystem. But if you're using WASI binaries locally they don't have that restriction.
You might be interested in WAGI: https://github.com/deislabs/wagi
And to catch up on WASI: https://xeiaso.net/talks/unix-philosophy-logical-extreme-was...
-
Waggy, the library for writing WAGI API handlers in Go
As I'm sure you've heard, WASM has been growing in popularity and use over the past few years. And with the creation of WASI (Web Assembly System Interface) and WAGI (Web Assembly Gateway Interface), WASM is starting to venture outside of running just in the browser. And in the case of WAGI, if you've been programming since the earlier days of the internet, it might feel very similar to CGI programming (and that's because it's based on CGI1.1!) WAGI provides a way for developers to define handlers for HTTP requests and route them to specific functions inside of, or entire, WASM modules. It does so by piping the headers of the incoming request to os.Args[1:], piping the body of the incoming request to os.Stdin, and writing the response to os.Stdout. (To learn more about configuring, routing, compiling, and deploying WAGI routes, as well as the limitations of WAGI routes, please consult the WAGI docs and the TinyGo WASM docs)
-
Rethinking Virtualization for Back Ends
What do you think of WAGI [1], which is basically CGI for WASM modules.
[1]: https://github.com/deislabs/wagi/blob/main/docs/writing_modu...
- Isolates, MicroVMs, and WebAssembly (In 2022)
-
The Promise of WASM
as serverless functions (https://github.com/deislabs/wagi)
-
Single Page Applications using Rust (with WASM)
I'm experimenting with WASM & Rust but with a different framework named wagi, there's a great video by Rainer Stropek & Stefan Baumgartner that gives a little introduction to it [0]
[0]: https://www.youtube.com/watch?v=9NDwHBjLlhQ
[1]: https://github.com/deislabs/wagi
-
Building a WebAssembly-powered serverless platform
Krustlet and WAGI are two such projects.
-
Introduction to Hippo: The WebAssembly PaaS
It does support it, the runtime we are currently using enables that -- see https://github.com/deislabs/wagi/blob/main/docs/writing_modu...
Good point on the docs, I will open an issue and add some information about it, thanks!
What are some alternatives?
ts-belt - 🔧 Fast, modern, and practical utility library for FP in TypeScript.
wasi-experimental-http - Experimental outbound HTTP support for WebAssembly and WASI
dwarf-2-sourcemap - A DWARF to SourceMaps converter for WASM
wasmer-python - 🐍🕸 WebAssembly runtime for Python
wyrcan
wasm-to-oci - Use OCI registries to distribute Wasm modules
ramda - :ram: Practical functional Javascript
wizer - The WebAssembly Pre-Initializer
krustlet - Kubernetes Rust Kubelet [Moved to: https://github.com/krustlet/krustlet]
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
io-ts - Runtime type system for IO decoding/encoding
wasi-vfs - A virtual filesystem layer for WASI.