/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Mozilla, Intel, Red Hat, and Fastly announce the launch of Bytecode Alliance, which aims to take WebAssembly and other related open standards beyond the browser

Mozilla, Intel, Red Hat and Fast today announced the launch of the Bytecode Alliance, a new open-source group that focuses on …

TechCrunch Frederic Lardinois

Context & Ripple Effects

WebAssembly began in 2015 as a cross-vendor bet on a binary format for the web, launched by Google, Microsoft, Mozilla and others (the original WebAssembly coalition), and by late 2017 every major browser shipped it (universal browser support). With the in-browser phase complete, Mozilla, Intel, Red Hat and Fastly are now forming the Bytecode Alliance to carry the standard past the browser boundary.

The move follows a template this group knows well: the same cast helped launch the Alliance for Open Media for royalty-free video in 2015, pooling engineering under neutral governance rather than leaving each vendor to fork the stack. The Alliance matters because it decides who stewards WebAssembly as it escapes its original host.

First-order effects

  • Mozilla, Red Hat, Fastly and Intel gain a shared governance home for WebAssembly runtimes outside the browser, with Fastly positioned to apply it at the network edge and Red Hat on the server side.

Second-order effects

  • Vendors that backed WebAssembly in the browser but sit outside the Alliance — Google and Microsoft among them — must decide whether to join or watch a four-company consortium set the direction for out-of-browser deployments.

Third-order effects

  • If the Alliance-for-Open-Media pattern repeats, web-originated standards become the substrate for edge and server computing governed by multi-vendor consortia rather than any single platform owner.

The trend: Cross-vendor open-source alliances are becoming the standard vehicle for carrying web-born technologies like WebAssembly into general-purpose computing beyond their original host.

Discussion

  • @wasmweekly WebAssemblyWeekly on x
    The Bytecode Alliance - a new industry partnership that is looking to make a secure-by-default WebAssembly ecosystem outside of the browser https://hacks.mozilla.org/... - e.g. this could solve the worrying security vulnerabilities associated with using 3rd party npm packages
  • @loige @loige on x
    This is the best picture I have seen lately that describes how transient code dependencies can be very dangerous. Also interesting to see what #webassembly and the bytecode alliance are doing about this. Thanks @linclark! https://hacks.mozilla.org/... https://twitter.com/...
  • @sarbjeetjohal Sarbjeet Johal on x
    .@Mozilla @Intel @RedHat & @fastly today announced launch of #BytecodeAlliance, an open-source group focusing on creating new software foundations, building on standards like WebAssembly and WebAssembly System Interface (#WASI). @ellenfeaheny @furrier https://techcrunch.com/... h…
  • @natevw Nathan Vander Wilt on x
    This https://hacks.mozilla.org/... article [starting after “learn more about what we're building together"] near straight up nails what's needed for small modules to survive, imo. (e.g. what I naïvely imagined https://deno.land/ was aiming for.)