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!?
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:
This is the best job I've done conveying why I'm so enthusiastic about #wasm – or at least, the most succinct job I've done! We walk from the 1960's right up to the present day and, as a bonus, uh
Drumming up some excitement 🥁… I just recorded the first episode of a new podcast series that I'm hosting: the #WasmAssembly, your monthly podcast gathering of people to geek out about all things #WebAssembly.
My first guest was no other than #Wasm OG @kripken, whom you may associate with projects like #Emscripten and, you know, WebAssembly, the language. The episode should go up mid April, watch this space!
Yes. It's WasmAssembly, a name smarter than hairdresser 💇 names à la United Hairlines.
This talk by @esoterra introduces the idea of #Wasm "component-native" tooling, using Claw, a language built this way from the start.
It's obviously valuable to port existing language toolchains to Wasm. As we think about Wasm's future, it's also interesting to have component-native toolchains in the mix, because they have greater flexibility to take unconventional approaches, and find new creative ways of solving problems.