Recently I attended a webinar for a new web technology from Microsoft called Blazor. In summary, Blazor is a technology that allows developers to create web applications using C#, HTML, and CSS. Furthermore, it allows the C# code to run on any modern browser, including mobile browsers without the need for plugins or any special frameworks or configuration. This technology insight is certainly intriguing, but I will talk more about Blazor in a later post.
For this article, I want to talk about a key piece of technology called WebAssembly, which is at the heart of Blazor. WebAssembly (or Wasm) is an open standard that was finalized in 2017. In the following months all major browsers implemented support for WebAssembly across all supported operating systems and platforms.
While there are some examples where WebAssembly has been used, the best is yet to come. The WebAssembly Core specification became a “Candidate Recommendation” with the W3C standards body on July 18th, 2019, and less then three months later, on October 1st, 2019, it became a “Proposed Recommendation.” This recommendation is the final maturity level before becoming a “WC3 Recommendation”. As the standard has become more mature 3rd party technology companies such as Microsoft have been hard at work laying the groundwork to let developers better use WebAssemblies.