Building Graphical Applications with Wasmer and WASI


WebAssembly modules have no built in I/O capabilities, they cannot access the filesystem, open sockets or render to the screen. In order to do anything useful, a wasm module must communicate with, and direct its host (i.e. the browser for web embedding) to perform I/O on its behalf. The wasmer team are looking to drive WebAssembly adoption, and want to make I/O easier - which is why they have created I/O devices, a ‘standard’ interface for wasm modules which allows them to render to the screen.

WebAssembly: Key to a high-performance web, or ideal for malware?


There has been a lot of negative press around WebAssembly since a study reported that the majority of websites they analysed used the technology for malicious purposes. This article is a brief interview with Andreas Rossberg, one of the creators of WebAssembly, where he addresses these concerns.

Announcing Experimental Mobile Blazor Bindings


Yet more Blazor news! This blog post announces a new experimental project to enable native mobile app development with Blazor. Microsoft already has a framework for creating cross-platform native mobile application using Xamarin. This experimental project combines the two.

How to Use WebAssembly to Transform Images Without a Server


A brief but very practical and useful blog post, using a WebAssembly build of ImageMagick, avoiding the need to send images to a server in order to apply transformations.

And Finally …

A Kubernetes Kubelet written in Rust to run WebAssembly applications on wasm-based runtimes instead of a container runtime. 🤯🤯🤯