Skip To Main Content
Bytecode Alliance on Muck Rack

Bytecode Alliance

As seen in: Markets Insider, TechCrunch, Yahoo Finance, Business Wire, CoinDesk, Benzinga, Neowin, InfoWorld, KTLA-TV (Los Angeles, CA), Morningstar and
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work. Claim your profile

Get in touch with Bytecode

Contact Bytecode, search articles and posts on X, monitor coverage, and track replies from one place.

Learn more about Muck Rack

Actions

Share this page

Is this you?

As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile

Articles

WebAssembly JVM Evolution: Performance, Portability, and Endive Transition

|
By Bytecode Alliance
| TechGig Learn Complete Grow
Andrea Peruffo highlighted WebAssembly's expansion beyond browsers to the server-side JVM, citing advancements in performance and crucial use cases. The Chicory runtime is also transitioning to Endive under the Bytecode Alliance for enhanced community governance. WebAssembly is expanding to server-side JVM, enhancing software portability and security. Performance improved via JIT compilation, moving beyond slow interpreters for Wasm runtimes.
Open in Who Shared Issue with article?

WASI 0.3 Launched

|
By Bytecode Alliance, Bailey Hayes, Yosh Wuyts
| bytecodealliance.org
WASI 0.3 is official, and async is now native to WebAssembly Components. The WASI Subgroup voted to ratify WASI 0.3.0, rebasing WASI onto the WebAssembly Component Model’s async primitives. The 0.3.0 specification is now stable, and runtime and toolchain support is landing now. The work that wasi:io in WASI 0.2 used to do (pollables, input-streams, output-streams) is now part of the canonical ABI, where the Component Model now offers these primitives natively.
Open in Who Shared Issue with article?

PEP 816 – WASI Support | peps.python.org

|
By Bytecode Alliance
| python.org
Specification The WASI and WASI SDK version supported by a CPython version in CI or its stable Buildbot builder when b1 is released MUST be the version to be supported for the lifetime of that Python version after this PEP is accepted. If there is a discrepancy between CI and the Buildbot builder for some reason, the WASI maintainers as specified by PEP 11 will choose which sets of versions will be designated as the versions to support.
Open in Who Shared Issue with article?
See all 456 licensed articles (459 Total)