@admin Go is everwhere now.

@admin I like this open source project.

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

阅读全文：https://mp.weixin.qq.com/s/dJN3UzQIsQWQdni_6l8h3Q

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.

GitHub: https://github.com/perlin-network/life
Tutorials: https://medium.com/perlin-network/life-a-secure-blazing-fast-cross-platform-webassembly-vm-in-go-ea3b31fa6e09

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.

Read the full article: https://medium.com/@shesh.soft/blazor-full-stack-web-development-with-c-and-webassembly-ac0a75515033

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.

Read the full article: https://hackernoon.com/writing-a-frontend-web-framework-with-webassembly-and-go-ff84cd1346fe

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.

Read the full article: https://medium.com/@amarabha/the-history-of-web-has-seen-a-few-major-events-in-the-past-three-decades-2a96246b8b54

OpenCC 很好，但遗憾的是我们必须开个服务才能使用。而我先前一直希望能在浏览器上直接运行，对页面的文本直接进行转换。

而后发现tesseract.js是使用 Emscripten 编译而成，对 wasm 相关技术的成熟度感到意外。于是便有了编译wasm版本的OpenCC的想法，同时也是对Emscripten进行一番探索。

这个项目对 OpenCC 进行了添加修改修改，并利用Emscripten进行编译，在 OpenCC 进行中文简繁体转换的能力上具有以下特性：

可在浏览器环境中直接运行。
在 node，eletron 中运行不需要再进行 addon 编译，避免复杂的 addon 部署工作。理论上应该也可以在 React Native 和 Web Worker 中运行(未经测试)。
分离了字典数据的加载和文本转换功能，在浏览器中只加载必要的字典数据，并允许自定义数据加载方式，方便从 CDN 上加载数据。

Read the full article: https://medium.com/@oyyd/用emscripten编译wasm版本的-opencc-在浏览器上进行简繁体转换-8ddeb8e0877d

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.

Read the full article: https://medium.com/@robert.balicki_2494/smithy-progress-update-how-i-decreased-webassembly-bundle-size-by-90-e7fe194b2f58

I become curious of WebAssembly standard when Ruslan Plakhuta mentioned that topic. He pointed out an idea of running full blockchain node in a browser via WebAssembly.

Attending a hackathon today, I spent the whole day thinking about it and trying to build existing implementations of Ethereum and Bitcoin to WebAssembly.

I’ve tried a number of option and implementations, but I failed. There are lots of packages which can’t be built to WebAssembly yet, but it might be soon fixed.

My research led me to thinking of what this idea may mean for distributed networks and for users.

Read the full article: https://medium.com/@sergiibomko/full-blockchain-node-in-a-browser-via-webassembly-768b7af6a80b