#webassembly is starting beta

2.28: news.cyb/dev.net/webassembly.org is starting beta:
Mozilla, Microsoft, Google, and Apple have teamed up
to make the web more efficient.

. web pages become animated and interactive
with programming by the javascript language;
the efficient way to distribute a program
is to compile the programming language
thereby translating it into machine instructions
that are executed by a virtual machine
(these instructions are called bytecode
because they convert common instructions
into bite-sized numbers in 0..255).
. but instead of sending bytecodes
the current web sends javascript language
that the browser then needs to translate.
. now that major browsers have webassembly
they can accept bytecode programs
and if there is a browser that doesn't read webassembly
the web page will send some javascript language
that converts bytecode into javascript language.
. but most people use the 4 major browsers
by Mozilla, Microsoft, Google, and Apple
so web pages that send out webassembly
should see a rapid speed-up in their execution
because they don't have to wait for
their javascript to translate to bytecode.

Luke Wagner @mozilla.com:
to: public-webassembly@w3.org
date: Tue, Feb 28, 2017 at 8:03 AM
subject: WebAssembly consensus and end of Browser Preview

WebAssembly CG members representing four browsers,
[Google]Chrome, [MS]Edge, [Moz]Firefox, and [Apple]WebKit,
have reached consensus that the design of the initial
(MVP [1][minimum viable product])
WebAssembly API and binary format
is complete to the extent that
no further design work is possible without
implementation experience and significant usage.
This marks the end of the Browser Preview
and signals that browsers can begin
shipping WebAssembly on-by-default.
From this point forward,
future features will be designed to ensure
backwards compatibility.

This consensus includes a JavaScript API [2]
and binary format [3]
accompanied by a reference interpreter [4].
You can test out WebAssembly today using the Emscripten toolchain
by following the developer’s guide [5]
and reading more on MDN[moz dev net][6].
The next steps will be to form a W3C Working Group,
to produce a specification for the initial version of WebAssembly,
and to continue iterating on future features [7]
in the current Community Group.
To get involved, you can join design discussions [8]
and contribute [9] to the the WebAssembly GitHub project.

Luke Wagner, Ben Titzer, Filip Pizlo, and Abhijith Chatra

P.S. We are also happy to announce the selection of
the official WebAssembly logo [10]!