Well, it took about 2 weeks longer than I expected (spare time for programming is especially spare at times!) but I finally finished swapping out the graphical backend of my roguelike project with a handrolled one using #wgpu! I'm super excited to be fully in control of my #gamedev destiny!
Wgpu is still pretty difficult, even if it is cleaner than opengl with glow and #glutin. (And up-to-date with its own dependencies, always nice!) #rust
At some point I'll need to refactor all this again if I want to support #wasm. Wasm puts a lot of restrictions on the game I don't like, but the ease of access for players (just try it in the browser!) is an undeniable draw. Maybe I can do a cut-down version, like a demo or shareware for the web? #gamedev#rust
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!
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 .
I thought I would take up the challenge of getting @enhance_dev#WASM working with #aspnetcore with the ability to SSR web components directly into the request pipeline.
Someone big doing this has been such an inevitable development but it has taken so long! With #WASM now included in standards and supported in pretty much every browser there is an opportunity to treat the browser as the target platform abstraction for high performance stuff like #games. And there is nothing the actual underlying OS can do to gatekeep that content without breaking the web! https://www.gamedeveloper.com/mobile/microsoft-launching-web-based-mobile-game-storefront-in-july
Without Nix, how do you set up complicated build/test environments on other systems? The sheer amount of sedimentary layers you need to do #WASM or #WebGPU stuff is astounding, and then you add the various utility Python libraries needed to glue together a test harness.
🎧 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/!
PostgreSQL in #WASM allows you to run a #PostgreQL instance in the browser, Node.js, or Bun. Finally a proper, dependency-less database server for your browser :) #linktuesday
In this guide, aimed at web developers who want to benefit from #WebAssembly, you'll learn how to make use of #Wasm to outsource CPU-intensive tasks with the help of a running example.
Hello World! Firefly Zero is an in-development handheld game console that runs #wasm and supports #BLE multiplayer. It is written by @orsinium in #Rust, runs on #ESP32, and will be fully open source (both software and hardware).
We already have a working desktop emulator and are getting a Rust and #golang SDK ready for alpha testing. Sounds fun? Stay tuned!
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.
> 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!?