ABI stands for Application Binary Interface (wiki page).

We can see an ABI as a contract between two binary applications, to assure that one binary is able to access certain native functions from the other binary.

Each time we compile a C or C++ application there is a set of system calls that the application will normally use, for example, to open a file, read its contents… or even opening a socket.

For doing that, the applications normally target the POSIX ABI to run these syscalls in Unix-like systems. There are different implementations following POSIX, such as libc, musl…

Read the article: https://medium.com/wasmer/webassembly-cloudabi-b573047fd0a9

A few days ago, I wanted to take Go WebAssembly out for a spin, but I wasn’t sure what to build. Maybe a game ? but I didn’t really want to build a game from scratch. So I remembered the Elevator Saga, a programming game by Magnus Wolffelt I stumbled upon a few years ago: The goal is to transport people up and down building floors by controlling elevators, writing the rules in Javascript. What if I modified it to accept WebAssembly flavoured Go instead of JS !

Read the article: https://medium.com/@didil/practice-your-go-webassembly-with-a-game-7195dabbfc44

The technology that most directly underpins webpiling is WebAssembly. The details are best explained on the official site, but for our purposes you can think of WebAssembly as being a kind of platform, like x86 or ARM, in that you can compile native libraries to be executed from this format. The output of this compilation process is a .wasm file, which can then be loaded and called from JavaScript in order to run natively-implemented functions in a browser. WebAssembly has a number of benefits, but the two that are most important for webpiling are (1) it’s a logical output format for native library implementations and (2) it runs very, very fast.

Read the article: https://medium.com/@babylonjs/marker-tracking-in-babylon-js-ce99490be1dd

We’ve been working steadily to get Wasmer to execute WebAssembly modules on the server-side as fast as possible.

TL;DR — We got 100x improvement on startup time on Wasmer 0.2.0

Before getting into details, it’s essential to understand how Wasmer works under the hood to see what could be improved.

Read the article: https://medium.com/wasmer/running-webassembly-100x-faster-️-a8237e9a372d

I was very happy then when I came across tinygo, compile down a web assembly module and come to found it it makes WAY less assumptions and has a very simple based comment based system for importing functions — something to my knowledge currently impossible in the mainline Go compiler.

tinygo takes advantage of LLVM and is able to reduce web assembly modules to a pretty extreme amount pretty well. What this enables me to do is write very minimal modules like this hello world:

Read the article: https://medium.com/@richardanaya/hyper-efficient-front-end-development-with-web-assembly-using-go-and-llvm-8e6a1ccdd2bc

If you didn’t know. There’s a secret in the compiler community. LLVM can compile to web assembly. LLVM is a tool used by languages like Clang and Rust as a universial intermediate representation(IR) that can be compiled down to machine code output. Web assembly is one of those outputs.

Read the article: https://medium.com/@richardanaya/write-web-assembly-with-llvm-fbee788b2817

In the early days of programming, hackers around the world participated in what was referred to as the “demo scene.” It still thrives today but I am mostly familiar with the “old school” phase that mainly involved using hardware hacks and other tricks to push personal computers to their limits. We could “trick” the video processor into drawing in areas it wasn’t supposed to and with clever timing produce more colors or sprites than were “allowed.” It was a fun time and I learned a lot.

Read the article: https://blog.jeremylikness.com/gopher-meet-plasma-a-webassembly-experiment-4048e4d3b8d7

Software systems have “bugs”that lead to injury and death!

• Generally, when bugs mean human casualties or significant
  financial loss.
• Critical infrastructure from power plants to TLS implementations
  (Microsoft Research, F∗).
• Airplanes, weapon systems.
• And yes, sometimes even operating systems (Data 61, seL4
  Linux).

The PDF https://lorenz.leutgeb.xyz/paper/cakeml-wasm-viennajs-beam.pdf

WebAssembly elicits hopes about everything from importing new functionalities into browser based applications, to the potential (and in some circles hoped for) death of JavaScript. This talk is for folks who are curious about the real world applications and limitations of WebAssembly as it exists today. We'll follow along the journey of some intrepid developers as they integrate the popular FFmpeg multimedia framework into a React application for the purposes of editing video client side.

Youtube Video

Doom 3 running in the browser using Emscripten / WebAssembly

Try the game: http://continuation-labs.com/d3wasm/