This is a good start to the year, some crystal-ball gazing. WebAssembly has undergone quite a transformation over the past few years, from being a browser-based technology that was effectively a better replacement for the tired old plugin system (e.g. Flash, Applets, Silverlight), to being a versatile runtime used across an ever-growing set of use-cases (serverless, edge, plug-in, blockchain). Considering this transformation, this blog posts look at what might be just around the next corner.
I’ll revisit this prediction when running the State of WebAssembly survey in 2023.
WebAssembly was originally created through collaboration between Mozilla, Apple, Microsoft and Google. Since then, various other large and influential organisations have demonstarted commitmet to the technology. This post outlines why Red Hat are involved and investing in this technology, and some of the areas where they contribute.
This is an interesting post … in the early days of WebAssembly you often heard people asking “how does this differ from the JVM?”. The Java Virtual Runtime (JVM) is a platform-agnostic virtual machien that was intended to bring the Java language to the whole range of computing platforms, including the web (Java Applets). On the surface of it, there is a lot in common between wasm and the JVM, and the question is a fair challenge. It’s a question I tackled on StackOverflow a while back.
This fantastic blog post does far more justice to the question than my brief response on StackOverflow.
An online version of the vim editor, using WebAssembly, with file storage via IndexedDB, because … why not?!
Docker recently introduced first-class support for WebAssembly, allowing you to bundle up wasm files in docker containers. This brief tutorial takes you through the steps required, allowing you to try this out for yourself.