WebAssembly Pushes Browsers Toward Native-Class Apps

  submitted by   <a href="https://www.reddit.com/user/Active-Fuel-49"> /u/Active-Fuel-49 </a> <br/> <span><a href="https://emnudge.dev/blog/what-happened-to-webassembly/">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1s4ypq8/what_happened_to_webassembly/">[comments]</a></span>

Inside Ohm's PEG-to-Wasm compiler

Apple's intentional crippling of Mobile Safari continues | Hacker News Hacker News new | past | comments | ask | show | jobs | submit login Apple's intentional crippling of Mobile Safari continues ( pwa.gripe ) 20 points by xd1936 2 hours ago | hide | past | favorite | discuss help Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact Search:

  submitted by   <a href="https://www.reddit.com/user/Low-Trust2491"> /u/Low-Trust2491 </a> <br/> <span><a href="https://rune.codes/hub/tech-trends/webassembly-beyond-the-browser-the-universal-runtime-of-2026">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1s0lwp6/webassembly_is_breaking_out_of_the_browser_from/">[comments]</a></span>

mohebifar/tooscut: Professional video editing, right in your browser. Made with Rust, WebGPU, WASM, and Tanstack Start.

A new browser-based non-linear editor (NLE) demonstrates professional video editing powered by WebGPU and Rust/WASM, delivering GPU-accelerated compositing, real-time previews, and near-native export performance without installs. The app features a multi-track timeline, unlimited video and audio tracks, linked clips, cross-transitions, and keyframe animation with bezier easing for transform, opacity, and effect parameters. Real-time GPU-computed effects include brightness, contrast, saturation, blur, and hue rotation, while the File System Access API enables local-first workflows so media never leaves the user’s machine. By combining WebGPU, WebAssembly, and Web Audio, the project highlights how modern web APIs can replace native apps for high-performance creative workflows and lower friction for distribution and trials.

A free, open-source non-linear video editor (NLE) running entirely in the browser leverages WebGPU, WASM, Rust/WGPU, and TanStack to deliver professional editing features without native installs. Posted on Hacker News, the project demonstrates that modern web graphics APIs and WebAssembly can handle intensive media processing, though users report playback issues on some devices (e.g., M2 Air on Safari). Key players include the open-source project (tooscut.app), WebGPU/WASM tooling, and Rust/WGPU for performance. This matters because it lowers friction for web-based content workflows, enables integration into web apps, and showcases how browser-native GPU access can rival desktop software for demanding tasks.

A browser-based professional NLE video editor, built with WebGPU and Rust compiled to WASM, delivers GPU-accelerated compositing, keyframe animation, and real-time previews rivaling native apps. The editor supports a canvas-rendered, multi-track timeline with unlimited video/audio tracks, linked clips, cross-transitions, and bezier-eased keyframeable properties (transform, opacity, effects). Real-time GPU-computed effects include brightness, contrast, saturation, blur, and hue rotation. It uses WebAssembly performance and WebGPU for rendering while keeping media local via the File System Access API and Web Audio for playback—no installation required. This matters because it showcases the web platform’s maturation for high-performance creative apps and could shift workflows toward zero-install, privacy-friendly browser tooling.

  submitted by   <a href="https://www.reddit.com/user/waozen"> /u/waozen </a> <br/> <span><a href="https://www.openui.com/blog/rust-wasm-parser">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1rzfwwy/rewriting_our_rust_wasm_parser_in_typescript/">[comments]</a></span>

Edge.js, open-sourced by Wasmer, is a Node-compatible JavaScript runtime that runs existing Node.js apps and native modules inside a WebAssembly-backed sandbox. It preserves full Node semantics (v24) and reuses Node dependencies (libuv, llhttp, etc.) while isolating unsafe operations—OS system calls and native code—via WASIX; the JS engine itself is pluggable (V8, JavaScriptCore, QuickJS) and remains sandboxed. The approach aims to deliver container-free, high-density, fast-startup execution for serverless, AI, and edge workloads, achieving roughly 5–30% overhead compared with native Node when using --safe mode. This matters because it promises easier migration of existing Node apps to secure, scalable edge environments without breaking compatibility.

Edge.js: Run Node apps inside a WebAssembly sandbox | Hacker News Hacker News new | past | comments | ask | show | jobs | submit login Edge.js: Run Node apps inside a WebAssembly sandbox ( wasmer.io ) 14 points by syrusakbary 1 hour ago | hide | past | favorite | discuss help Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact Search:

  submitted by   <a href="https://www.reddit.com/user/syrusakbary"> /u/syrusakbary </a> <br/> <span><a href="https://wasmer.io/posts/edgejs-safe-nodejs-using-wasm-sandbox">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1rwe78b/edgejs_running_node_apps_inside_a_webassembly/">[comments]</a></span>

@ihtesham2005: 🚨 RIP Chrome for AI agents. Someone built a headless browser from scratch that runs 11x faster and

lightpanda-io / browser

  submitted by   <a href="https://www.reddit.com/user/ketralnis"> /u/ketralnis </a> <br/> <span><a href="https://component-model.bytecodealliance.org/">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1rrugle/the_webassembly_component_model/">[comments]</a></span>

Author built a live benchmark and demo comparing JavaScript (CPU) and WebGPU (GPU) in the browser, showing when GPU compute makes sense. The article explains WebGPU’s role beyond graphics—enabling parallel compute in web apps—and contrasts CPU (JavaScript/WebAssembly) and GPU strengths. The author created practical, not academic, tests (linked GitHub repo and live demo) including a particle simulation to illustrate workloads where GPUs excel. The piece targets web developers and conference attendees (jsDay), and emphasizes pragmatic evaluation rather than theoretical claims, inviting readers to try the demo and examine the code. This matters because WebGPU + WebAssembly can unlock higher-performance browser compute for graphics, simulations, and data-parallel tasks.

  submitted by   <a href="https://www.reddit.com/user/self"> /u/self </a> <br/> <span><a href="https://github.com/friendlymatthew/gabagool">[link]</a></span>   <span><a href="https://www.reddit.com/r/programming/comments/1rqx2ms/snapshotable_webassembly_interpreter_from_scratch/">[comments]</a></span>

A fully snapshotable Wasm interpreter

A developer tried to implement a fully client-side text-generation feature using WebAssembly/WebGPU for privacy but ran into severe UX issues because their custom caching made users re-download a 1.5GB model after cache clears or hard refreshes. The article details the pain of shipping large model files in the browser, the limitations of the browser cache, and the need for robust caching strategies and storage APIs to avoid wasting user bandwidth. It highlights trade-offs between on-device privacy and practical delivery, and argues for better tooling and platform support (e.g., IndexedDB, Service Workers, cache partitioning) to make browser AI viable. This matters for web apps wanting local inference without backend costs or telemetry leakage.

Notes on Writing WASM

Show HN: 原生 WebGPU / WebGL 性能分析工具（适用于 Mac）

A developer ported fogleman/primitive — a Go CLI that recreates images using primitive shapes via hill-climbing — to run entirely in the browser by compiling its core to WebAssembly. The in-browser demo (primitive-playground.taiseiue.jp) lets users drop images and watch them reconstruct shape-by-shape (triangles, ellipses, beziers, etc.) client-side with no server dependency; source is on GitHub (taiseiue/primitive-playground). This makes an otherwise terminal-bound tool accessible to wider audiences and preserves privacy/performance by avoiding server uploads. It’s relevant for web developers, graphics hobbyists, and WASM adopters; the author invites suggestions for additional shapes or features.

elfconv：Linux应用程序到高性能Wasm二进制翻译器（2025）

elfconv: Linux Apps to High-Performance Wasm Binary Translator (2025)

The author ported their long-running open-source Scheme project Bob — a suite including an interpreter, compiler and VM written in Python — to target WebAssembly, enabling Scheme code to run in browsers and other Wasm hosts. They explain motivations (modern deployment, performance, sandboxing) and technical work: compiling Scheme to WebAssembly, adapting the runtime and memory model, and integrating with JavaScript/Web APIs. The piece highlights tooling and challenges around garbage collection, calling conventions, and interop between Python-based components and Wasm. This matters because it modernizes a legacy language implementation for web delivery, demonstrates practical Wasm compilation patterns, and may help language implementers and educators deploy lightweight language VMs to the browser.

A developer ported Meta’s HTDemucs v4 music source-separation model to Rust using the Burn deep-learning framework, enabling full inference in-browser (WASM + WebGPU) and as native CLI or DAW plugin. The project (demucs-rs) runs locally with no server or Python runtime; model weights (f16 safetensors) are cached from Hugging Face and include 4‑stem, 6‑stem, and higher-quality variants. Native builds use Metal on macOS and Vulkan on Linux/Windows; a VST3/CLAP plugin with SwiftUI lets producers separate stems inside a DAW and export or play stems via MIDI/faders. The rewrite improves portability and privacy, showcasing Rust+Burn for ML on WASM and practical music-production workflows.

An item titled “Making WebAssembly a first-class language on the Web” indicates a focus on elevating WebAssembly (Wasm) from a compilation target to a more fully supported, native-feeling programming option in web browsers. Based on the title alone, the likely topic is improvements to the web platform—such as tooling, debugging, interoperability with JavaScript and Web APIs, and developer experience—that would make Wasm easier to write, deploy, and maintain for web applications. If implemented, such changes could broaden the kinds of software that run efficiently in the browser and reduce reliance on JavaScript for performance-critical code. No further details, dates, organizations, or specific proposals are available because the article body was not provided.