wit-bindgen
fp-bindgen
wit-bindgen | fp-bindgen | |
---|---|---|
27 | 24 | |
887 | 469 | |
3.5% | 0.4% | |
9.4 | 5.3 | |
1 day ago | 4 days ago | |
Rust | Rust | |
Apache 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.
wit-bindgen
- Wit-Bindgen
-
WASM by Example
The component model is already shipping in Wasmtime, and will be stable for use in Node.js and in browsers via jco (https://github.com/bytecodealliance/jco) soon. WASI Preview 2 will be done in December or January, giving component model users a stable set of interfaces to use for scheduling, streams, and higher level functionality like stdio, filesystem, sockets, and http on an opt-in basis. You should look at wit-bindgen (https://github.com/bytecodealliance/wit-bindgen) to see some of the languages currently supported, and more that will be mature enough to use very soon (https://github.com/bytecodealliance/componentize-py)
Right now jco will automatically generate the JS glue code which implements a Component Model runtime on top of the JS engine's existing WebAssembly implementation. So, yes, Components are a composition of Wasm Modules and JS code is handling passing values from one module/instance to another. You still get the performance benefits of running computation in Wasm.
One day further down the standardization road, we would like to see Web engines ship a native implementation of the Component Model, which might be able to make certain optimizations that the JS implementation cannot. Until then you can consider jco a polyfill for a native implementation, and it still gives you the power to compose isolated programs written in many languages and run them in many different contexts, including the Web.
(Disclosure: I am co-chair of WASI, Wasmtime maintainer, implemented many parts of WASI/CM)
-
Spin 2.0 – open-source tool for building and running WASM apps
Thank you!
To your point, the primary consideration for choosing the languages is their support for WebAssembly, and WASI in particular.
Due to Spin's heavy use of WASI and the component model, languages that have first party support in the WIT bindings generator (https://github.com/bytecodealliance/wit-bindgen) are the easiest to implement, followed by languages that can be built on top of the support for those with first party support.
For example, the JavaScript support is built by embedding QuickJS (in particular, Shopify's Javy project — https://github.com/fermyon/spin-js-sdk), which then uses the Rust SDK.
-
Rust + WASM + Typescript [+ React]
There are many options, but what worked best for me is compiling with cargo-wasi and loading the resulting Wasm file with browser_wasi_shim. Using wasm32-wasi instead of wasm32-unknown-unknown requires a bit more work (the communication with JS has to be set up manually), but gives the flexibility of having just a Wasm file that can be dropped in and loaded dynamically. (There's wit-bindgen for generating wrapping code according to an interface definition but I didn't have much success with it.)
-
Introducing - Wasmer Runtime 4.0
I've been playing with creating a go version of the abi for use with wit-bindgen because the current one uses cgo https://github.com/bytecodealliance/wit-bindgen
-
What in Rust is equivalent to C++ DLLs (shared libraries), or what do I need to do to support extensions in my app?
wit-bindgen - Language Binding Generator for WASM Interface Type
-
Quick tip: Numeromancy, WebAssembly and SingleStoreDB Cloud
wit-bindgen-rust = { git = "https://github.com/bytecodealliance/wit-bindgen.git", rev = "60e3c5b41e616fee239304d92128e117dd9be0a7" }
-
Using WASM for a plugin system in Rust? (generate code at runtime and then hot reloading it as a library)
Yep, you're right. For this, there are a few options. The ones most relevant to you are fp-bindgen, which targets Wasmer, and wit-bindgen, which targets wasmtime.
-
Introducing Ambient 0.1: a runtime for building high-performance multiplayer games and 3D applications, powered by Rust, WebAssembly and WebGPU
Are you evaluating if WebAssembly Component Model, its WIT format and related tooling like wit-bindgen could be a good fit for your multiple languages support?
-
Using SingleStoreDB, WebAssembly and GraphQL
[package] name = "sentiment" version = "0.1.0" edition = "2021" # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html [dependencies] wit-bindgen-rust = { git = "https://github.com/bytecodealliance/wit-bindgen.git", rev = "60e3c5b41e616fee239304d92128e117dd9be0a7" } vader_sentiment = { git = "https://github.com/ckw017/vader-sentiment-rust" } lazy_static = "1.4.0" [lib] crate-type = ["cdylib"]
fp-bindgen
-
How feasible is to create a WASM plugin system in Rust?
fp-bindgen is a library that can help you if you to write custom plugin APIs for such a use case: https://github.com/fiberplane/fp-bindgen
-
Using WASM for a plugin system in Rust? (generate code at runtime and then hot reloading it as a library)
Yep, you're right. For this, there are a few options. The ones most relevant to you are fp-bindgen, which targets Wasmer, and wit-bindgen, which targets wasmtime.
-
Show HN: Notion-style editing meets infra-debugging tools
1. Integrations with some of the most popular open-source observability tools: Prometheus, Elasticsearch, Loki, and more integrations with other tools are on the way.
2. A WASM-based plugin system for integrations (which, in the future, will allow for 3rd-party integrations to be built and run securely) along with an open-source bindings generation framework https://github.com/fiberplane/fp-bindgen
3. An advanced block-based editor: You can run PromQL, LogQL, and Lucene queries, and display Prometheus charts and Elasticsearch or Loki log tables alongside the rest of your content. Filter your metrics, and logs, highlight important records, and collaborate on your infrastructure data.
4. Templates are written in Jsonnet language and allow you to programmatically create notebooks and automate your Fiberplane workflows. They can have Webhook URLs attached to them allowing you to connect Fiberplane with your alert tools (or really anything that can send a Webhook request) making them a powerful tool for incident runbooks and post-mortems.
5. A CLI that allows you to share your terminal debugging output with your team with a simple command.
6. Our backend is all in Rust, using the Axum web framework. It also includes some fun parts like a custom Operation Transformation library that’s used directly from the backend and compiled to WASM for the frontend.
Fiberplane was created out of our own experience of running large distributed systems. There was too much context switching when working with monitoring and observability tools. Over the past two years, we’ve been working hard on the first real-time collaboration notebook for the observability space to make infrastructure debugging faster and easier.
We’re launching into public availability and looking to create the best debugging and incident resolution workflow tool for developers, Site Reliability, and DevOps engineers. We would love your feedback.
-
We're working on a new WASM/Rust scripting system. Here I'm playing around with a script that changes the day/night cycle.
Why did you choose wit-bindgen over fp-bindgen? fp-bindgen seems to be better suited for Rust-to-Rust communication.
- Start debugging, we'll handle the rest
- Building collaborative notebooks for debugging infrastructure
- Better Workflows for DevOps and Site Reliability Engineers
-
easy to use Plugin API in rust?
Checkout https://github.com/fiberplane/fp-bindgen
- What are some Rust-using companies in the Netherlands?
What are some alternatives?
lunatic - Lunatic is an Erlang-inspired runtime for WebAssembly
wasmtime - A fast and secure runtime for WebAssembly
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
redpanda - Redpanda is a streaming data platform for developers. Kafka API compatible. 10x faster. No ZooKeeper. No JVM!
kwasm - Proof of concept React-ish UI library, powered by WebAssembly
fingerprintjs - Browser fingerprinting library. Accuracy of this version is 40-60%, accuracy of the commercial Fingerprint Identification is 99.5%. V4 of this library is BSL licensed.
webassembly-tour - ⚙️ Take you through a tour of WebAssembly (WASM targets on WASI) with wasmCloud, Krustlet, WAGI, etc. 🌟 Give it a star if you like it.
Appwrite - Your backend, minus the hassle.
wasi-experimental-http - Experimental outbound HTTP support for WebAssembly and WASI
n8n - Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
component-model - Repository for design and specification of the Component Model
minimal_wasm_template