capability-providers
wasmCloud official capability providers (by wasmCloud)
interfaces
wasmCloud API interfaces: smithy IDLs and shared libraries (by wasmCloud)
capability-providers | interfaces | |
---|---|---|
1 | 1 | |
78 | 34 | |
- | - | |
7.5 | 6.6 | |
2 months ago | 4 months ago | |
Rust | CSS | |
- | Apache License 2.0 |
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.
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.
capability-providers
Posts with mentions or reviews of capability-providers.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-17.
-
Which scripting languages work well embedded with Rust?
The native code ("provider") side of the interface also uses the smithy generated code. This lives in a separate repo - https://github.com/wasmCloud/capability-providers/blob/main/httpserver-rs/src/lib.rs .
interfaces
Posts with mentions or reviews of interfaces.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-01-17.
-
Which scripting languages work well embedded with Rust?
I like how wasmCloud does things - they define the interface using smithy like this https://github.com/wasmCloud/interfaces/blob/main/httpserver/httpserver.smithy (in the httpserver interface, the wasm side receives http requests as structs, and replies with responses as structs. The native-code side is responsible for listening on the TCP port etc. There are a bunch of other first-party interfaces, including an httpclient interface, for outgoing requests initiated by wasm). They then generate basic interface code for all supported languages from the smithy definitions. They also hand-write some helper functions, to make things easier on the wasm side (this isn't the same from language to language - there are more helpers for rust than other languages).
What are some alternatives?
When comparing capability-providers and interfaces you can also consider the following projects:
wasmCloud - wasmCloud allows for simple, secure, distributed application development using WebAssembly components and capability providers.
ApiV2-GraphQL-Docs - AniList API V2 GraphQL Documentation
dyon - A rusty dynamically typed scripting language
tl - The compiler for Teal, a typed dialect of Lua
hematita - A memory safe Lua interpreter
css.gg - 700+ Pure CSS, SVG, PNG & Figma UI Icons Available in SVG Sprite, styled-components, NPM & API and 6000 glyphs
riker - Easily build efficient, highly concurrent and resilient applications. An Actor Framework for Rust.
gluon - A static, type inferred and embeddable language written in Rust.
capability-providers vs wasmCloud
interfaces vs ApiV2-GraphQL-Docs
capability-providers vs dyon
interfaces vs tl
capability-providers vs hematita
interfaces vs css.gg
capability-providers vs riker
interfaces vs hematita
capability-providers vs tl
interfaces vs dyon
capability-providers vs gluon
interfaces vs gluon