WCG（WebAssembly Community Group）提名主席JF在WebAssembly的官方Github仓库中发布一则消息，称将会于2015年6月17日将Wasm技术当前阶段的发展计划公之于众。WCG的核心成员主要由一群来自苹果、谷歌、微软及Mozilla等互联网巨头公司的顶尖工程师组成，这些工程师会定期对Wasm技术的标准进行调研和讨论。所有与Wasm技术相关的标准草案，以及未来的发展路线都由他们共同制定。

Life is a secure, blazing-fast, cross-platform, and modular WebAssembly VM written in Go, built for running computationally heavy code on practically any device you can imagine.

At Perlin, we developed Life to be:

Fast — Life uses a wide range of optimization techniques and is far more performant than quite a number of different WebAssembly implementations we’ve tested (such as go-interpreter/wagon and paritytech/wasmi).

Correct — Life was built from the WebAssembly reference manual, and thus passes most of the official test suite (66/72 passed, none of the failures are related to the execution semantics).

Secure — User code executed on Life is fully sandboxed. A WebAssembly module’s access to resources (instruction cycles, memory usage) may easily be controlled to the very finest detail.

Pure — Life does not rely on any native dependencies, and may easily be cross-compiled for running WebAssembly modules on practically any platform (Windows/Linux/Mac/Android/iOS/etc).

Practical — Life makes full use of the minimal nature of WebAssembly to write code once and run anywhere. Every single part of Life may be modularized and used for whatever interests developers may have in mind.

With that being said, we seek for Life to be a tool that any project may easily integrate into their applications for the sake of running WebAssembly code anywhere with ease.

Blazor (Browser + Razor) is an experimental .NET web framework using C# and HTML. It runs in the browser on a real .NET runtime (Mono) implemented in WebAssembly that executes normal .NET assemblies. It is based on existing web technologies like HTML and CSS, but you use C# and Razor syntax instead of JavaScript to build composable web UI. It gives you all the benefits of a rich, modern single-page application (SPA) platform while letting you use .NET end-to-end, including sharing code across server and client.

avaScript Frontend frameworks have undoubtedly helped to push the boundaries of what was previously possible in the context of a browser. Ever more complex applications have come out built on top of the likes of React, Angular and VueJS to name but a few and there’s the well known joke about how a new frontend framework seems to come out every day.

However, this pace of development is exceptionally good news for developers around the world. With each new framework, we discover better ways of handling state, or rendering efficiently with things like the shadow DOM.

The latest trend however, seems to be moving towards writing these frameworks in languages other than JavaScript and compiling them into WebAssembly. We’re starting to see major improvements in the way that JavaScript and WebAssembly communicates thanks to the likes of Lin Clark and we’ll undoubtedly see more major improvements as WebAssembly starts to become more prominent in our lives.

The history of web has seen a few major events in the past three decades. One of them was the launch of JavaScript 22 years ago on December 4, 1995. Since then JavaScript has slowly evolved to become the de-facto standard of front-end web development. The present day web is much more dynamic and data intensive. Heavy graphics based games and applications require a much more robust browser. That is why developers are going crazy over the concept of WebAssembly. Is it here to replace JavaScript? Or is it like any other hype that will fade away with time? The answer is neither of the two.

In a previous post, I introduced Smithy, a web development framework written in Rust that compiles to WebAssembly. In the mean time, there has been substantial progress, and Smithy is on the verge of being ready for alpha use!

My goal for Smithy is to enable you to use idiomatic Rust to write front-end code.