# WebAssembly

WebAssembly 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.

## NetWasm 0.10 Speeds Up C# on WebAssembly, Now Faster Than Mono AOT

DevFeed: [NetWasm 0.10 Speeds Up C# on WebAssembly, Now Faster Than Mono AOT](<https://devfeed.tech/articles/netwasm-0-10-speeds-up-c-on-webassembly-now-faster-than-mono-aot-142922.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/NetWasm-0-10-Faster/>)

Author: Edin Kapić

Published: 2026-11-19T09:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [inlining](<https://devfeed.tech/topics/inlining.md>), [vectorization techniques](<https://devfeed.tech/topics/vectorization-techniques.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [toolchain](<https://devfeed.tech/topics/toolchain.md>)

Tags: [aot](<https://devfeed.tech/tags/aot.md>), [arithmetic](<https://devfeed.tech/tags/arithmetic.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [development](<https://devfeed.tech/tags/development.md>), [dotnet](<https://devfeed.tech/tags/dotnet.md>), [exception-handling](<https://devfeed.tech/tags/exception-handling.md>), [faster](<https://devfeed.tech/tags/faster.md>), [mono](<https://devfeed.tech/tags/mono.md>), [net](<https://devfeed.tech/tags/net.md>), [net-11](<https://devfeed.tech/tags/net-11.md>), [netwasm-0-10-faster](<https://devfeed.tech/tags/netwasm-0-10-faster.md>), [news](<https://devfeed.tech/tags/news.md>), [simd](<https://devfeed.tech/tags/simd.md>), [wasi](<https://devfeed.tech/tags/wasi.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

NetWasm 0.10's compiler optimizations made it faster than Mono AOT on the project's benchmark set: across 2,213 cases, version 0.10.8 at O3 with NetWasmGC took 0.41 times Mono AOT's time as a geometric mean, excluding five cases where Mono's LLVM removed the work. Changes across releases 0.10.1-0.10.8 included shared exception handling, inlining and redundant bounds-check removal, 128-bit WebAssembly SIMD with scalar fallback, and reuse of division results for remainder and range checks. The excerpt reports gains on quicksort, DoomSharp, and a vectorized fluid-equation solver, while desktop .NET 11 RC3 remained faster overall at 0.87 times NetWasm's time. Results used Wasmtime 49.0.3 on one Apple M1 Max; the authors note measurement sensitivity to function alignment, slower vector performance than desktop .NET, specific slow operations, and a NewtR regression.

### Source excerpt

Summary: NetWasm, an ahead-of-time compiler from C# to WebAssembly, has reworked exception handling, bounds-check elimination, SIMD and division in its 0.10 series. Across more than 2000 benchmark cases, the project reports running in 0.41 times the time of Mono AOT's WASI build. By Edin Kapić

## AWS Serverless Infrastructure from WebAssembly Components

DevFeed: [AWS Serverless Infrastructure from WebAssembly Components](<https://devfeed.tech/articles/aws-serverless-infrastructure-from-webassembly-components-126722.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.11293>)

Author: Philipp Vollmer

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Serverless](<https://devfeed.tech/topics/serverless.md>), [Wasm components](<https://devfeed.tech/topics/wasm-components.md>), [AWS Lambda](<https://devfeed.tech/topics/aws-lambda.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [component](<https://devfeed.tech/tags/component.md>), [components](<https://devfeed.tech/tags/components.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [least-privilege](<https://devfeed.tech/tags/least-privilege.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [s3](<https://devfeed.tech/tags/s3.md>), [sandboxing](<https://devfeed.tech/tags/sandboxing.md>), [security](<https://devfeed.tech/tags/security.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

The approach uses a WebAssembly component's WIT interface to keep AWS Lambda infrastructure and permissions aligned. One WIT interpreter generates S3 bucket infrastructure definitions and least-privilege IAM permissions; a generic runtime runs the component as a Lambda function and exposes buckets as capabilities. The authors state consistency properties for bucket existence and Lambda permissions and provide evidence that their interpreters satisfy them. In the limited Lambda-to-S3 example, they show selected deployment failures prevented by the approach that occur in a baseline setup. Combined with WebAssembly runtime sandboxing, this provides capability-based security for AWS infrastructure access.

### Source excerpt

arXiv:2611.11293v1 Announce Type: cross Abstract: The infrastructure definitions and the code for serverless applications are often only loosely connected. This yields a large error class: the referenced infrastructure components might not exist. It is also hard to keep the application and its permissions in sync. To address this problem we present an infrastructure from code solution where we provision cloud infrastructure from Wasm Interface Type (WIT) - the language defining the interface of WebAssembly components. We limit ourselves to the basic example of an AWS Lambda function accessing S3 buckets. We build two interpreters for the WIT language: one that derives the definition of S3 buckets as infrastructure as code and least-privilege IAM permissions, and a generic runtime that runs the component as a Lambda function and provides access to the S3 buckets as capabilities. We formulate consistency properties that ensure the existence of the S3 buckets and correct permissions of the Lambda, and provide evidence that our interpreters satisfy them. We show how selected failures for deployment of such cloud components can be prevented using our technique and how a baseline setup fails at this task. Together with the strict sandboxing of the WebAssembly runtime we achieve an instance of capability-based security for access to AWS infrastructure as a further result.

## WasmLens: Automatic Glass-Box Instrumentation for Composed WebAssembly Applications

DevFeed: [WasmLens: Automatic Glass-Box Instrumentation for Composed WebAssembly Applications](<https://devfeed.tech/articles/wasmlens-automatic-glass-box-instrumentation-for-composed-webassembly-applications-127272.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.12710>)

Author: Michiel Van Kenhove, Ewout Verlinde, Jos\\'e Santos, Filip De Turck, Bruno Volckaert, Merlijn Sebrechts

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Wasm components](<https://devfeed.tech/topics/wasm-components.md>), [tracing](<https://devfeed.tech/topics/tracing.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [middleware](<https://devfeed.tech/topics/middleware.md>)

Tags: [binaries](<https://devfeed.tech/tags/binaries.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [composition](<https://devfeed.tech/tags/composition.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [graph](<https://devfeed.tech/tags/graph.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [latency](<https://devfeed.tech/tags/latency.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [observability](<https://devfeed.tech/tags/observability.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [traces](<https://devfeed.tech/tags/traces.md>), [tracing](<https://devfeed.tech/tags/tracing.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

WasmLens reconstructs end-to-end traces across black-box WebAssembly components by injecting middleware into composed binaries, using instrumentation points derived from the composition graph. Its per-component span-stack tracing design restores parent-child relationships across component boundaries without changing component interfaces or source code; the abstract says this design was adopted upstream. In the reported measurements, mean request latency rose from 238 μs to 454 μs across six boundaries. Increasing the expected crossings from six to eleven raised latency to 514 μs, adding 12 μs per crossing, of which 10.4 μs was attributed to instrumentation. The authors characterize this overhead as additive with composition depth.

### Source excerpt

arXiv:2611.12710v1 Announce Type: new Abstract: The WebAssembly Component Model enables language-independent composition of independently developed components, but complicates observability. Existing tracing support flattens execution hierarchy by attributing every span created inside a composition to a single host-level parent context, so execution across component boundaries cannot be reconstructed. The problem is amplified because components are typically deployed as black boxes whose internals cannot be modified or inspected by the system integrator. To address these limitations, we propose a revised wasi:otel/tracing design in which the runtime maintains a per-component span stack, restoring parent-child relationships across component boundaries without changing component interfaces or source code. This change has since been adopted upstream. Building on this design, we present WasmLens, an automatic instrumentation tool that derives instrumentation points from a composition graph and injects tracing middleware into already composed binaries, yielding end-to-end traces for black-box compositions with no developer configuration. This automatic instrumentation raises mean request latency from $238$ $\mu$s to $454$ $\mu$s across six component boundaries. Raising the expected number of boundary crossings from 6 to 11 further increases latency to $514$ $\mu$s, an incremental cost of $12$ $\mu$s per crossing, of which $10.4$ $\mu$s is attributable to instrumentation. These results show that instrumentation overhead is additive in composition depth rather than proportional to baseline execution time.

## Reducing Cold-Start Latency on the WebAssembly Edge via Locality and Network-Aware Scheduling

DevFeed: [Reducing Cold-Start Latency on the WebAssembly Edge via Locality and Network-Aware Scheduling](<https://devfeed.tech/articles/reducing-cold-start-latency-on-the-webassembly-edge-via-locality-and-network-aware-scheduling-126805.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.12620>)

Author: Michiel Van Kenhove, Emiel Sucaet, Jos\\'e Santos, Filip De Turck, Bruno Volckaert, Merlijn Sebrechts

Published: 2026-11-10T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [wasmCloud](<https://devfeed.tech/topics/wasmcloud.md>), [round robin](<https://devfeed.tech/topics/round-robin.md>)

Tags: [artifacts](<https://devfeed.tech/tags/artifacts.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cold-start](<https://devfeed.tech/tags/cold-start.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [e2e](<https://devfeed.tech/tags/e2e.md>), [edge](<https://devfeed.tech/tags/edge.md>), [edge-computing](<https://devfeed.tech/tags/edge-computing.md>), [hybrid](<https://devfeed.tech/tags/hybrid.md>), [latency](<https://devfeed.tech/tags/latency.md>), [locality](<https://devfeed.tech/tags/locality.md>), [network](<https://devfeed.tech/tags/network.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [round-robin](<https://devfeed.tech/tags/round-robin.md>), [routing](<https://devfeed.tech/tags/routing.md>), [scheduler](<https://devfeed.tech/tags/scheduler.md>), [scheduling](<https://devfeed.tech/tags/scheduling.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [worker](<https://devfeed.tech/tags/worker.md>)

### AI overview

A hybrid scheduler for a WebAssembly edge orchestrator combines worker cache state with network proximity to reduce cold-start and routing delays. On a Raspberry Pi testbed with emulated regional latency, it reduced mean end-to-end latency by up to 40.8% versus round-robin. Locality-aware placement was most effective for large or frequently requested artifacts; network-aware placement mattered more for small artifacts when routing latency had a larger relative impact. Combining both signals produced the lowest latency across the evaluated workloads.

### Source excerpt

arXiv:2611.12620v1 Announce Type: new Abstract: Edge computing places computation closer to users and data sources, but introduces heterogeneous hardware, limited resources, and variable network conditions. WebAssembly (Wasm) is increasingly considered for these environments because modules are compact, portable, and quick to start. However, cold-start latency remains a challenge: when a worker node does not yet hold the required artifact, it must fetch it before execution, adding transfer overhead that directly increases the end-to-end (E2E) latency, especially for large artifacts or slow network links. At the same time, the geographical distance between the requester and the assigned worker independently contributes to latency through network routing overhead. Together, artifact locality and network proximity do not always point to the same placement decision, and naive scheduling strategies fail to account for either. This work extends a Wasm-native edge orchestrator with state-aware scheduling strategies that jointly optimize for both objectives. Evaluation on a Raspberry Pi testbed with emulated regional network latency shows that a hybrid scheduler combining cache-state and network-proximity signals reduces mean E2E latency by up to 40.8% compared to a default round-robin baseline. Artifact locality-aware placement is most effective when artifacts are large or repeatedly requested, while network-aware placement dominates when artifacts are small and routing latency has a larger relative effect, but combining both objectives consistently yields the lowest E2E latency across diverse edge workloads.

## PhotoFinish: Portable Timerless Probing of Microarchitectural Latencies

DevFeed: [PhotoFinish: Portable Timerless Probing of Microarchitectural Latencies](<https://devfeed.tech/articles/photofinish-portable-timerless-probing-of-microarchitectural-latencies-122816.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.09879>)

Author: Tristan Hornetz, Eduard Ebert, Lorenz Hetterich, Lukas Gerlach, Michael Schwarz

Published: 2026-11-09T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [race-condition](<https://devfeed.tech/topics/race-condition.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [aes](<https://devfeed.tech/tags/aes.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [browser](<https://devfeed.tech/tags/browser.md>), [cache](<https://devfeed.tech/tags/cache.md>), [cpus](<https://devfeed.tech/tags/cpus.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [engine](<https://devfeed.tech/tags/engine.md>), [latency](<https://devfeed.tech/tags/latency.md>), [parallel](<https://devfeed.tech/tags/parallel.md>), [portable](<https://devfeed.tech/tags/portable.md>), [precision](<https://devfeed.tech/tags/precision.md>), [timer](<https://devfeed.tech/tags/timer.md>), [timing](<https://devfeed.tech/tags/timing.md>), [tlb](<https://devfeed.tech/tags/tlb.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

PhotoFinish infers microarchitectural latency without reading or constructing a clock: two parallel threads race a tested operation against a fixed reference, then write distinct values to shared memory, leaving a latency-dependent architectural value. The authors report reliable cache-state classification across 38 CPUs and four ISAs, with comparable fidelity in WebAssembly running in a browser. They also apply it to AES T-table and Evict+Reload attacks, TLB and execution-engine latencies, and LLC-slice identification. The approach requires parallel execution and shared memory; the abstract presents it as a general timerless probe and reports that timer restrictions alone do not prevent fine-grained latency observations.

### Source excerpt

arXiv:2611.09879v1 Announce Type: new Abstract: Timing measurements are a fundamental building block of microarchitectural attacks, enabling software to convert otherwise invisible latency differences into architectural observations. Thus, restricting high-resolution timers is a common defense, especially in constrained environments such as web browsers. Timerless probing primitives provide an alternative approach. Instead of reading or constructing a timer, they observe architectural events that correlate with the microarchitectural state. However, such primitives typically rely on platform-specific behavior, and none generalizes across the wider computing landscape. In this paper, we present PhotoFinish, a portable timerless probing primitive that converts latency differences directly into an architectural value. PhotoFinish races an operation under test against a fixed reference in two parallel threads that then write unique values to the same shared location, resulting in a latency-dependent architectural value. PhotoFinish only requires parallel execution and shared memory, without constructing or reading a clock. We evaluate PhotoFinish on 38 CPUs spanning four ISAs and demonstrate reliable cache state classification across widely different microarchitectures, with comparable fidelity when compiled to WebAssembly and executed inside a browser. We further use PhotoFinish in AES T-table and Evict+Reload attacks, show that it applies beyond caches to TLB and execution-engine latencies, and demonstrate sufficient precision to identify the LLC slice of an address. Our results demonstrate shared-memory races as a generic and precise replacement for explicit timing, showing that restricting timers alone does not prevent software from observing fine-grained microarchitectural latency differences.

## CVE-2026-54914 - WebAssembly Micro Runtime: Heap Buffer Overflow in WAMR WASI poll\_oneoff Output Buffer

DevFeed: [CVE-2026-54914 - WebAssembly Micro Runtime: Heap Buffer Overflow in WAMR WASI poll\_oneoff Output Buffer](<https://devfeed.tech/articles/cve-2026-54914-webassembly-micro-runtime-heap-buffer-overflow-in-wamr-wasi-poll-oneoff-output-buffer-119393.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-54914>)

Author: CVEFEED.io; github.com

Published: 2026-11-05T18:17:08Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [heap overflow](<https://devfeed.tech/topics/heap-overflow.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [buffer](<https://devfeed.tech/tags/buffer.md>), [buffer-overflow](<https://devfeed.tech/tags/buffer-overflow.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-54914](<https://devfeed.tech/tags/cve-2026-54914.md>), [heap](<https://devfeed.tech/tags/heap.md>), [heap-buffer-overflow](<https://devfeed.tech/tags/heap-buffer-overflow.md>), [poll](<https://devfeed.tech/tags/poll.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [wasi](<https://devfeed.tech/tags/wasi.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Before WAMR 2.4.5, wasi_poll_oneoff validates space for only one wasi_event_t, but the underlying poll routine can write events according to the guest-controlled nsubscriptions count. A crafted guest module can therefore cause an event write to cross the validated Wasm linear-memory boundary into adjacent host heap memory. The partly attacker-controlled overwrite can reliably crash the host; further confidentiality or integrity effects depend on heap layout. The issue is fixed in WAMR 2.4.5.

### Source excerpt

CVE ID :CVE-2026-54914 Published : Nov. 5, 2026, 6:17 p.m. | 46 minutes ago Description :WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. Prior to 2.4.5, wasi_poll_oneoff in core/iwasm/libraries/libc-wasi/libc_wasi_wrapper.c validates the output pointer for only one wasi_event_t, while wasmtime_ssp_poll_oneoff in core/iwasm/libraries/libc-wasi/sandboxed-system-primitives/src/posix.c can write as many events as the guest-controlled nsubscriptions value. A crafted guest module can provide multiple subscriptions that produce events while positioning an output region large enough for only one event, causing a later out[nevents] write to cross the validated Wasm linear-memory boundary into adjacent host heap memory. The overwrite contains partly attacker-controlled event data and can reliably crash the host process, with further confidentiality or integrity consequences depending on heap layout. This issue is fixed in version 2.4.5. Severity: 8.3 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Walma: Learning to See Memory Corruption in WebAssembly

DevFeed: [Walma: Learning to See Memory Corruption in WebAssembly](<https://devfeed.tech/articles/walma-learning-to-see-memory-corruption-in-webassembly-113984.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2603.24167>)

Author: Oussama Draissi, Mark G\\"unzel, Ahmad-Reza Sadeghi, Lucas Davi

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Neural Network](<https://devfeed.tech/topics/neural-network.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>)

Tags: [adversarial](<https://devfeed.tech/tags/adversarial.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [applications](<https://devfeed.tech/tags/applications.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [binaries](<https://devfeed.tech/tags/binaries.md>), [boundary](<https://devfeed.tech/tags/boundary.md>), [bug](<https://devfeed.tech/tags/bug.md>), [costs](<https://devfeed.tech/tags/costs.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cve](<https://devfeed.tech/tags/cve.md>), [data](<https://devfeed.tech/tags/data.md>), [entropy](<https://devfeed.tech/tags/entropy.md>), [evasion](<https://devfeed.tech/tags/evasion.md>), [framework](<https://devfeed.tech/tags/framework.md>), [learning](<https://devfeed.tech/tags/learning.md>), [memory](<https://devfeed.tech/tags/memory.md>), [memory-corruption](<https://devfeed.tech/tags/memory-corruption.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

WALMA detects WebAssembly linear-memory corruption by turning memory snapshots into grayscale images and classifying their compiled-code row structure with a convolutional neural network. Its VGG-16 detector achieved 95%-100% verdict accuracy on four of five CVE-affected applications with no false alarms; a smaller 1.9-million-parameter ResNet came within a few points on those four and can run inside the runtime on every host call. Boundary attestation on 53 WABench binaries added 1.07x-1.69x cost, which the authors report scales with host exposure. The method can check integrity against compromised modules and against untrusted hosts only if snapshots reach the verifier intact. The abstract also reports that black-box evasion requires contiguous overwrites of hundreds of kilobytes to megabytes.

### Source excerpt

arXiv:2603.24167v3 Announce Type: replace Abstract: The monolithic linear memory of WebAssembly (Wasm) creates a bidirectional attack surface: a memory corruption bug in a module can compromise the host, and a compromised host can corrupt the state of a trusted module. Existing defenses either require custom runtimes or source code changes, and none can verify runtime integrity under an adversarial host. We present WALMA, the first attestation framework delivering resilience by reaction against data-centric attacks that corrupt a region of memory. We render linear memory snapshots as grayscale images and classify them with a convolutional neural network. The network reads the row-aligned structure that compiled code imposes on memory and detects corruption that byte and texture statistics miss. Our main VGG-16 detector reaches 95%--100% verdict accuracy on four of five CVE-affected applications without a single false alarm, and a 1.9M-parameter ResNet, small enough to run inside the runtime on every host call, stays within a few points of it on the same four. A Shannon-entropy analysis bounds which out-of-band edits the network can separate from valid state, and black-box evasion requires contiguous overwrites of hundreds of kilobytes to megabytes. On the 53 WABench binaries, boundary attestation costs 1.07x--1.69x, scaling with a module's exposure to the host rather than with its runtime. WALMA thus makes linear memory integrity a property a Wasm runtime can check continuously: end to end against compromised modules, and against untrusted hosts provided snapshots reach the verifier intact.

## Accelerating QUIC Encryption in WebAssembly Using WASM-SIMD

DevFeed: [Accelerating QUIC Encryption in WebAssembly Using WASM-SIMD](<https://devfeed.tech/articles/accelerating-quic-encryption-in-webassembly-using-wasm-simd-113868.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.01989>)

Author: Sota Yamawaki, Yasuo Okabe

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [QUIC](<https://devfeed.tech/topics/quic.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [vectorization techniques](<https://devfeed.tech/topics/vectorization-techniques.md>)

Tags: [acceleration](<https://devfeed.tech/tags/acceleration.md>), [aes](<https://devfeed.tech/tags/aes.md>), [amdahl-s-law](<https://devfeed.tech/tags/amdahl-s-law.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [edge](<https://devfeed.tech/tags/edge.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [gigabit-ethernet](<https://devfeed.tech/tags/gigabit-ethernet.md>), [limits](<https://devfeed.tech/tags/limits.md>), [memory](<https://devfeed.tech/tags/memory.md>), [native](<https://devfeed.tech/tags/native.md>), [network](<https://devfeed.tech/tags/network.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [overhead](<https://devfeed.tech/tags/overhead.md>), [quic](<https://devfeed.tech/tags/quic.md>), [simd](<https://devfeed.tech/tags/simd.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Explicit WASM-SIMD kernels substantially improve QUIC encryption performance in WebAssembly, but shift the main limits to other parts of the stack. On two hosts connected by 10-Gigabit Ethernet, kernels processing eight AES blocks or four ChaCha20 blocks per pass increased receiver goodput over a non-SIMD baseline by 61.34% for AES-128-GCM and 31.55% for ChaCha20-Poly1305; compiler auto-vectorization improved AES-128-GCM by only 1.28%. ChaCha20-Poly1305 achieved 1.99 times the goodput of AES-128-GCM. Profiling and Amdahl's law suggest that even native-speed cryptography would leave the Wasm stack at roughly one third the goodput of the fastest native stack. Memory allocation, runtime overhead, and per-datagram UDP I/O remain constraints, so cryptographic acceleration alone is insufficient.

### Source excerpt

arXiv:2611.01989v1 Announce Type: cross Abstract: WebAssembly (Wasm) runs untrusted code in a portable, lightweight sandbox and is increasingly used to host services on shared servers and edge platforms. Running the QUIC transport protocol inside Wasm would let each application choose and update its own transport without changing the host. QUIC, however, encrypts every packet, and Wasm offers neither dedicated AES instructions nor carry-less multiplication; a Wasm QUIC stack has been reported to reach only 17.6% of native goodput, with cryptography as its largest cost. Whether the 128-bit SIMD extension of Wasm (WASM-SIMD) can recover this cost, and what limits a pure-Wasm stack once it does, has remained unclear. Here we show that explicit WASM-SIMD kernels recover much of the cryptographic cost, after which non-cryptographic costs become the limit. On two hosts connected by 10-Gigabit Ethernet, kernels that process eight AES blocks or four ChaCha20 blocks per pass raise receiver goodput over a non-SIMD baseline by 61.34% for AES-128-GCM and 31.55% for ChaCha20-Poly1305, whereas compiler auto-vectorization gains only 1.28% for AES-128-GCM. ChaCha20-Poly1305 still delivers 1.99 times the goodput of AES-128-GCM, confirming end to end the preference that stand-alone cipher benchmarks suggest. Receiver-side profiling combined with Amdahl's law predicts that even native-speed cryptography would leave Wasm at roughly one third of the goodput of the fastest native stack. Cryptographic acceleration is therefore necessary but not sufficient: memory allocation, runtime overhead and per-datagram UDP I/O now bound pure-Wasm transports. We anticipate that this per-category cost breakdown will guide further optimization of Wasm network stacks and the design of system interfaces for batched I/O.

## FreeRDP 3.33 Released With WebAssembly Support, Huge Influx Of Activity Due To AI

DevFeed: [FreeRDP 3.33 Released With WebAssembly Support, Huge Influx Of Activity Due To AI](<https://devfeed.tech/articles/freerdp-3-33-released-with-webassembly-support-huge-influx-of-activity-due-to-ai-111821.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/FreeRDP-3.33>)

Author: Michael Larabel

Published: 2026-11-02T11:07:14Z

Content type: release

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [browser](<https://devfeed.tech/tags/browser.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [experimental](<https://devfeed.tech/tags/experimental.md>), [freerdp](<https://devfeed.tech/tags/freerdp.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [llm](<https://devfeed.tech/tags/llm.md>), [macos](<https://devfeed.tech/tags/macos.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [rdp](<https://devfeed.tech/tags/rdp.md>), [release](<https://devfeed.tech/tags/release.md>), [sdl](<https://devfeed.tech/tags/sdl.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [translations](<https://devfeed.tech/tags/translations.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>), [udp](<https://devfeed.tech/tags/udp.md>), [unicode](<https://devfeed.tech/tags/unicode.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

FreeRDP 3.33 adds support for running in a web browser when compiled to WebAssembly. The release also improves the SDL client, adds experimental UDP support for direct RDP connections and experimental Windows shadow-server support, and extends keyboard, clipboard, and message-translation support. Maintainers report a large influx of pull requests and bug or regression feedback, and say a patch release addressing remaining backlog issues is planned. Version 3.33 includes 13 known security fixes.

### Source excerpt

The FreeRDP 3.33 software released today as the newest version of this open-source Microsoft Remote Desktop Protocol (RDP) implementation...

## Write Once, Instrument Anywhere: Portable, Sandboxed Tooling with WebAssembly Components

DevFeed: [Write Once, Instrument Anywhere: Portable, Sandboxed Tooling with WebAssembly Components](<https://devfeed.tech/articles/write-once-instrument-anywhere-portable-sandboxed-tooling-with-webassembly-components-107384.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.38682>)

Author: Elizabeth Gilbert, Chris Fallin, Heather Miller, Ben L. Titzer

Published: 2026-10-30T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Wasm components](<https://devfeed.tech/topics/wasm-components.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Framework](<https://devfeed.tech/topics/framework.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [cs-pl](<https://devfeed.tech/tags/cs-pl.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [ebpf](<https://devfeed.tech/tags/ebpf.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [environment](<https://devfeed.tech/tags/environment.md>), [fragmentation](<https://devfeed.tech/tags/fragmentation.md>), [framework](<https://devfeed.tech/tags/framework.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [instrumentation](<https://devfeed.tech/tags/instrumentation.md>), [language](<https://devfeed.tech/tags/language.md>), [languages](<https://devfeed.tech/tags/languages.md>), [low-level](<https://devfeed.tech/tags/low-level.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [performance](<https://devfeed.tech/tags/performance.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [portable](<https://devfeed.tech/tags/portable.md>), [porting](<https://devfeed.tech/tags/porting.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Splicer is a WebAssembly component interposition framework for portable, sandboxed instrumentation. It aims to combine application-level semantic types with tooling that can be plugged in across languages and hardware, while granting each tool only explicitly specified permissions. The abstract frames this as an alternative to the tradeoffs of language-specific frameworks, which can lose portability, and lower-level boundary instrumentation such as eBPF, which works across language boundaries but may expose bytes and packets rather than application semantics. The authors report benchmarks showing pluggability of non-trivial tools written in multiple source languages and evaluate their performance; the supplied excerpt gives no benchmark results or quantitative performance findings.

### Source excerpt

arXiv:2610.38682v1 Announce Type: new Abstract: Monitoring and debugging deployed software is crucial for scalability, performance, and robustness. Cross-cutting concerns are pervasive across software ecosystems, yet engineers must address them with a fragmented toolbox. While high-level frameworks exist to offer application-level types and semantics, they often lock a solution into specific languages, runtimes, or hardware architectures. Portability often forces engineers to choose lower-level instrumentation mechanisms. For example, in-language frameworks can trace a request across processes, but multi-language contexts require instrumentation at the boundary, for example using eBPF. While these frameworks provide powerful capabilities, they often result in 1) a tradeoff between application-level types or low-level bytes and packets, 2) non-composable domain-specific tools, 3) feature fragmentation across frameworks, and 4) tools that often run with unrestricted access to the program and its environment. We address these problems with Splicer, a WebAssembly component interposition framework that 1) provides semantically rich application-level types, 2) enables pluggable tooling with powerful capabilities, 3) reduces ecosystem fragmentation through porting across languages and hardware, and 4) confines each tool to a sandbox with explicitly granted permissions. We evaluate Splicer on a suite of benchmarks demonstrating the pluggability of non-trivial tooling written in multiple source languages and their performance.

## Two Critical Wasmtime Flaws Could Let Malicious WebAssembly Modules Escape Sandboxes

DevFeed: [Two Critical Wasmtime Flaws Could Let Malicious WebAssembly Modules Escape Sandboxes](<https://devfeed.tech/articles/two-critical-wasmtime-flaws-could-let-malicious-webassembly-modules-escape-sandboxes-100506.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/10/two-critical-wasmtime-flaws-could-let.html>)

Author: The Hacker News

Published: 2026-10-26T11:52:41Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [Compilers and Linkers](<https://devfeed.tech/topics/compilers-and-linkers.md>), [modules](<https://devfeed.tech/topics/modules.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [arm64](<https://devfeed.tech/tags/arm64.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [bug](<https://devfeed.tech/tags/bug.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-115889](<https://devfeed.tech/tags/cve-2026-115889.md>), [cve-2026-115893](<https://devfeed.tech/tags/cve-2026-115893.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [modules](<https://devfeed.tech/tags/modules.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [sandbox](<https://devfeed.tech/tags/sandbox.md>), [sandboxes](<https://devfeed.tech/tags/sandboxes.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [wasmtime](<https://devfeed.tech/tags/wasmtime.md>), [web-security](<https://devfeed.tech/tags/web-security.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Two critical Cranelift flaws in Wasmtime could let a user-controlled WebAssembly module escape its sandbox; exploitation requires a vulnerable build to compile the module, and one flaw affects only ARM64. CVE-2026-115889 affects all architectures: oversized value identifiers could overflow 24-bit fields in release builds, causing incorrect machine code. CVE-2026-115893 affects ARM64: very large br_table jump tables could exceed branch reach and redirect execution. The maintainers rated both 9.9/10; they reported no attacks, and advisories do not specify what an attacker could access after escape. Update to 36.0.19, 48.0.7, 49.0.4, or Wasmtime 50.0.0. Unsupported release lines received no fixes. Programs embedding Wasmtime must be rebuilt; updating only the command-line tool is insufficient. No workaround is listed. RustSec lists both flaws, but as of October 26 GitHub had reviewed only CVE-2026-115889, so Dependabot users should not expect an alert for the ARM64 flaw.

### Source excerpt

Two Critical Wasmtime Flaws Could Let Malicious WebAssembly Modules Escape Sandboxes Two critical flaws in Wasmtime, a WebAssembly runtime that can be built into other software, could allow a malicious WebAssembly module to escape the sandbox intended to contain it, the project's main ... Read more Published Date: Oct 26, 2026 (2 hours, 42 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-115893 CVE-2026-115889

## WADE: An LSTM-Based Anomaly Detection Engine for WebAssembly Applications

DevFeed: [WADE: An LSTM-Based Anomaly Detection Engine for WebAssembly Applications](<https://devfeed.tech/articles/wade-an-lstm-based-anomaly-detection-engine-for-webassembly-applications-99542.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.31984>)

Author: Ilaria Campestrini, Stefano Zanero, Engin Kirda

Published: 2026-10-26T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [anomaly-detection](<https://devfeed.tech/tags/anomaly-detection.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [lstm](<https://devfeed.tech/tags/lstm.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

WADE detects potential attacks in browser-executed WebAssembly by learning each application's normal function-level execution patterns. It trains an LSTM on traces gathered under benign conditions, then flags runtime deviations. The application-specific models do not require per-vulnerability signatures and are intended to detect known and previously unseen attacks. In an evaluation of 67 applications across ten vulnerability classes, WADE reported zero false negatives and a 0.42% false positive rate; these results are limited to the described dataset.

### Source excerpt

arXiv:2610.31984v1 Announce Type: cross Abstract: WebAssembly (Wasm) enables near-native performance for web applications through a portable and sandboxed execution model. However, its limited runtime protection mechanisms (e.g., the lack of stack canaries and address space layout randomization (ASLR)) leave Wasm applications vulnerable to traditional attacks. We present WADE (WebAssembly Anomaly Detection Engine), a system that detects anomalous runtime behaviors in browser-executed WebAssembly applications. WADE monitors function-level execution traces collected under benign conditions and trains a Long Short-Term Memory (LSTM) network to learn the normal execution behavior of each application. At runtime, the model flags deviations from these learned patterns as potential attacks. Unlike signature-based approaches, WADE builds application-specific behavioral models, enabling detection of both known and previously unseen attacks without per-vulnerability signatures. We evaluate WADE on a dataset of 67 WebAssembly applications spanning ten vulnerability classes, achieving zero false negatives and a 0.42% false positive rate.

## Cirkit Designer: AI-powered ESP32 development with instruction-accurate simulation

DevFeed: [Cirkit Designer: AI-powered ESP32 development with instruction-accurate simulation](<https://devfeed.tech/articles/cirkit-designer-ai-powered-esp32-development-with-instruction-accurate-simulation-99328.md>)

Original publisher: [Read original article](<https://developer.espressif.com/blog/2026/10/cirkit-esp32-s3-browser-simulation/>)

Author: John Lee

Published: 2026-10-26T00:00:00Z

Content type: article

Language: en

Sources: [Blog on Developer Portal](<https://devfeed.tech/sources/blog-on-developer-portal.md>)

Topics: [ESP32-S3](<https://devfeed.tech/topics/esp32-s3.md>), [ESP32](<https://devfeed.tech/topics/esp32.md>), [Simulation](<https://devfeed.tech/topics/simulation.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Xtensa](<https://devfeed.tech/topics/xtensa.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [arduino](<https://devfeed.tech/tags/arduino.md>), [blog](<https://devfeed.tech/tags/blog.md>), [browser](<https://devfeed.tech/tags/browser.md>), [designer](<https://devfeed.tech/tags/designer.md>), [development](<https://devfeed.tech/tags/development.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [esp32](<https://devfeed.tech/tags/esp32.md>), [esp32-s3](<https://devfeed.tech/tags/esp32-s3.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [overview](<https://devfeed.tech/tags/overview.md>), [peripherals](<https://devfeed.tech/tags/peripherals.md>), [rust](<https://devfeed.tech/tags/rust.md>), [simulation](<https://devfeed.tech/tags/simulation.md>), [web-app](<https://devfeed.tech/tags/web-app.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Cirkit Designer runs compiled ESP32 and ESP32-S3 firmware in a Rust emulator compiled to WebAssembly, executing locally in the browser and connecting firmware to modeled peripherals through interfaces such as GPIO, I2C, SPI, and PWM. Unlike the server-side QEMU approach discussed, local execution avoids a server round trip for circuit interactions; Arduino CLI builds, AI requests, and external internet access still use Cirkit's backend. The article's ISS tracker example uses an ESP32-S3, simulated ILI9341 display, and HTTPS gateway to fetch live position data, with a labeled demo mode when connectivity is unavailable. Cirkit AI can design circuits, write firmware, help diagnose issues, and create reusable models for unsupported components. Direct ESP-IDF project builds and ESP32-C3/C6 simulation are described as forthcoming.

### Source excerpt

This article introduces Cirkit Designer's simulation architecture for ESP32 and ESP32-S3: an instruction-accurate emulator built from scratch in Rust, compiled to WebAssembly, and connected to simulated hardware in the browser. We'll look at how compiled firmware executes and how it interacts with simulated peripherals.

## A Modern Browser for the PlayStation Portable

DevFeed: [A Modern Browser for the PlayStation Portable](<https://devfeed.tech/articles/a-modern-browser-for-the-playstation-portable-86044.md>)

Original publisher: [Read original article](<https://hackaday.com/2026/10/13/a-modern-browser-for-the-playstation-portable/>)

Author: Jenny List

Published: 2026-10-13T11:00:29Z

Content type: article

Language: en

Sources: [Hackaday](<https://devfeed.tech/sources/hackaday.md>)

Topics: [Plover](<https://devfeed.tech/topics/plover.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [conf](<https://devfeed.tech/tags/conf.md>), [esp32-p4](<https://devfeed.tech/tags/esp32-p4.md>), [espressif](<https://devfeed.tech/tags/espressif.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [microcontroller](<https://devfeed.tech/tags/microcontroller.md>), [playstation](<https://devfeed.tech/tags/playstation.md>), [playstation-hacks](<https://devfeed.tech/tags/playstation-hacks.md>), [playstation-portable](<https://devfeed.tech/tags/playstation-portable.md>), [processor](<https://devfeed.tech/tags/processor.md>), [psp](<https://devfeed.tech/tags/psp.md>), [ram](<https://devfeed.tech/tags/ram.md>), [web-browser](<https://devfeed.tech/tags/web-browser.md>)

### AI overview

Tilefinch is a modern web browser built for the PlayStation Portable, using Lexbor for its browser engine, QuickJS for JavaScript, and the PSP's built-in capabilities such as video decoding. The article notes that its performance has not been tested and suggests the project may point to web browsing on other limited-hardware platforms, including the ESP32-P4.

### Source excerpt

The Sony PlayStation Portable, better known as the PSP, is now over two decades old. In its day it was an impressive handheld gaming machine, not least because of the ...read more

## Vercel Labs Ships scriptc, a TypeScript-to-Native Compiler That Leaves the JavaScript Engine Behind

DevFeed: [Vercel Labs Ships scriptc, a TypeScript-to-Native Compiler That Leaves the JavaScript Engine Behind](<https://devfeed.tech/articles/vercel-labs-ships-scriptc-a-typescript-to-native-compiler-that-leaves-the-javascript-engine-behind-59808.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/09/vercel-scriptc-node/>)

Author: Daniel Curtis

Published: 2026-09-25T05:49:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Compiler](<https://devfeed.tech/topics/compiler.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>)

Tags: [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [development](<https://devfeed.tech/tags/development.md>), [execution](<https://devfeed.tech/tags/execution.md>), [has](<https://devfeed.tech/tags/has.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [native](<https://devfeed.tech/tags/native.md>), [news](<https://devfeed.tech/tags/news.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [vercel-scriptc-node](<https://devfeed.tech/tags/vercel-scriptc-node.md>), [web-development](<https://devfeed.tech/tags/web-development.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Vercel Labs released scriptc, an experimental compiler that converts TypeScript into small native executables without Node, V8, or a JavaScript engine. It can emit C, LLVM IR, assembly, native executables, or WebAssembly. Early benchmarks show much faster startup and lower memory use than Node, but slower execution in some workloads and limited compatibility with npm packages.

### Source excerpt

Vercel Labs has introduced scriptc, an experimental compiler that converts TypeScript into small native executables without relying on Node, V8, or a JavaScript engine. It uses the TypeScript compiler for type checking and can output C or WebAssembly code. Initial benchmarks show faster startup times and lower memory usage than Node, though it experiences slower execution speeds. By Daniel Curtis

## Apple Releases Swift 6.4 with Cross-Platform Builds, Interoperability, and Performance Improvements

DevFeed: [Apple Releases Swift 6.4 with Cross-Platform Builds, Interoperability, and Performance Improvements](<https://devfeed.tech/articles/apple-touts-simpler-and-clearer-code-with-swift-6-4-58972.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4225734/apple-touts-simpler-and-clearer-code-with-swift-6-4.html>)

Author: Paul Krill

Published: 2026-09-23T22:59:35Z

Content type: release

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [Swift](<https://devfeed.tech/topics/swift.md>), [Programming language](<https://devfeed.tech/topics/programming-language.md>), [cross-platform](<https://devfeed.tech/topics/cross-platform.md>), [interoperability](<https://devfeed.tech/topics/interoperability.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Compiler](<https://devfeed.tech/topics/compiler.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Microcontroller](<https://devfeed.tech/topics/microcontroller.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browser](<https://devfeed.tech/tags/browser.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [interoperability](<https://devfeed.tech/tags/interoperability.md>), [memory-safety](<https://devfeed.tech/tags/memory-safety.md>), [programming-language](<https://devfeed.tech/tags/programming-language.md>), [programming-languages](<https://devfeed.tech/tags/programming-languages.md>), [programming-languages-software-development-swift](<https://devfeed.tech/tags/programming-languages-software-development-swift.md>), [release](<https://devfeed.tech/tags/release.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [swift](<https://devfeed.tech/tags/swift.md>), [swift-6](<https://devfeed.tech/tags/swift-6.md>), [swift-6-4](<https://devfeed.tech/tags/swift-6-4.md>)

### AI overview

Apple released Swift 6.4 with updates to core library APIs, builds, debugging, interoperability, and performance. The release makes Swift Build the default in Swift Package Manager, adds stable cross-platform subprocess support, expands C++ and Java interoperability, improves WebAssembly performance, and adds capabilities for embedded Swift and memory-safe programming.

### Source excerpt

Apple has released Swift 6.4, an upgrade to the programming language that brings improvements across the board including core library APIs, builds, debugging, interoperability with other platforms, and performance. Swift 6.4 was announced September 15. "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," Apple's Joe Heck and Holly Borla wrote in the announcement. They listed the following highlights of the release: 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 JavaScript kit 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. Swift 6.4 also completes a multi-release overhaul of how the compiler tracks Swift modules in debug info. LLDB now imports modules through precise dependency tracking instead of by-name lookups. Debug builds on Linux and Windows, and dSYM bundles on Darwin, shrink significantly because binary Swift modules are no longer embedded in them. Swift 6.4 also makes it easier to avoid unnecessary copies of data while staying memory-safe, extending earlier work on Span, non-copyable types, and InlineArray, ac

## Building ASGI Microservices with Cloudflare Python Workers in Production

DevFeed: [Building ASGI Microservices with Cloudflare Python Workers in Production](<https://devfeed.tech/articles/building-asgi-microservices-with-cloudflare-python-workers-in-production-58324.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/asgi-microservices-on-cloudflare-python-workers/>)

Author: SitePoint Team

Published: 2026-09-22T19:08:57Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [ASGI](<https://devfeed.tech/topics/asgi.md>), [Cloudflare Workers](<https://devfeed.tech/topics/cloudflare-workers.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Python](<https://devfeed.tech/topics/python.md>), [FastAPI](<https://devfeed.tech/topics/fastapi.md>), [async](<https://devfeed.tech/topics/async.md>), [Starlette](<https://devfeed.tech/topics/starlette.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [API](<https://devfeed.tech/topics/api.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>), [V8](<https://devfeed.tech/topics/v8.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [async](<https://devfeed.tech/tags/async.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-workers](<https://devfeed.tech/tags/cloudflare-workers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [edge](<https://devfeed.tech/tags/edge.md>), [fastapi](<https://devfeed.tech/tags/fastapi.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [programming](<https://devfeed.tech/tags/programming.md>), [pyodide](<https://devfeed.tech/tags/pyodide.md>), [python](<https://devfeed.tech/tags/python.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [starlette](<https://devfeed.tech/tags/starlette.md>), [web](<https://devfeed.tech/tags/web.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

A practical guide to deploying production ASGI microservices built with Python frameworks such as FastAPI and Starlette on Cloudflare Workers. It covers edge execution, authenticated fan-out, Workers KV caching, global deployment, and cold-start optimization.

### Source excerpt

Deploy a Python ASGI microservice on Cloudflare Workers: Pyodide cold-start mitigation, async subrequest handling, and KV-backed state caching. Continue reading Building ASGI Microservices with Cloudflare Python Workers in Production on SitePoint.

## How Penpot Added Glassmorphism Background Blur with WebGL

DevFeed: [How Penpot Added Glassmorphism Background Blur with WebGL](<https://devfeed.tech/articles/say-hello-to-background-blur-58001.md>)

Original publisher: [Read original article](<https://penpot.app/blog/say-hello-to-background-blur/>)

Author: Elena Torró

Published: 2026-09-22T17:03:40Z

Content type: article

Language: en

Sources: [Penpot Blog](<https://devfeed.tech/sources/penpot-blog.md>)

Topics: [User interface design](<https://devfeed.tech/topics/ui-design.md>), [glassmorphism](<https://devfeed.tech/topics/glassmorphism.md>), [WebGL](<https://devfeed.tech/topics/webgl.md>), [Rust](<https://devfeed.tech/topics/rust.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Canvas](<https://devfeed.tech/topics/canvas.md>), [SVG](<https://devfeed.tech/topics/svg.md>), [CSS](<https://devfeed.tech/topics/css.md>), [render](<https://devfeed.tech/topics/render.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [canvas](<https://devfeed.tech/tags/canvas.md>), [code](<https://devfeed.tech/tags/code.md>), [css](<https://devfeed.tech/tags/css.md>), [design](<https://devfeed.tech/tags/design.md>), [glassmorphism](<https://devfeed.tech/tags/glassmorphism.md>), [pixels](<https://devfeed.tech/tags/pixels.md>), [rust](<https://devfeed.tech/tags/rust.md>), [svg](<https://devfeed.tech/tags/svg.md>), [ui](<https://devfeed.tech/tags/ui.md>), [ui-design](<https://devfeed.tech/tags/ui-design.md>), [websites](<https://devfeed.tech/tags/websites.md>)

### AI overview

Penpot explains how it added glassmorphism-style background blur by using its WebGL renderer, Rust-to-WebAssembly engine, and Skia's backdrop-filter support. The article contrasts this approach with limitations in SVG rendering and browser support.

### Source excerpt

Have you ever heard what "glassmorphism" is? Maybe not, but I'm sure you've seen an increase in glass effects in UI design across websites, apps, and operating systems.

## Cloudflare Python Workers are now generally available

DevFeed: [Cloudflare Python Workers are now generally available](<https://devfeed.tech/articles/cloudflare-python-workers-are-now-generally-available-57666.md>)

Original publisher: [Read original article](<https://simonwillison.net/2026/Sep/21/cloudflare-python-worker/>)

Author: Simon Willison

Published: 2026-09-21T22:25:44Z

Content type: release

Language: en

Sources: [Simon Willison's Weblog](<https://devfeed.tech/sources/simon-willison-s-weblog.md>)

Topics: [Python](<https://devfeed.tech/topics/python.md>), [Cloudflare](<https://devfeed.tech/topics/cloudflare.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Developer Platform](<https://devfeed.tech/topics/developer-platform.md>), [V8](<https://devfeed.tech/topics/v8.md>), [PyPI](<https://devfeed.tech/topics/pypi.md>), [Simulation](<https://devfeed.tech/topics/simulation.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [cloudflare-33](<https://devfeed.tech/tags/cloudflare-33.md>), [developer-platform](<https://devfeed.tech/tags/developer-platform.md>), [development](<https://devfeed.tech/tags/development.md>), [development-environment](<https://devfeed.tech/tags/development-environment.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>), [node](<https://devfeed.tech/tags/node.md>), [pyodide](<https://devfeed.tech/tags/pyodide.md>), [pyodide-52](<https://devfeed.tech/tags/pyodide-52.md>), [pypi](<https://devfeed.tech/tags/pypi.md>), [python](<https://devfeed.tech/tags/python.md>), [python-1-284](<https://devfeed.tech/tags/python-1-284.md>), [release](<https://devfeed.tech/tags/release.md>), [running](<https://devfeed.tech/tags/running.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [v8](<https://devfeed.tech/tags/v8.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [webassembly-132](<https://devfeed.tech/tags/webassembly-132.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Cloudflare Python Workers have reached general availability after a two-year preview. The platform runs Python through Pyodide-compiled WebAssembly in the V8-based workerd runtime, with limitations including non-functional multiprocessing and threading. Its local development tool simulates the stack using a 123MB binary.

### Source excerpt

Cloudflare Python Workers are now generally available After a two year preview, Cloudflare's support for running Python code in their server-side Workers platform is now stable: "Python is now a first-class, fully supported language on the Cloudflare Developer Platform". A neat thing about this is how it works. Cloudflare are running Python compiled to WebAssembly via Pyodide in their V8-based workerd runtime. This comes with some limitations, documented here - most notably both multiprocessing and threading are non-functional in the WebAssembly VM. One particularly interesting detail of this is the local development environment story - their pywrangler development tool (confusingly packaged as workers-py on PyPI) runs a full local simulation of their stack, including executing code with Pyodide in WebAssembly in V8 in a 123MB workerd binary, which for me ended up in node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd. Python Workers represent a significant investment in the wider Python ecosystem by Cloudflare. The release announcement is credited to Gyeongjae Choi, Dominik Picheta, and Hood Chatham - Gyeongjae and Hood are both Pyodide core maintainers. Via Hacker News Tags: python, cloudflare, webassembly, pyodide

## Firebase Phone Number Authentication in Kotlin/Wasm (Part 3)

DevFeed: [Firebase Phone Number Authentication in Kotlin/Wasm (Part 3)](<https://devfeed.tech/articles/firebase-phone-number-authentication-in-kotlin-wasm-part-3-55442.md>)

Original publisher: [Read original article](<https://proandroiddev.com/kotlin-wasm-auth-part-3-phone-sign-in-9b47f1993940?source=rss----c72404660798---4>)

Author: Tomislav Mladenov

Published: 2026-09-19T16:03:23Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Firebase](<https://devfeed.tech/topics/firebase.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Firebase console](<https://devfeed.tech/topics/firebase-console.md>), [Wasm components](<https://devfeed.tech/topics/wasm-components.md>)

Tags: [auth](<https://devfeed.tech/tags/auth.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [billing](<https://devfeed.tech/tags/billing.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [firebase-console](<https://devfeed.tech/tags/firebase-console.md>), [firebaseauthentication](<https://devfeed.tech/tags/firebaseauthentication.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [kotlin-wasm](<https://devfeed.tech/tags/kotlin-wasm.md>), [number](<https://devfeed.tech/tags/number.md>), [phone](<https://devfeed.tech/tags/phone.md>), [phone-authentication](<https://devfeed.tech/tags/phone-authentication.md>), [recaptcha](<https://devfeed.tech/tags/recaptcha.md>), [region](<https://devfeed.tech/tags/region.md>), [regions](<https://devfeed.tech/tags/regions.md>), [requires](<https://devfeed.tech/tags/requires.md>), [series](<https://devfeed.tech/tags/series.md>), [sign-in](<https://devfeed.tech/tags/sign-in.md>), [sms](<https://devfeed.tech/tags/sms.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [wasm](<https://devfeed.tech/tags/wasm.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### AI overview

Firebase phone sign-in in Kotlin/Wasm needs Blaze billing enabled and the desired SMS region allowed in Firebase settings; otherwise attempts fail with `auth/billing-not-enabled` or `auth/operation-not-allowed`. The flow adds bindings for `RecaptchaVerifier`, `PhoneAuthProvider` and `signInWithCredential`, plus a DOM element for the verifier. Each attempt should clear the previous verifier and create a fresh one because reCAPTCHA tokens are single-use; reusing one can cause retries to fail with `auth/invalid-app-credential`. Sign-in first verifies the phone number and stores its verification ID, then exchanges that ID and the SMS code for a credential and signed-in user. For development, a console-registered fictional number and fixed code can be used with app verification disabled, avoiding captcha, real SMS and quota use; the excerpt cautions against shipping with that switch enabled.

### Source excerpt

Part 3 of the Wasm series is phone sign-in, and the Kotlin code is once again the easy half. Before you write a line, know the three Firebase console traps. Phone auth now requires the Blaze plan, and until billing is on every attempt fails with auth/billing-not-enabled, fictional test numbers included. The SMS region policy (Authentication -> Settings -> SMS region policy) denies all regions by default and returns auth/operation-not-allowed until you allow yours. And reCAPTCHA tokens are single-use, which we'll get to in the code. Console sorted? Good, the Wasm part is pleasantly small. Phone sign-in needs four things our part 1 bindings didn't have: a reCAPTCHA verifier, the phone provider, a credential sign-in function and the user's phone number. All of them go into the same @file:JsModule("firebase/auth") file: external class RecaptchaVerifier( auth: Auth, container: String, parameters: JsAny, ) : JsAny { fun clear() } external class PhoneAuthProvider(auth: Auth) : JsAny { fun verifyPhoneNumber(phoneNumber: String, applicationVerifier: RecaptchaVerifier): Promise<JsString> companion object { fun credential(verificationId: String, verificationCode: String): JsAny } } external fun signInWithCredential(auth: Auth, credential: JsAny): Promise<UserCredential> Two small js() helpers stand in for what would be dynamic on Kotlin/JS: one builds the verifier options, the other flips Firebase's testing switch: private fun invisibleRecaptchaParams(): JsAny = js("({ size: 'invisible' })") private fun disableAppVerificationForTesting(auth: Auth): Unit = js("{ auth.settings.appVerificationDisabledForTesting = true; }") The verifier also wants a real DOM element to attach to, and our UI is a Compose canvas, so we create a plain div for it once: private fun recaptchaContainer(): String { if (document.getElementById(RECAPTCHA_CONTAINER_ID) == null) { val container = document.createElement("div") container.setAttribute("id", RECAPTCHA_CONTAINER_ID) document.body?.appendChild(cont

## Persistent Databases in the Browser with DuckDB-Wasm and OPFS

DevFeed: [Persistent Databases in the Browser with DuckDB-Wasm and OPFS](<https://devfeed.tech/articles/persistent-databases-in-the-browser-with-duckdb-wasm-and-opfs-42756.md>)

Original publisher: [Read original article](<https://duckdb.org/2026/09/18/opfs-wasm.html>)

Author: Carlo Piovesan, Geertjan Wielenga

Published: 2026-09-18T00:00:00Z

Content type: article

Language: en

Sources: [DuckDB](<https://devfeed.tech/sources/duckdb.md>)

Topics: [DuckDB](<https://devfeed.tech/topics/duckdb.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Filesystems](<https://devfeed.tech/topics/filesystems.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [2021](<https://devfeed.tech/tags/2021.md>), [2023](<https://devfeed.tech/tags/2023.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [await](<https://devfeed.tech/tags/await.md>), [backend](<https://devfeed.tech/tags/backend.md>), [background](<https://devfeed.tech/tags/background.md>), [batch](<https://devfeed.tech/tags/batch.md>), [bigint](<https://devfeed.tech/tags/bigint.md>), [browser](<https://devfeed.tech/tags/browser.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [duckdb](<https://devfeed.tech/tags/duckdb.md>), [file](<https://devfeed.tech/tags/file.md>), [file-system](<https://devfeed.tech/tags/file-system.md>), [using-duckdb](<https://devfeed.tech/tags/using-duckdb.md>), [wasm](<https://devfeed.tech/tags/wasm.md>)

### AI overview

DuckDB-Wasm can reopen a database stored in the browser's Origin Private File System (OPFS) after reloads, using an `opfs://` path. The article reports persistence with versions 1.32.0 and 1.33.1-dev64.0 or later; the then-current npm `latest` build, 1.33.1-dev57.0, created files but did not write to them. SQL references to other OPFS files can be registered automatically with `opfs: { fileHandling: 'auto' }` or manually; manual registration avoids reacquiring handles on every statement. Writes go to a WAL and reach the main database file at checkpoints. Because browser tabs may end without clean shutdown, the article recommends checkpointing after each batch of important writes; setting `checkpoint_threshold` to `0KB` checkpoints after every statement at a throughput cost. OPFS may be evicted or cleared, so it should not be the only copy of irreplaceable data. The database can be read back through the browser OPFS API or exported as Parquet. The article also notes one handle per file and limits on SQL renames.

### Source excerpt

DuckDB-Wasm can open a persistent database file in the browser's Origin Private File System (OPFS). This post shows how, and when data reaches disk.

## 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](<https://devfeed.tech/articles/kermit-2-2-0-adds-wasmwasi-support-and-a-new-coil3-extension-kevin-schildhorn-38233.md>)

Original publisher: [Read original article](<https://touchlab.co/kermit-220>)

Published: 2026-09-16T00:00:00Z

Content type: release

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Library](<https://devfeed.tech/topics/library.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [Extension](<https://devfeed.tech/topics/extension.md>)

Tags: [2-2](<https://devfeed.tech/tags/2-2.md>), [coil](<https://devfeed.tech/tags/coil.md>), [extension](<https://devfeed.tech/tags/extension.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kermit](<https://devfeed.tech/tags/kermit.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [library](<https://devfeed.tech/tags/library.md>), [swift](<https://devfeed.tech/tags/swift.md>), [update](<https://devfeed.tech/tags/update.md>), [version](<https://devfeed.tech/tags/version.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>)

### 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.

## New Release: Tor Browser 15.0.23

DevFeed: [New Release: Tor Browser 15.0.23](<https://devfeed.tech/articles/new-release-tor-browser-15-0-23-53189.md>)

Original publisher: [Read original article](<https://blog.torproject.org/new-release-tor-browser-15023/>)

Author: ma1

Published: 2026-09-15T00:00:00Z

Content type: release

Language: en

Sources: [Tor Project](<https://devfeed.tech/sources/tor-project-blog.md>)

Topics: [tor](<https://devfeed.tech/topics/tor.md>), [Firefox](<https://devfeed.tech/topics/firefox.md>), [Security](<https://devfeed.tech/topics/security.md>), [browser](<https://devfeed.tech/topics/browser.md>), [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [changelog](<https://devfeed.tech/topics/changelog.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [applications](<https://devfeed.tech/tags/applications.md>), [browser](<https://devfeed.tech/tags/browser.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [digicert](<https://devfeed.tech/tags/digicert.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [security](<https://devfeed.tech/tags/security.md>), [tor](<https://devfeed.tech/tags/tor.md>), [version](<https://devfeed.tech/tags/version.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Tor Browser 15.0.23 is available with Firefox security updates and other platform-specific changes. The release also documents an expired DigiCert EV certificate affecting fresh Windows installations of earlier versions, along with a temporary workaround and a full changelog.

### Source excerpt

Tor Browser 15.0.23 is now available from the Tor Browser download page and also from our distribution directory. This version includes important security updates to Firefox. Windows Package Signature Issue The DigiCert EV code-signing certificate we use to sign Windows installation packages is expired since September 1st and we are currently in the process to renew it. Unfortunately, this process is delayed and not yet complete. This has caused Windows users trying to install Tor Browser 15.0.21 and 15.0.22 from scratch to receive "bad signature" warnings. As a temporary work-around, for Windows only we're keeping Tor Browser 15.0.20 (the latest correctly signed version) listed on our download page, relying on automatic updates (which are signed with a different key, not involving this expired certificate) to bring Windows users to the current version. Users who prefer to download the latest version directly, ignoring the certificate expiration warning, can download it from https://dist.torproject.org/torbrowser/15.0.23/. Send us your feedback If you find a bug or have a suggestion for how we could improve this release, please let us know. Full changelog The full changelog since Tor Browser 15.0.22 is: All Platforms Updated NoScript to 13.6.33.1984 Bug tor-browser#45296: (H1) SharedWorker Identity Mismatch allows WebAssembly execution at Safer Bug tor-browser#45297: (H1) Missing setHTMLUnsafe hook leaves a permanent WebAssembly-capable child realm at Safer Bug tor-browser#45299: Backport Security Fixes from Firefox 156 Bug tor-browser#45303: Rebase Tor Browser stable onto 140.16.0esr Bug tor-browser-build#41875: Update relprep.py for the new versions.ini URL Windows + macOS + Linux Updated Firefox to 140.16.0esr Linux Bug tor-browser#44996: Change the 32-bit linux message to the expired version for the final 15.0 release Android Updated GeckoView to 140.16.0esr Build System All Platforms Bug tor-browser-build#41871: Update downloads repository references in relprep

## Caught Sleeping at Work(queue) -- Zephyr Podcast #050

DevFeed: [Caught Sleeping at Work(queue) -- Zephyr Podcast #050](<https://devfeed.tech/articles/caught-sleeping-at-work-queue-zephyr-podcast-050-38674.md>)

Original publisher: [Read original article](<https://zephyrproject.org/caught-sleeping-at-workqueue-zephyr-podcast-050/>)

Author: Benjamin Cabé

Published: 2026-09-11T12:46:06Z

Content type: news

Language: en

Sources: [Zephyr Project](<https://devfeed.tech/sources/zephyr-project-2.md>)

Topics: [WebAssembly](<https://devfeed.tech/topics/web-assembly.md>), [qemu](<https://devfeed.tech/topics/qemu.md>), [ESP32](<https://devfeed.tech/topics/esp32.md>), [ctf](<https://devfeed.tech/topics/ctf.md>), [Espressif](<https://devfeed.tech/topics/espressif.md>), [Arduino](<https://devfeed.tech/topics/arduino.md>), [RISC-V](<https://devfeed.tech/topics/riscv.md>), [cortex m4](<https://devfeed.tech/topics/cortex-m4.md>), [Ethernet](<https://devfeed.tech/topics/ethernet.md>), [Modbus](<https://devfeed.tech/topics/modbus.md>), [USB](<https://devfeed.tech/topics/usb.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [ctf](<https://devfeed.tech/tags/ctf.md>), [esp32](<https://devfeed.tech/tags/esp32.md>), [espressif](<https://devfeed.tech/tags/espressif.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [linux](<https://devfeed.tech/tags/linux.md>), [modbus](<https://devfeed.tech/tags/modbus.md>), [perfetto](<https://devfeed.tech/tags/perfetto.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [qemu](<https://devfeed.tech/tags/qemu.md>), [risc-v](<https://devfeed.tech/tags/risc-v.md>), [usb](<https://devfeed.tech/tags/usb.md>), [webassembly](<https://devfeed.tech/tags/webassembly.md>), [zephyr](<https://devfeed.tech/tags/zephyr.md>)

### 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.

[Next page](<https://devfeed.tech/topics/web-assembly.md?cursor=WyIyMDI2LTA5LTExVDEyOjQ2OjA2KzAwOjAwIiwgIjMwZTlmZWQyLTEyNzgtNDIyYi1hNWUyLTBmNzgyMzI4NTY5OCJd>)