# webassembly Published articles for webassembly. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Kermit 2.2.0 adds WasmWasi support and a new Coil3 extension - Kevin Schildhorn DevFeed: [Kermit 2.2.0 adds WasmWasi support and a new Coil3 extension - Kevin Schildhorn]() Original publisher: [Read original article]() Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Library](), [WebAssembly](), [Extension]() Tags: [2-2](), [coil](), [extension](), [ios](), [kermit](), [kotlin-multiplatform](), [library](), [swift](), [update](), [version](), [webassembly]() ### AI overview Kermit 2.2.0 adds WasmWasi support for selected targets, updates supported targets, and introduces a Kermit module for receiving logs from Coil 3 image loaders. ### Source excerpt The 2.2.0 update for Kermit is out now featuring a new Coil3 extension, plus support for more targets including WasmWasi. ## Swift 6.4 Released DevFeed: [Swift 6.4 Released]() Original publisher: [Read original article]() Author: Holly Borla Published: 2026-09-15T07:30:00Z Content type: release Language: en Sources: [Swift.org]() Topics: [Swift](), [cross-platform](), [Programming](), [Memory Safety](), [WebAssembly](), [browser](), [Microcontroller]() Tags: [cross-platform](), [errors](), [libraries](), [linux](), [macos](), [memory-safety](), [programming](), [swift](), [webassembly]() ### AI overview Swift 6.4 is now available with Swift Build as the default in Swift Package Manager, a stable cross-platform Subprocess API, expanded C++20 and Java interoperability, faster WebAssembly support, broader embedded Swift capabilities, and performance improvements that maintain memory safety. ### Source excerpt Swift 6.4 is now available. Swift aims to be a great choice across the stack, from apps and servers to systems code, embedded devices, and the browser. This release deepens that support, and makes everyday code easier to write. Highlights include: Swift Build is now the default in Swift Package Manager, so your projects build the same way on Linux, macOS, and Windows. Subprocess reaches 1.0, a stable, cross-platform way to run and interact with other programs from Swift, from command-line tools to streaming processes. Interoperability reaches further, with Swift's Span now bridging directly with C++20's std::span, and Swift/Java interop extending its async and callback support. Swift runs faster in the browser, with WebAssembly bridging through JavaScriptKit up to 40 times faster, and the Wasm SDK available directly from Swift.org. Embedded Swift grows more capable, with support for existential types and richer error handling for microcontroller-class targets. Performance improves while maintaining memory safety, with new array types that hold non-copyable elements without copy-on-write overhead, and the new Iterable protocol for iterating without copies. There's so much more. Read on for a detailed guide to the new changes, or see the Swift Evolution dashboard for the full list of proposals in Swift 6.4. Simpler and clearer code Swift 6.4 streamlines your day-to-day programming to make your code simpler and clearer. More natural optional some and any types. When writing an optional some or any type, you no longer have to wrap the type in parentheses. Instead of (some Rocket)?, you can simply write some Rocket? (SE-0521). Source-level control over compiler warnings. When you need to control the behavior of warnings in your project, such as suppressing warnings or promoting them to errors, you can now define the warning behavior directly in your code using the new @diagnose attribute (SE-0522). Clarify which API to use when multiple libraries conflict. When multiple ## Caught Sleeping at Work(queue) -- Zephyr Podcast #050 DevFeed: [Caught Sleeping at Work(queue) -- Zephyr Podcast #050]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-09-11T12:46:06Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [WebAssembly](), [qemu](), [ESP32](), [ctf](), [Espressif](), [Arduino](), [RISC-V](), [cortex m4](), [Ethernet](), [Modbus](), [USB](), [Linux]() Tags: [blog](), [ctf](), [esp32](), [espressif](), [ethernet](), [linux](), [modbus](), [perfetto](), [podcast](), [qemu](), [risc-v](), [usb](), [webassembly](), [zephyr]() ### AI overview Episode 50 of the Zephyr podcast covers the Zephyr Developer Summit schedule, Analog Devices' acquisition of Alif Semiconductor, new sensor and board support, SMP coredump improvements, CTF trace conversion to Perfetto, WebAssembly Micro Runtime documentation, and other Zephyr developments. ### Source excerpt ADI buys Alif, WebAssembly in Zephyr, CTF traces reach Perfetto, and why you should never sleep in the system workqueue. ## Advancing Embedded Go: Recoverable Panics, UEFI, Radio and Hardware Dev Kit DevFeed: [Advancing Embedded Go: Recoverable Panics, UEFI, Radio and Hardware Dev Kit]() Original publisher: [Read original article]() Author: Olimpiu Pop Published: 2026-09-11T05:05:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Go Language](), [Embedded Software Dev](), [networking]() Tags: [development](), [embedded](), [embedded-software-dev](), [errors](), [go](), [hardware](), [llvm](), [networking](), [news](), [release](), [tiny-go](), [tinygo-devkit](), [wasm](), [webassembly]() ### AI overview TinyGo 0.42 adds recoverable runtime panics, Go 1.27 and LLVM 22 support, and a UEFI target. The article also covers prior wireless and board support, WebAssembly and WASI compilation, and the TinyGo Starter Kit with Seeed Studio XIAO. ### Source excerpt TinyGo version 0.42 introduces significant updates, including recoverable panics and support for Go 1.27 and LLVM 22, improving error handling and enabling Go code to run as UEFI applications. The TinyGo Starter Kit with Seeed Studio XIAO facilitates hardware use for developers, featuring an ESP32-C3 board and modular sensors. These features enhance its functionality for embedded systems and Wasm. By Olimpiu Pop ## Any Nix package, live in your browser DevFeed: [Any Nix package, live in your browser]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-10T23:44:15Z Content type: article Language: en Sources: [Simon Willison's Weblog]() Topics: [Nix](), [WebAssembly](), [qemu](), [x86](), [GitHub Actions](), [Pull Request]() Tags: [browser](), [code-review](), [code-review-16](), [github-actions](), [github-actions-72](), [linux](), [linux-54](), [qemu](), [webassembly](), [webassembly-131](), [x86]() ### AI overview The article describes trynix.dev, which runs an x86_64 Linux virtual machine in the browser using qemu-wasm and WebAssembly. It can boot Nix packages from the past 13 years, including Python 3.6.2, and supports URL-addressable interactive shells. It also highlights trynix-preview, a GitHub Action that links pull requests to browser-based builds without servers. ### Source excerpt Any Nix package, live in your browser Farid Zakaria calls this his "magnum opus of Nix work", and I can see why. trynix.dev provides a qemu-wasm powered x86_64 Linux virtual machine running entirely in your browser through WebAssembly. That VM can then be booted with any Nix package from the past 13 years. They are URL addressable, so you can navigate to this page: https://trynix.dev/?pkg=python3%403.6.2 Then click "Load" and get an interactive shell against a virtual machine running Python 3.6.2 from 2017. Farid is building all sorts of neat things on top of this. One recent example: Review a pull request by booting it introduces trynix-preview, described like this: GitHub action that comments a link on a pull request which lets you boot the PR's build in the browser using https://trynix.dev. No servers, just browsers. Via Lobste.rs Tags: code-review, linux, webassembly, github-actions ## How we rebuilt Cloudflare Workers' module registry for Node.js compatibility DevFeed: [How we rebuilt Cloudflare Workers' module registry for Node.js compatibility]() Original publisher: [Read original article]() Author: James Snell Published: 2026-09-09T13:00:00Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [Workers](), [Node.js]() Tags: [cloudflare](), [cloudflare-workers](), [developer-platform](), [developers](), [javascript](), [node-js](), [open-source](), [webassembly](), [workers]() ### AI overview Cloudflare rebuilt the Workers runtime module registry to improve Node.js compatibility, URL-based module resolution, module caching, import validation, lazy compilation, and WebAssembly support. ### Source excerpt Workers now enables Node.js compatibility by default, supports applications up to 64 mebibytes, and adds a URL-based module registry with import.meta, lazy compilation, shared code caches, and clearer errors. ## Worth Reading: An Interactive Introduction to the STP DevFeed: [Worth Reading: An Interactive Introduction to the STP]() Original publisher: [Read original article]() Published: 2026-09-08T05:55:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Protocol (disambiguation)](), [WebAssembly]() Tags: [video](), [webassembly](), [worth-reading]() ### AI overview An enthusiastic recommendation for Vincent Bernat's interactive introduction to the spanning tree protocol, which begins with an STP implementation in WebAssembly and is also available as a video. ### Source excerpt I can't even start imagining how much time Vincent Bernat spent creating his interactive introduction to the spanning tree protocol (starting with STP implemented in WebAssembly); the results are simply phenomenal (there's also a video version for people who forgot how to read). I don't think we'll ever need another STP intro after this one ;) ## What's new in Swift: August 2026 Edition DevFeed: [What's new in Swift: August 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-09-04T16:30:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [modern web development](), [Vapor](), [Back end]() Tags: [backend](), [cloudflare](), [demo](), [frontend](), [swift](), [wasm](), [webassembly]() ### AI overview A Swift community update highlights Elementary and ElementaryUI, projects for server-rendered and browser-based web UIs. It also describes Swift-to-WebAssembly progress and a Cloudflare full-stack demo using shared message types. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. Here's an update from guest contributor Simon Leeb on Swift's progress as a language for web scenarios: Hi, Simon here! I am the creator of the elementary-swift project, a collection of packages born from a simple wish: I want to build web UIs in Swift and ultimately help Swift become a first-class choice for the web. This journey began after I started using Swift for backend services. The web frontend, however, still lived in a separate ecosystem, and I really wanted it to feel as ergonomic, safe, and efficient as the Swift I was writing everywhere else. That led to the creation of Elementary: a modern and efficient HTML rendering library with a familiar declarative API, built for the web. It integrates easily with frameworks like Vapor and Hummingbird, and has become a practical option for server-rendered web UIs. Around that same time, years of community work in the swift-wasm project made compiling Swift to WebAssembly increasingly viable, while Embedded Swift was taking its first experimental steps. This made me wonder: "How hard can it be to use Embedded Swift and build a state-driven web UI framework that produces tiny WebAssembly binaries?" Turns out: quite hard, actually! But it was too late. Despite my better judgment, I was in the middle of creating what is now known as ElementaryUI. Where Elementary renders HTML on the server, ElementaryUI runs in the browser itself. You can watch my talk at Swift@FOSDEM 2026 if you want to know more about the why, what, and how. To showcase where the project is heading, I recently posted a small Full-Stack Swift on Cloudflare demo. It features Swift in the browser communicating with a Swift backend on an edge worker through shared message types. I hope it gives people a concrete sense of how much the core technologies and the surrounding tooling have advanced. ElementaryUI is still young, with plen ## .NET Conf 2026 - Save the Date DevFeed: [.NET Conf 2026 - Save the Date]() Original publisher: [Read original article]() Author: Jon Galloway Published: 2026-08-25T16:28:27Z Content type: news Language: en Sources: [.NET Blog]() Topics: [.NET Conf](), [.NET](), [C# 15](), [ASP.NET Core](), [Blazor](), [WebAssembly](), [Aspire](), [OpenAPI Specification](), [Model Context Protocol]() Tags: [asp-net-core](), [blazor](), [c-sharp-15](), [community](), [conference](), [event](), [mcp](), [net](), [net-11](), [net-conf](), [speakers](), [union-types](), [virtual-event](), [webassembly]() ### AI overview Microsoft announces .NET Conf 2026, a free online event running November 10-12, featuring community sessions and the launch of .NET 11. The article previews updates across .NET, including C# 15 union types, .NET MAUI, ASP.NET Core, Blazor, OpenAPI, Aspire, and the official MCP C# SDK. ### Source excerpt .NET Conf returns November 10-12, 2026, with three days of sessions, community, and the launch of .NET 11. The post .NET Conf 2026 - Save the Date appeared first on .NET Blog. ## Entity Raises $5 Million for Browser-Based Gaming Platform Built on WebGPU and WebAssembly DevFeed: [Entity Raises $5 Million for Browser-Based Gaming Platform Built on WebGPU and WebAssembly]() Original publisher: [Read original article]() Author: Nicole Carpenter Published: 2026-08-25T14:46:56Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [browser](), [WebAssembly](), [webgpu](), [Cloud Gaming](), [pc]() Tags: [browser](), [cloud-gaming](), [funding](), [games](), [launch](), [news](), [web](), [webassembly](), [webgpu]() ### AI overview Dublin-based startup Entity raised $5 million in seed funding to develop a browser-based gaming platform using WebGPU and WebAssembly. The company says the platform will support games played through a browser without downloads and is expected to launch in 2027. ### Source excerpt The 'next-generation gaming platform' will launch in 2027. ## Fast and Hard Code DevFeed: [Fast and Hard Code]() Original publisher: [Read original article]() Author: Armin Ronacher Published: 2026-08-22T00:00:00Z Content type: opinion Language: en Sources: [Armin Ronacher]() Topics: [Rust](), [LLMs](), [Zig](), [Artificial Intelligence](), [Programming](), [WebAssembly](), [Cloudflare](), [Vercel](), [eBPF]() Tags: [ai](), [cloudflare](), [ebpf](), [llms](), [performant](), [programming](), [rust](), [thoughts](), [vercel](), [webassembly](), [zig]() ### AI overview An opinion article argues that LLM-assisted programming makes language choice less consequential, allowing developers to use unfamiliar or traditionally difficult languages. It focuses on growing interest in fast, small software built with Rust and Zig, while noting examples involving WebAssembly, Cloudflare, Vercel, and other demanding technologies. ### Source excerpt One of the memes on Twitter is that "programming is solved now." I'm not sure to what degree it is, but one thing is pretty clear: the act of familiarizing yourself with a language no longer matters and some of the friction that mattered for humans does not matter for agents. As a result, LLMs make language choice much less consequential than it used to be. If you don't like the choice, you can seemingly rewrite it in another language and you can make it pick a language that you, as a programmer, are entirely unfamiliar with. Which in turn means that people can, and do, choose based on the marketing of languages much more. As a long-term Rust programmer I found it quite fascinating to see people now ship Rust code who previously might not have chosen it. I attribute at least one part of this to two recent vibe shifts: there is a lot more talk about wanting fast software, and about LLMs being exceptional at optimizing code without regressing behavior. Folks like Mitchell Hashimoto, Charlie Marsh, Jarred Sumner, Daniel Lemire and quite a few others always carried a certain level of obsession with fast and performant software and they also all happen to be receptive to agents writing code. Maybe as a result, or unrelated others are now joining in. That's because with things like autoresearch you don't even necessarily need to know all the tricks: you just need to put an agent on it -- though knowledge greatly helps! If you look around, there are plenty of projects that want to be fast and small, and they increasingly pick "hard languages". And it's not just Rust that is benefiting. Even Zig -- despite the fact that the creators and parts of the core community are pretty negative on the whole AI thing -- is too. For instance Cloudflare's new Artifacts service uses a pure-Zig Git-protocol engine, compiled to a roughly 100 KB WebAssembly module and Vercel released fx, a Zig coding agent advertised to be small and fast. From what I can tell, all these projects are largely LLM ## An insider argues that Google remains committed to Flutter and Dart DevFeed: [An insider argues that Google remains committed to Flutter and Dart]() Original publisher: [Read original article]() Author: Randal L. Schwartz Published: 2026-08-19T16:02:19Z Content type: opinion Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Dart](), [Google](), [multiplatform](), [WebAssembly]() Tags: [cross-platform](), [dart](), [devrel](), [flutter](), [google](), [mobile-app-development](), [programming](), [software-development](), [wasm](), [webassembly]() ### AI overview This commentary argues, from the author's stated experience as a Flutter Google Developer Expert, that Google remains committed to Flutter and Dart despite restructuring-related concerns and reduced public communication. It cites renewed advocacy and investment in rendering, Dart ergonomics, WebAssembly compilation, and multiplatform performance. ### Source excerpt Every few months, like clockwork, the tech blogosphere gets flooded with the same recycled headline: "Is Flutter Dying?", "Why CTOs Are Quietly Leaving Flutter", or "Why Google is Killing Its Cross-Platform Bet." As someone who has been a Flutter Google Developer Expert for eight years now -- literally from day one of the GDE program -- and a five-decade software industry veteran, I usually just chuckle at the clickbait. "Flutter is dead." -- Said every six months since 2018. Meanwhile: Flutter is kicking tail on every single measurable scale. The alarmist articles point to standard corporate reorganizations, shifting tech job boards, and "state management fatigue" as evidence of Flutter's demise. But having watched this ecosystem evolve from an experimental alpha into an enterprise powerhouse, the reality on the ground is the exact opposite. Here is the real insider story on what's actually happening with Dart and Flutter. 1. The Inside Story: What Happened at Google? When tech companies restructured engineering teams recently, the internet spun a wild narrative that "Google put Flutter on life support." Having direct access to internal teams, I watched the commitment to Dart and Flutter remain steadfast within the organization. However, there was a temporary disconnect: internal engineering activity was roaring, but external communications and public advocacy had slowed down, leaving an information vacuum that clickbait writers eagerly filled. I personally called out to team leaders and senior VPs that this perception gap needed immediate correction. And the leadership responded strongly: Revitalized DevRel & Advocacy: A renewed surge in active community engagement, tutorials, and public roadmaps. Enterprise Adoption Transparency: Showcasing massive internal and external production milestones. Aggressive Core Investment: Deep work on the Impeller rendering engine, Dart 3.x ergonomics, WebAssembly (Wasm) compilation, and native multiplatform performance. Flutter is no ## Introducing YeSQL: Practical PostgreSQL, One Concept at a Time DevFeed: [Introducing YeSQL: Practical PostgreSQL, One Concept at a Time]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2026-08-18T08:00:00Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [SQL](), [WebAssembly]() Tags: [how-to](), [interactive](), [postgresql](), [sql](), [webassembly]() ### AI overview The article introduces YeSQL, a free collection of 24 short PostgreSQL lessons. Each lesson combines one concept with a runnable query and realistic data. Queries run locally in the browser through PGlite, PostgreSQL compiled to WebAssembly, without signup or a server round-trip. ### Source excerpt I'm happy to share something new: YeSQL is live, a free set of 24 short PostgreSQL lessons -- one concept, one runnable query, real data, no signup. It's free to use today, and it's also a prototype for something I've wanted to build for a while: making every query in The Art of PostgreSQL runnable, right on the page. ## Compiling to intermediate representation: Write yourself a compiler, Part III DevFeed: [Compiling to intermediate representation: Write yourself a compiler, Part III]() Original publisher: [Read original article]() Published: 2026-08-16T22:00:00Z Content type: tutorial Language: en Sources: [Tomasz Nurkiewicz around Java and concurrency]() Topics: [Compiler](), [virtual machines](), [Code](), [WebAssembly](), [Java]() Tags: [assembly](), [bytecode](), [compilation](), [compiler](), [go](), [interpreter](), [ir](), [javascript](), [python](), [virtual-machines](), [webassembly](), [writing-compiler]() ### AI overview This tutorial explains how a small interpreter project evolves into a compiler by emitting intermediate representation (IR). It contrasts interpreted and compiled languages, describes bytecode and virtual machines, and uses Java and WebAssembly examples to show how IR instructions are executed. ### Source excerpt It's time to dive a bit deeper and abandon the naive realm of interpreters. Our tiny little project can finally call itself a compiler. In this part we'll emit so-called intermediate representation instead of just evaluating and running the source code as-is. OK, what does this all mean? ## wasmCloud 2.7: Bidirectional host component plugins, concurrent pooling, and multi-backend binding by default DevFeed: [wasmCloud 2.7: Bidirectional host component plugins, concurrent pooling, and multi-backend binding by default]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-08-12T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [configuration](), [networking]() Tags: [component](), [concurrent](), [configuration](), [networking](), [release](), [secrets](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud 2.7 introduces bidirectional host component plugins, concurrent pooled instances, and multi-backend binding by default. It also adds workload-level HTTP connection pooling, raw-socket quotas, opt-in egress policies, configurable CA trust, and updated Helm chart CRDs. ### Source excerpt wasmCloud 2.7 makes host component plugins bidirectional (plugins can call workload exports), multiplies warm-instance capacity with maxConcurrency, enables multi-backend binding by default, and hardens workload networking with quotas and private CA trust. ## Introducing sqlfmt: an SQL gofmt-style formatter DevFeed: [Introducing sqlfmt: an SQL gofmt-style formatter]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2026-08-11T12:30:37Z Content type: release Language: en Sources: [Dimitri Fontaine]() Topics: [SQL](), [formatting](), [Tooling](), [Go Language](), [WebAssembly](), [PostgreSQL]() Tags: [formatting](), [go](), [postgresql](), [sql](), [tooling](), [webassembly]() ### AI overview The article introduces sqlfmt, a gofmt-style SQL formatter based on the author's SQL indentation conventions from The Art of PostgreSQL. It uses a single opinionated style with no configuration options, including river alignment and specific rules for keywords, commas, continuation lines, data types, and comments. The formatter is available through a CLI and a WebAssembly-based web tool. ### Source excerpt Formatting SQL tends to bring some of the same questions again and again: should we uppercase clause keywords? should we put the separating comma at the start of a line to ease refactoring? how to align the SQL clauses with one-another? Over the years I have grown my own SQL style and didn't find tooling that would implement it. Also, I've been asked here and there if there is a tool that would replicate The Art of PostgreSQL SQL indentation style... and now there is finally a good answer to that question! sqlfmt is a gofmt-style formatter that implements my own favorite SQL indentation style. One opinionated style, no configuration knobs. Run it, commit the result, move on. ## wasmCloud 2.6: Trigger services, host component plugins, and warm instance pooling DevFeed: [wasmCloud 2.6: Trigger services, host component plugins, and warm instance pooling]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-08-03T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [WebAssembly](), [Messaging](), [Latency]() Tags: [components](), [dns](), [latency](), [plugins](), [services](), [stateful](), [streaming](), [wasmcloud](), [webassembly]() ### AI overview wasmCloud 2.6.0 and patch 2.6.1 introduce trigger services, host component plugins, warm-instance pooling, default NATS consumer groups for replicas, per-component DNS allowlists, Wasmtime 47 updates, and direct WASI 0.3 component builds. ### Source excerpt wasmCloud 2.6 ships trigger services, host component plugins (WebAssembly components that extend the host), warm-instance pooling, consumer groups by default for NATS messaging, and per-component DNS allowlists. ## An Update on WAMR and the Bytecode Alliance DevFeed: [An Update on WAMR and the Bytecode Alliance]() Original publisher: [Read original article]() Author: The Bytecode Alliance Published: 2026-07-21T00:00:00Z Content type: news Language: en Sources: [Bytecode Alliance]() Topics: [WebAssembly](), [Development]() Tags: [community](), [development](), [news](), [project](), [update](), [webassembly]() ### AI overview The WebAssembly Micro Runtime (WAMR) will continue development independently of the Bytecode Alliance after the organizations concluded that the project has distinct goals and direction. ### Source excerpt We're writing to share some news about the future of the Bytecode Alliance and the WebAssembly Micro Runtime (WAMR). ## 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. ## 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. ## Swift Package Index Update DevFeed: [Swift Package Index Update]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-06-23T14:00:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [Swift](), [Linux](), [Android](), [WebAssembly]() Tags: [android](), [announcement](), [ecosystem](), [linux](), [swift](), [update](), [webassembly]() ### AI overview Swift Package Index has joined Apple while continuing to support package discovery, documentation, dependency evaluation, and compatibility testing across Swift's expanding multi-platform ecosystem, including Linux, Android, and WebAssembly. ### Source excerpt Since its launch, Swift Package Index has become an essential part of the Swift ecosystem, helping developers discover quality packages, evaluate compatibility, and make informed decisions about dependencies. Started by Dave Verwer and Sven A. Schmidt, the project currently indexes thousands of packages and serves as a central hub for package documentation. Recently, Swift Package Index has grown alongside the Swift project's multi-platform expansion, extending its compatibility testing to encompass Linux, Android, and WebAssembly. Today, Swift Package Index announced that it has joined Apple and continues its mission: Together, we're building a comprehensive package registry to serve the Swift community's evolving needs. Learn more by reading the Swift Package Index announcement. ## Experimenting with the proposed Cross-Origin Storage API in Transformers.js DevFeed: [Experimenting with the proposed Cross-Origin Storage API in Transformers.js]() Original publisher: [Read original article]() Author: Thomas Steiner Published: 2026-06-23T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [AI, ML & Data Engineering]() Tags: [ai-models](), [announcement](), [api](), [artificial-intelligence](), [asr](), [browser](), [cache](), [chrome](), [chrome-extension](), [cos](), [cross-origin-storage](), [inference](), [javascript](), [on-device](), [open-source](), [storage](), [transformers](), [transformers-js](), [wasm](), [web](), [web-apps](), [web-developers](), [web-standards](), [webassembly]() ### AI overview A tutorial that uses Transformers.js browser inference examples to examine duplicate model and WebAssembly downloads across origins and the proposed Cross-Origin Storage API. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## 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. ## WWDC 2026 Viewing Guide DevFeed: [WWDC 2026 Viewing Guide]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2026-06-15T09:16:45Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [Swift](), [SwiftUI](), [Xcode](), [WebAssembly](), [gRPC](), [MLX](), [NumPy](), [Testing]() Tags: [2026](), [apple](), [auto-layout](), [comparison](), [ios](), [ios27](), [macos27](), [objective-c](), [swift](), [swiftui](), [webassembly](), [wwdc](), [xcode]() ### AI overview A guide to planning and watching WWDC 2026 sessions, highlighting platform themes and selected updates in Swift, SwiftUI, Xcode, WebAssembly, gRPC, and MLX. ### Source excerpt My WWDC 2026 viewing guide to help you plan the sessions you want to watch. Where Do I Start? The two big themes for the year are again Liquid Glass and Apple Intelligence. Start by watching the Platforms State of the Union (SOTU) for a summary of what's new this year. If you only have five minutes try the SOTU recap. You don't have to learn everything new today! There are over 100 sessions and a lot of new stuff to learn. You may feel like you're getting left behind. Don't let it overwhelm you. You've got time. Don't burn yourself out trying to keep up. Watching The Sessions I watch the videos using the Apple Developer app. It's available on macOS and iOS. The video player supports from 0.5x to 2x playback, most videos have transcripts and summaries, and allow copying of the onscreen sample code. You can also watch on YouTube. There are a lot of sessions, but many are short (15-20 minutes). There's no padding and Apple's engineers get to the point quickly. Swift Swift 6.4 is here with some quality of life improvements: What's new in Swift Condense long @available attributes with anyAppleOS, @diagnose to control compiler deprecation warnings. Double-colon module selector. Standard Library task cancellation shield, dictionary mapKeyedValues, new FilePath type. XCTest interop with Swift Testing. Subprocess 1.0. New ProgressManager. @C attribute for Swift-C interop. Compile to WebAssembly. New @inline(always) and @specialized attributes. Iterable protocol for noncopyable elements. Build real-time apps and services with gRPC and Swift gRPC Swift package to generate and deploy network code for remote procedure call services. Explore numerical computing in Swift with MLX NumPy-like API. Examples of computing the Mandlebrot set, heat distribution, and curve fitting. SwiftUI Liquid Glass changes and some welcome improvements: What's new in SwiftUI Liquid Glass is now mandatory. Minimal menu icons by default. Resize live previews in Xcode. Prominent tab role. Toolbar visibil [Next page]()