# wasm WebAssembly (Wasm) is a binary instruction format for a stack-based virtual machine and a portable compilation target for programming languages. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Electric is joining team Neon at Databricks DevFeed: [Electric is joining team Neon at Databricks]() Original publisher: [Read original article]() Author: Nikita Shamgunov Published: 2026-08-11T13:00:00Z Content type: news Language: en Sources: [Blog -- Neon Docs]() Topics: [databricks](), [Database](), [real-time](), [wasm](), [AI-assisted coding]() Tags: [agentic](), [company](), [postgres](), [real-time](), [sync](), [wasm]() ### AI overview Electric is joining Neon within Databricks, bringing PGlite and its real-time Postgres synchronization technology. The article presents these as primitives for lightweight applications and agent workloads. ### Source excerpt Today Databricks announced that Electric, the team behind PGlite and the Electric sync engine, is joining Databricks. We have our own reason to celebrate: Electric is joining the Neon team within Databricks, bringing lightweight WASM Postgres + real-time sync to Neon. ## Durable Objects are Made for Agents DevFeed: [Durable Objects are Made for Agents]() Original publisher: [Read original article]() Author: Calvin French-Owen Published: 2026-07-22T12:00:00Z Content type: opinion Language: en Sources: [Calvin French-Owen]() Topics: [Cloudflare](), [Serverless](), [SQLite](), [V8](), [event driven](), [WebSocket](), [wasm]() Tags: [cloudflare](), [event-driven](), [serverless](), [sqlite](), [v8](), [websockets]() ### AI overview An opinionated technical article explains why Cloudflare Durable Objects can be a strong primitive for building agents and other stateful products. It describes their serverless V8 execution model, per-object SQLite storage, ID-based request routing, event-driven structure, and potential shortcomings. ### Source excerpt I've spent the last few months building almost exclusively on Cloudflare Durable Objects. They're a near-perfect primitive for building agents--here's where they shine, and where they fall short. ## GC and Exceptions in Wasmtime DevFeed: [GC and Exceptions in Wasmtime]() Original publisher: [Read original article]() Author: Nick Fitzgerald Published: 2026-07-20T00:00:00Z Content type: release Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [Exception](), [toolchains]() Tags: [compilation](), [exceptions](), [release](), [toolchains](), [wasm](), [webassembly]() ### AI overview Wasmtime 47 enables the Wasm GC and exceptions proposals by default. The article explains how Wasm GC supports languages with object-and-reference data models by letting the runtime manage types and lifetimes, while the exceptions proposal provides more efficient exception handling for WebAssembly compilation targets. ### Source excerpt The Wasm GC and exceptions proposals are both enabled by default in today's Wasmtime 47 release! We are excited to help bring more languages to WebAssembly and everywhere that Wasmtime runs. Getting to this point involved large Wasmtime changes and represents the culmination of years of engineering effort. ## We compiled our TypeScript parser to WASM DevFeed: [We compiled our TypeScript parser to WASM]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-07-15T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Parser](), [Rust](), [wasm](), [browser](), [TypeScript]() Tags: [browser](), [parsing](), [rust](), [typescript](), [wasm]() ### AI overview Encore describes compiling its Rust parser for TypeScript infrastructure declarations to WebAssembly so it can run in the browser. The browser-based parser supports reproducing parser errors from code snippets and shared links, and powers the tsparser.encore.dev playground. ### Source excerpt How we compiled the Rust parser that reads infrastructure out of Encore code so it runs in the browser, and how we use it to reproduce the parser errors people report. ## wasmCloud 2.5.0: Wasmtime 46, WASI 0.3, and multiplexed WebAssembly host plugins DevFeed: [wasmCloud 2.5.0: Wasmtime 46, WASI 0.3, and multiplexed WebAssembly host plugins]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Streaming]() Tags: [helm](), [release](), [streaming](), [wasi](), [wasm](), [webassembly]() ### AI overview wasmCloud 2.5.0 is released with Wasmtime 46 and WASI 0.3 enabled by default. It adds configurable top-level WebAssembly proposals, multiplexed host-plugin interfaces, async-shaped and WIT improvements, Helm chart hardening, a host-controller refactor, and quality-of-life fixes. ### Source excerpt wasmCloud 2.5.0 ships with Wasmtime 46, WASI 0.3 on by default, configurable WebAssembly proposals, and `(implements ..)` multiplexing for host plugins. ## Using vibes to rewrite my blog DevFeed: [Using vibes to rewrite my blog]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-06-27T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [gatsby](), [React](), [MDX](), [Syntax Highlighting](), [Claude](), [wasm](), [codex]() Tags: [article](), [blog](), [claude](), [codex](), [gatsby](), [mdx](), [react](), [syntax-highlighting]() ### AI overview The author describes rewriting the swizec.com blog after Gatsby became difficult to maintain and slow to deploy. They experiment with TimberJS, a React Server Components-based framework, to render MDX with file-based routing, metadata, embeds, image generation, and server-side syntax highlighting. The rewrite reduced reported deployment time from more than 45 minutes to about 3 minutes, while the author emphasizes that effective vibe coding still requires technical knowledge. ### Source excerpt The death of engineering has been greatly exaggerated. You still need to know what you're doing. ## June 2026 newsletter DevFeed: [June 2026 newsletter]() Original publisher: [Read original article]() Author: Mark Needham Published: 2026-06-18T00:00:00Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [data](), [Open Source](), [real-time](), [wasm](), [WebAssembly](), [Apache Iceberg](), [Parser]() Tags: [analytics](), [clickhouse](), [data](), [database](), [engineering](), [open-source](), [performance](), [real-time](), [release](), [systems](), [wasm](), [webassembly]() ### AI overview The June 2026 ClickHouse newsletter marks the project's tenth anniversary, highlights its open-source community, and covers contributions to WebAssembly user-defined functions, geospatial and Iceberg functionality, and performance improvements in ClickHouse 26.5. ### Source excerpt Welcome to the June 2026 ClickHouse newsletter, which will round up what's happened in real-time data warehouses over the last month. ## wasmCloud 2.4.0: HPA + KEDA autoscaling, multi-handler workloads, pluggable NATS DevFeed: [wasmCloud 2.4.0: HPA + KEDA autoscaling, multi-handler workloads, pluggable NATS]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-17T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [Kubernetes](), [autoscaling](), [Messaging](), [Security]() Tags: [autoscaling](), [handler](), [helm](), [kubernetes](), [messaging](), [net-11-preview-7](), [opentelemetry](), [prometheus](), [security](), [wasmcloud]() ### AI overview wasmCloud 2.4.0 adds Kubernetes-native autoscaling for Wasm workloads through HPA and KEDA, multi-handler messaging workflows, expanded Helm configuration, a redesigned host plugin API, and a Wasmtime 45.0.2 security update. ### Source excerpt wasmCloud 2.4.0 brings Kubernetes-native autoscaling for Wasm workloads via HPA and KEDA, multi-handler messaging in wash dev, a Helm chart NATS overhaul with split scheduler/data URLs, a NATS-backed operator liveness probe, and a Wasmtime 45.0.2 security bump. ## The Road to Component Model 1.0 DevFeed: [The Road to Component Model 1.0]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [browser]() Tags: [apis](), [architecture](), [async](), [binaries](), [browser](), [compatibility](), [interfaces](), [polyfill](), [production](), [wasi](), [wasm](), [webassembly]() ### AI overview This article explains the path toward a stable, formally specified WebAssembly Component Model 1.0. It reviews how the Component Model and WASI relate, describes the Component Model as a foundational layer with WASI providing system-resource interfaces, and notes that both are already used in production while their specifications continue to evolve. ### Source excerpt WASI P3 is almost here, bringing native async support to the WebAssembly System Interface (WASI) and Component Model. In this post, we're looking to the next big milestone: a stable, formally specified Component Model 1.0. At February's Bytecode Alliance Plumbers Summit, Luke Wagner and Alex Crichton gave a preview of what the path to a stable 1.0 actually looks like. At Wasm I/O 2026 in Barcelona in March, Luke expanded on that vision. So let's take a look at where the Component Model is heading. ## What's new in Swift: May 2026 Edition DevFeed: [What's new in Swift: May 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-06-03T21:45:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [SDKs](), [Back end](), [iOS](), [MLX](), [wasm](), [WebAssembly](), [AWS Lambda]() Tags: [aws](), [aws-lambda](), [backend](), [community](), [conferences](), [ios](), [local](), [mlx](), [news](), [releases](), [serverless](), [swift](), [wasm](), [webassembly]() ### AI overview A curated May 2026 digest of Swift community activity, including meetup videos, backend development resources, the Temporal Swift SDK, AWS Lambda, MLX for iOS, and Swift for WebAssembly updates. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. To start, we're focusing on some of the many local meetup groups sharing Swift content: Around the world, local meetup groups and conferences bring Swift developers together, and some even predate Swift itself! Many have YouTube channels where they share videos from their events, so you can tune in remotely. Let's highlight a few. In May the SF Swift meetup hosted a talk by Dan Federman, Agentify Your Swift Repo, which covers building an agent for CI and review feedback. Swift Barcelona has a dedicated YouTube presence, while some groups, like the new MLX India meetup, post event playlists, including a recent talk about using MLX Swift in iOS apps that's worth checking out. And there's even a community-organized Swift Community Meetups YouTube channel, which hosts meetups online and is home to a series of cross-platform Swift talks. These groups support developers in a few ways worth calling out: Local community: they're building local connections among Swift developers and organizations. Room for experimentation: by being less formal and sometimes featuring works in progress, meetups create space to share ideas, get feedback, and learn from one another. I encourage more folks to get involved in their local Swift meetup. And if your group starts publishing content and videos, please share on the Swift Forums in the Community Showcase category. -- Dave Lester Now on to other news about Swift: Videos to watch Interested in using Swift for backend server development? Mohammad Azam posted a livestream recording of Introduction to Hummingbird, a walkthrough of the web framework covering installation and development basics. Meet the Temporal Swift SDK, from Replay 2026, introduces the SDK that brings Temporal's durable workflows (long-running processes that survive crashes, retries, and restarts without losing state) to Swift. The SDK recently reached ## How Wasm components enable pluggable tooling through interposition DevFeed: [How Wasm components enable pluggable tooling through interposition]() Original publisher: [Read original article]() Author: Elizabeth Gilbert Published: 2026-05-14T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [wasm](), [Architecture & Design](), [Tooling]() Tags: [architecture](), [modularity](), [services](), [tooling](), [wasm](), [wasm-components]() ### AI overview The article explains how WebAssembly components can support pluggable HTTP middleware through component composition, service chaining, and interposition. It describes in-process communication between components whose imports and exports agree, including fan-in service topologies and chains of handlers for cross-cutting request and response processing. ### Source excerpt And how the splicer framework makes it tractable at any interface edge. ## How Compose is changing UI development DevFeed: [How Compose is changing UI development]() Original publisher: [Read original article]() Published: 2026-05-11T00:00:00Z Content type: opinion Language: en Sources: [Kt. Academy]() Topics: [Compose](), [Jetpack Compose](), [Android](), [Kotlin](), [Web Development](), [React](), [Vue.js](), [Web](), [wasm]() Tags: [adaptive](), [android](), [android-compose](), [android-development](), [compose](), [desktop](), [frontend-development](), [ios](), [javascript](), [kotlin](), [react](), [screenshot-testing](), [workshop-learning-programming]() ### AI overview This video transcript argues that Compose, a Kotlin-based declarative UI framework, is expanding beyond Android to iOS, desktop, and websites. It highlights Compose's shared tooling, adaptive layouts, previews, screenshot testing, and native animations while acknowledging weaker browser debugging support than traditional web tools. ### Source excerpt How Compose is changing the game in UI development. ## wasmCloud v2.0 is here DevFeed: [wasmCloud v2.0 is here]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-23T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [WebAssembly](), [Cloud Native Ecosystem](), [Kubernetes](), [Command-line interface](), [Containers](), [Development]() Tags: [cli](), [cloud-native](), [containers](), [go](), [kubernetes](), [native](), [operator](), [rust](), [typescript](), [vendor-lock-in](), [wasi](), [wasm](), [wasm-components](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud v2.0 is a redesigned platform for deploying WebAssembly workloads across clouds, Kubernetes clusters, datacenters, and edge locations. The release introduces a simplified runtime architecture, Kubernetes-native scheduling, Wasm Shell, a workload API, and a Kubernetes Operator. ### Source excerpt wasmCloud v2.0 is a reimagining of the wasmCloud platform: Kubernetes-native, radically simplified, and more powerful than ever. ## Hiring at Zed: Building in Real Time DevFeed: [Hiring at Zed: Building in Real Time]() Original publisher: [Read original article]() Author: Mary Luna Published: 2026-03-20T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Rust](), [Open Source](), [Code](), [real-time](), [Cloud](), [wasm](), [ui](), [Framework](), [Pull Request](), [GPU]() Tags: [building](), [cloud](), [code](), [collaboration](), [demo](), [framework](), [gpu](), [hiring](), [how-we-work](), [real-time](), [rust](), [ui](), [wasm](), [work]() ### AI overview Zed describes how it hires engineers and how new hires work during their first 90 days. The company says fewer than half of its hires submitted applications, with others discovered through open-source contributions, conferences, Hacker News, or existing relationships. New engineers land an early pull request, demonstrate their work, pair with colleagues, and contribute across Zed's vertically integrated Rust stack. ### Source excerpt How we work at Zed and how we hire. ## Five ways of looking at Jco, Part 1 DevFeed: [Five ways of looking at Jco, Part 1]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-19T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [JavaScript](), [wasm](), [WebAssembly](), [Rust]() Tags: [blog](), [javascript](), [js](), [presentation](), [technical](), [wasm](), [webassembly]() ### AI overview This first article in a series explains Jco as a layered architecture for the JavaScript and WebAssembly ecosystem. It introduces the projects involved in building JavaScript WebAssembly components, including StarlingMonkey, componentize-js, Wizer, and Jco's CLI and transpilation capabilities. ### Source excerpt Jco (@bytecodealliance/jco on NPM)is a "multi-tool for the JS WebAssembly ecosystem." At the 2026 Bytecode Alliance Plumbers Summit, Technical Steering Committee member Bailey Hayes put it another way: Jco is "like five projects in one." It's certainly a project with many facets--five big ones, arguably! Recognizing what those facets are, and how they fit together, is the key to understanding why Jco matters beyond the JavaScript ecosystem. In this blog series, we'll draw on Victor Adossi's Plumbers Summit presentation to take an in-depth look at Jco from five different perspectives, in order to better grasp how you can use (and contribute to!) Jco today. There's a lot to unpack here, so in this first post, we'll try to get to grips with Jco as a layered architecture that brings together many pieces of the Wasm and JS ecosystem. ## wasmCloud at KubeCon + CloudNativeCon EU 2026 DevFeed: [wasmCloud at KubeCon + CloudNativeCon EU 2026]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-03-12T00:00:00Z Content type: news Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm]() Tags: [2026](), [community](), [event](), [kubecon](), [maintainers](), [slack](), [wasm](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud announces its presence at KubeCon + CloudNativeCon EU 2026 in Amsterdam, including a kiosk in the Project Pavilion, WasmCon participation, and demonstrations of wasmCloud v2. ### Source excerpt Meet wasmCloud at KubeCon + CloudNativeCon EU 2026 in Amsterdam: visit the project booth, attend WasmCon, and see what is new in wasmCloud v2. ## nominal types in webassembly DevFeed: [nominal types in webassembly]() Original publisher: [Read original article]() Author: Andy Wingo Published: 2026-03-10T08:19:34Z Content type: article Language: en Sources: [wingolog]() Topics: [WebAssembly](), [wasm]() Tags: [exceptions](), [hoot](), [igalia](), [isorecursive-types](), [nominal-types](), [structural-types](), [type-equality](), [types](), [wasm](), [wastrel](), [webassembly]() ### AI overview This article explains WebAssembly's structural type equality, how recursive type groups approximate nominal typing within a module, and how the nominal typing proposal adds nominal types for stronger separation between types across modules. ### Source excerpt Before the managed data types extension to WebAssembly was incorporated in the standard, there was a huge debate about type equality. The end result is that if you have two types in a Wasm module that look the same, like this: (type $t (struct i32)) (type $u (struct i32)) Then they are for all intents and purposes equivalent. When a Wasm implementation loads up a module, it has to partition the module's types into equivalence classes. When the Wasm program references a given type by name, as in (struct.get $t 0) which would get the first field of type $t, it maps $t to the equivalence class containing $t and $u. See the spec, for more details. This is a form of structural type equality. Sometimes this is what you want. But not always! Sometimes you want nominal types, in which no type declaration is equivalent to any other. WebAssembly doesn't have that, but it has something close: recursive type groups. In fact, the type declarations above are equivalent to these: (rec (type $t (struct i32))) (rec (type $u (struct i32))) Which is to say, each type is in a group containing just itself. One thing that this allows is self-recursion, as in: (type $succ (struct (ref null $succ))) Here the struct's field is itself a reference to a $succ struct, or null (because it's ref null and not just ref). To allow for mutual recursion between types, you put them in the same rec group, instead of each having its own: (rec (type $t (struct i32)) (type $u (struct i32))) Between $t and $u we don't have mutual recursion though, so why bother? Well rec groups have another role, which is that they are the unit of structural type equivalence. In this case, types $t and $u are not in the same equivalence class, because they are part of the same rec group. Again, see the spec. Within a Wasm module, rec gives you an approximation of nominal typing. But what about between modules? Let's imagine that $t carries important capabilities, and you don't want another module to be able to forge those c ## Our Next Plumbers Summit event - February 25 & 26, 2026 DevFeed: [Our Next Plumbers Summit event - February 25 & 26, 2026]() Original publisher: [Read original article]() Author: David Bryant Published: 2026-02-11T00:00:00Z Content type: news Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [wasm](), [Maintainers](), [Go Language](), [JavaScript]() Tags: [2026](), [c-plus-plus](), [c-sharp](), [community](), [event](), [go](), [javascript](), [maintainers](), [remote](), [rust](), [summit](), [wasi](), [webassembly]() ### AI overview The Bytecode Alliance announces its next online Plumbers Summit, scheduled for February 25-26, 2026. The event will cover WebAssembly plans, hosted-project developments, Wasm tooling, and collaboration among maintainers, platform developers, and users. ### Source excerpt The Bytecode Alliance is pleased to invite you to the next installment in our ongoing Plumbers Summits event series, each designed to bring our members and community together to collectively contribute to the strategic planning for the upcoming year. Our next event will be held Wednesday and Thursday, February 25 and 26, 2026. This will be an all online event, supporting full remote participation for anyone anywhere, with sessions recorded so they can be watched anytime afterward via our YouTube channel ## 10 Years of Wasm: A Retrospective DevFeed: [10 Years of Wasm: A Retrospective]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-01-22T00:00:00Z Content type: article Language: en Sources: [Bytecode Alliance]() Topics: [wasm](), [WebAssembly](), [Web](), [browser](), [JavaScript]() Tags: [browsers](), [javascript](), [retrospective](), [wasm](), [web](), [webassembly]() ### AI overview A retrospective on WebAssembly's origins, standardization, and adoption over its first ten years. It covers the project's 2015 beginnings, the W3C's 2019 recognition of Wasm as the "fourth language of the web," and its use in web applications, streaming video, game engines, embedded devices, and cloud serverless functions. ### Source excerpt In April of 2015, Luke Wagner made the first commits to a new repository called WebAssembly/design, adding a high-level design document for a "binary format to serve as a web compilation target." ## The MonkCast: WASM and Edge Compute DevFeed: [The MonkCast: WASM and Edge Compute]() Original publisher: [Read original article]() Author: Fermyon Staff Published: 2025-11-18T12:00:00Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [wasm](), [Latency](), [Network](), [Serverless]() Tags: [ceo](), [edge-compute](), [edge-computing](), [latency](), [network](), [oss](), [serverless](), [wasm]() ### AI overview Fermyon CEO Matt Butcher joined the Monkcast for an episode discussing WebAssembly, edge computing, serverless compute, network latency, and open-source software. ### Source excerpt Our CEO Matt Butcher recently joined the Monkcast for an episode on Wasm, Edge Computing and beyond - diving deep into topics around serverless compute, network latency and OSS. ## Building an AI REPL with QuickJS DevFeed: [Building an AI REPL with QuickJS]() Original publisher: [Read original article]() Author: James Long Published: 2025-11-18T12:00:00Z Content type: opinion Language: en Sources: [James Long]() Topics: [Artificial Intelligence](), [wasm](), [WebAssembly](), [anthropic](), [Claude Code](), [User experience (UX)](), [C](), [debug](), [Error Handling]() Tags: [ai](), [anthropic](), [bytecode](), [c](), [claude-code](), [debugger](), [error-handling](), [github](), [ux](), [webassembly]() ### AI overview The article describes a three-hour experiment building an AI-integrated REPL with a custom WebAssembly build of QuickJS. The system evaluated JavaScript locally, exposed function bytecode and execution controls, and sent failed evaluations to Anthropic's Sonnet 4.5. The author concludes that the approach was not very useful for simple scripts but sees potential in sharing an executing environment with AI and debugger hooks. ### Source excerpt Yesterday I did a livestream where I built a usable REPL with AI integration. Mostly from scratch, all in 3 hours. It uses a custom WASM build of QuickJS for evaluation. If the evaluation fails, it sends the text to Anthropic to speak to Sonnet 4.5. The idea was to meld a live evaluation environment together with AI. By using QuickJS as an evaluator, we get more than just a sandbox: we are able to inspect bytecode of functions, we could pause execution as needed, etc. I thought we might discover use cases that would be difficult to do by sending JS to eval off to a remote sandbox (or a separate node instance). It's also a UX experiment: you can either write code or talk to AI. In the end, it didn't prove to be super useful. The cases where I want to provide deep introspection at runtime to AI are where I'm already working with a very complex codebase, not writing simple scripts. For the UX, I generally want to write code in a dedicated editor and send it off to be evaluated. I still think there's merit in the idea of sharing an executing environment with AI with the debugger hooks enabled; I'm researching companies working on this. Let me know if you know of any. Still, it was fun to give AI the ability to get the bytecode for a function and describe what the function does at a very low-level. I asked to write a function that sums the numbers in an array, and then asked it to get the bytecode and describe it: Some notable things that happened during this: QuickJS doesn't come with a WASM build by default. I told Claude Code to compile it to WebAssembly, and it got Emscripten all setup and successfully built it to WASM Sonnet 4.5 was able to very easily write a bunch of C code to provide new APIs in QuickJS Changing how error handling works, another example of how nice it was to get AI to work with the C code I intended to eventually dig into QuickJS and change some fundamental features but decided to pause this experiment Adding tools is really fun. Here I added a t ## WasmCon NA 2025 Liveblog DevFeed: [WasmCon NA 2025 Liveblog]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2025-11-10T00:00:00Z Content type: news Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Concurrency](), [Streaming]() Tags: [2025](), [concurrency](), [kubecon](), [kubecon-na](), [streaming](), [support](), [wasi](), [webassembly]() ### AI overview A liveblog from WasmCon at KubeCon + CloudNativeCon NA 2025 covers WebAssembly's evolution, WASI P3, the Component Model, language-integrated concurrency, streaming, and approaches to reducing unnecessary copying. ### Source excerpt Live coverage of WasmCon at KubeCon NA 2025 in Atlanta: WASI P3, the Component Model, language support, and the future of WebAssembly in production. ## Introducing the next-generation wasmCloud runtime DevFeed: [Introducing the next-generation wasmCloud runtime]() Original publisher: [Read original article]() Author: Brooks Townsend; Eric Gregory Published: 2025-11-05T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [wasm](), [Rust](), [API](), [Kubernetes]() Tags: [feature-flags](), [kubernetes](), [messaging](), [rust](), [wasi](), [wasmcloud](), [webassembly]() ### AI overview The article announces wash-runtime, a Rust crate that wraps Wasmtime to provide an ergonomic runtime and workload API for executing WebAssembly components with built-in WASI support. It describes how the design simplifies wasmCloud's architecture and supports embedding, plugins, NATS subscriptions, and future wasmCloud initiatives. ### Source excerpt The wash-runtime crate simplifies wasmCloud's architecture into an ergonomic WebAssembly host, paving the way for wasmCloud v2. ## Introducing the wash CLI's new Wasm-powered plugin system DevFeed: [Introducing the wash CLI's new Wasm-powered plugin system]() Original publisher: [Read original article]() Author: Brooks Townsend Published: 2025-08-27T00:00:00Z Content type: article Language: en Sources: [wasmCloud Blog]() Topics: [Command-line interface](), [wasm](), [WebAssembly](), [Extension](), [Security](), [Containers]() Tags: [cli](), [components](), [extensions](), [oci](), [plugin](), [security](), [wasm](), [webassembly]() ### AI overview The article introduces the next-generation wash CLI's WebAssembly component-based plugin system. It explains how the model supports portability, sandboxing, capability-based security, and development in multiple languages, while allowing custom commands and automatic plugin discovery. ### Source excerpt Why a Wasm-driven plugin model is so powerful for CLIs, and how the next-generation wash CLI uses WebAssembly components for portable, sandboxed extensions. [Next page]()