Be sure to check out Deepti Gandluri's and Austin Eng's talk on #WebAssembly and #WebGPU enhancements for faster Web AI: https://youtu.be/VYJZGa9m34w?si=_PPuJQJ9Zor5AyID. Running Al inference directly on client machines reduces latency, improves privacy by keeping all data on the client, and saves server costs. To accelerate these workloads, #Wasm and WebGPU are evolving to incorporate new low-level primitives. #GoogleIO
Our #GoogleIO talk is finally online 🎉! Thomas Nattestad and I share how Goodnotes ported their award-winning iPad app to the Web thanks to #WebAssembly, and SwiftWasm specifically. Next, we give an overview of how #Wasm is being used by various product teams at Google, including Google Photos, Sheets, Meet, and others. Lastly, I show how C++ image filters from a fictitious iOS and Android app called Delayedgram (🥁) can be ported to the Web and the filter code be shared!
The #game jam co-organized by Dave Thompson, CTO at @spritelyinst, starts today and are an excellent opportunity to test-drive the #Spritely#Hoot project's #Guile to #WebAssembly facilities.
Get inspired by last year's jam, and join the 10-day event..
Would be sweet if I can have a static #HTML / #CSS website that uses #HTMX for interaction with a backend written in Kotlin and compiled to #wasm running on an edge location using #wasi .
🎧 Just recorded episode 2 of the #WasmAssembly podcast with ✨ Deepti Gandluri ✨. In this episode, we talk about #Wasm's standardization, bleeding-edge and mature #WebAssembly proposals Deepti is excited about, and—of course—#AI and #WebGPU!
It's scheduled to be released in two weeks 🗓️. Now is a good time to subscribe to the show in your favorite podcast application: https://wasmassembly.libsyn.com/!
This gives a lot of people the possibility to begin using a platform with components that they already know and love -- and it gives the ability to target any arch or os with one "artifact". multiarch builds goes away here.
With Preview 2 of WASI and the Component Model complete and shipping 🎉 now we set our sights on what’s to come in Preview 3: native async support. #webassembly
Listen in as Luke Wagner takes you on that journey!
Extension.js: a plug-and-play, zero-config, cross-browser extension development tool with built-in support for #TypeScript, #WebAssembly, React, and modern #JavaScript.
I'm happy to announce I will be speaking at #RustFestZurich this year. My talk is about Linon, a graphical #RustLang application I began writing during my MSc studies at @uniheidelberg for interactively exploring the visual effects of continuous refraction or distortion of light rays. The application is based on #wgpu, making heavy use of #WGSL compute shaders.
GTK uses Vulkan by default on Wayland now. The migration from X to Wayland is super fascinating and intricate. I’ve been watching it unfold for years and have fought the urge to do deep dives. Future UI toolkits will continue to use multiple rendering engines and will facilitate compiling for desktop and/or browser which is going to reduce interest in JavaScript UI frameworks. There are frameworks that behave/look the same as desktop and Web applications.
Excited to listen to the first episode of @tomayac ‘s new WebAssembly podcast where he interviews Alon Zakai about the history and pre-history of #webassembly:
Learn about some early #WebAssembly history from one of the co-creators of #Wasm, Alon Zakai! Follow along how Alon explains how we came from Native Client to asm.js and then finally to WebAssembly, and explore some interesting historical and present day sidetracks on the way.
Getting started with #WebAssembly? Let us point you in the right direction with videos on OS design, the component model, security features, generative AI and more! ▶️
> I mean, you get problems if you try to launch a thread…
Which specific problems are you refering to?
As far as I understand, you can spawn threads in JS environments (e.g. in the browser) with no problems (using Web Workers and SharedArrayBuffer under the hood).
Only spawning them in non-JS environments is currently not supported, if I'm not mistaken. For this, we'll need the thread-spawn proposal implemented, right!?
Just updated all https://thi.ng/wasm-api packages, bindgen, build scripts, readmes and examples to be compatible with the brand new Zig v0.12.0 released a couple of days ago... This includes adapting to breaking changes (esp. Zig's build system) and updating the hybrid Zig/WASM/TypeScript project template: