Curious about #WebAssembly but don’t know where to start? Follow the fun journey explained at #openSUSE Conference of porting Little Piggy Tracker (a Game Boy-inspired audio app) to handhelds & the browser. #oSC25 #WASM https://youtu.be/pq-04MlLAnM?si=m4y_MdO-dkh7wV11
I have implemented an API for WASM modules for a game engine. I want to create tests for it to make sure that the API that the WASM scripts use are correctly implemented.
How could I build a test suite for this? Since I would have to compile the modules as well, I doubt just "cargo test" would be enough. Is there another testing tool that could be better for this?
Direct WASM→DOM access doesn't leave JavaScript behind - JS could use the same fast path! We could even build Fagnani's exact templating API as a reference implementation on top of it. But unlike a JS-only solution, the platform stays open for potentially superior approaches in ANY language. Rust might build something faster. Zig might build something smaller. That's the kind of competition through collaboration that drives innovation. Everybody wins wins wins. #compsci #webdev #wasm #javascript
Instead of standardizing one templating syntax (that'll be bikeshedded to death), give us the primitive: fast DOM access from any language. Let a thousand templating libraries bloom - in any language. Lower-level primitives enable more innovation than high-level APIs. That's the Unix philosophy. Simple, composable, powerful. Build the foundation right. #compsci #webdev #wasm #frontend #unix
The performance argument for native templating is weak - we're talking 2% gains, max. But remove the JS bridge for WASM? That's where real performance wins live. Fix the actual bottleneck. Every DOM call through JS is overhead we don't need. Direct access would unlock true native speeds for web UIs. Imagine game engines manipulating DOM at 60fps without JS overhead. #compsci #webdev #performance #wasm
Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. #compsci #webdev #wasm #webstandards
The #Kotlin team is opening a position to work on the #Wasm compiler ! https://kotl.in/wasm-apply
So happy to see the project that I have been in love with and contributing to for the last several years getting so much attention.
If you work with ESP32 or RPi Pico devices and want a development platform built with fault tolerance and concurrency at it’s heart that allows you to write sophisticated applications with very little code AtomVM might be just what you are looking for.
Introducing **Chakra** - a blazing fast in-browser WebAssembly runtime for builders.
```sh
chakra myfile.wasm
```
– Runs WASM in-browser with logs
– Supports Rust, TinyGo, C, Asc and Python
– One-line introspection & verify commands
Chakra is an open source project and we're building it *with the community*.
https://github.com/anistark/chakra
Read more: https://blog.anirudha.dev/chakra
Give us a shout-out or star the repo on github if you like the idea.
Why I use WebAssembly | nasso.dev
「 My favorite way to use WebAssembly is as a way to share code between platforms. Write the core logic of your application in Ru… a language that can easily compile to native code and WebAssembly . In this architecture, most of your code is shared between the “native” and the “web” variants of your app 」
Kotlin/Wasm (wasmJs variant) is going to be promoted to Beta! #kotlin #wasm https://blog.jetbrains.com/kotlin/2025/05/present-and-future-kotlin-for-web/
This boxer demo video of #wasm was amazing. And it's exactly what I had in mind when I asked here a few months back "what comes after containers?"
New #WasmAssembly podcast
episode is up: Enabling in-browser scientific computing with #Wasm: David Kircos of Quadratic.
https://www.youtube.com/watch?v=TTUaZXl0X4Y
https://wasmassembly.libsyn.com/enabling-in-browser-scientific-computing-with-wasm-david-kircos-of-quadratic
We discussed how Quadratic's spreadsheet uses #WebAssembly to enable scientific computing directly in the browser with tools like Pyodide, pandas, and numpy. The conversation also covers practical challenges such as bundling large-scale Wasm applications, exploring browser limitations, and Quadratic's integration of AI.
Good news for Webassembly fans: https://thenewstack.io/graalvm-finally-gets-java-for-webassembly/
BTW: Beneath the Waves
Manage your crew and your submarine, survive the onslaught of rocks, enemies, and mines, and collect some treasure chests!
Play in your browser:
https://aurel300.itch.io/btw
Made for LDJAM 57 in 72 hours.
New in LLVM 20.1.0, the #Wasm backend now supports the new stable Lime1 virtual CPU. Enable it with the -mcpu=lime1 flag!
Lime1 is a stable target that won't add features over time. Read more at:
https://github.com/WebAssembly/tool-conventions/blob/main/Lime.md#lime1