Weāre excited to see our friends again as we embark on a whistle-stop tour of two of our favorite European events (and cities) in the 2024 conference calendar: WASM I/O, Barcelona and KubeCon + CloudNativeCon Europe 2024, Paris. With the release of WASI 0.2 and the WebAssembly component model, weāre taking wasmCloud 1.0 on tourāintroducing it to cloud native developers, and platform engineers, as the best place to bring components to life in production environments.
4 posts tagged with "wasmCloud"
View All TagswasmCloud 0.82: WASI 0.2, OTEL logging, and more
Weāre proud to announce wasmCloud 0.82āthe last stop on the road to our 1.0 milestone. This release is all about preparing the way, bringing:
- Full and stable support for WASI 0.2 APIs
- Quality-of-life improvements for builds and deployment
- Support for OpenTelemetry logging
- Additional bug-fixes and improvements
Bring Your Own Wasm Components: Run Python (and any other language) in wasmCloud
WASI 0.2.0 is in the wild, pushing forward common standards for portable, language-agnostic components and interfaces. That means it just got a whole lot easier to create WebAssembly components from any languageāand have them work together with other components of any provenance. Better still, it's now possible to "bring your own Wasm components" from any language that compiles to WASI 0.2.0 and run them as distributed apps in wasmCloud.
WASI 0.2.0 and Why It Matters
WASI Preview 2 officially launched! After a vote in the WASI Subgroup of the W3C WebAssembly Community Group, the standard set of interfaces included in the launch of Preview 2, aka WASI 0.2.0, is ready for use by library implementers. We've been closely tracking the different release candidates of WASI 0.2.0 over the last 6 months, and wasmCloud will update its runtime WIT definitions to the pinned versions in just a few days.