This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to "wasm", hopefully LDC and/or SDC could glue to this.

https://www.w3.org/community/webassembly/

https://github.com/WebAssembly

In particular, see https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md https://github.com/WebAssembly/design/blob/master/FAQ.md and https://github.com/WebAssembly/design/blob/master/MVP.md

On 18/06/2015 8:05 p.m., John Colvin wrote:
> This appears to have involvement from all major browser vendors, which
> provides hope it might actually catch on properly. An llvm backend will
> be created which will compile to "wasm", hopefully LDC and/or SDC could
> glue to this.
>
> https://www.w3.org/community/webassembly/
>
> https://github.com/WebAssembly
>
> In particular, see
> https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md
> https://github.com/WebAssembly/design/blob/master/FAQ.md and
> https://github.com/WebAssembly/design/blob/master/MVP.md

I saw it.
I'm waiting for some sort of spec or example toolchain.

Once we have that I'd be willing to work on bindings and tutorial for it.
I honestly see no reason to not add it as a targetType to dub. Would be pretty awesome to write both client side and server in D using it.

On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote:
> This appears to have involvement from all major browser vendors, which provides hope it might actually catch on properly. An llvm backend will be created which will compile to "wasm", hopefully LDC and/or SDC could glue to this.
>
> https://www.w3.org/community/webassembly/
>
> https://github.com/WebAssembly
>
> In particular, see https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md https://github.com/WebAssembly/design/blob/master/FAQ.md and https://github.com/WebAssembly/design/blob/master/MVP.md

Sigh, another attempt to sneak native code into the browser, rather than just admitting that the web stack blows.  I have to admit I was hopeful about NaCl, but it appears to have gone nowhere.

Why can't they just admit that the core architecture of the web is horrific, ie an antiquated document format based on some shitty 50-year old IBM markup language (https://en.wikipedia.org/?title=Standard_Generalized_Markup_Language), a programming runtime that was cranked out in 10 days in the middle of the browser wars and certainly shows it (https://en.wikipedia.org/wiki/Brendan_Eich#Netscape_and_JavaScript), and a stylesheet language hacked on top to eliminate some redundancy, _by adding yet another language_?!

As Tim Bray, of all people, wrote a couple years ago, this Titanic is losing to native mobile apps and it's only a matter of time till it's sunk:

https://www.tbray.org/ongoing/When/201x/2014/01/01/Software-in-2014

But what do they do instead of starting anew?  Keep rearranging the deck chairs on the Titanic.  "Maybe if we fly in and install a new engine, it won't sink?!"

endRant();

On Thursday, 18 June 2015 at 10:36:16 UTC, Joakim wrote:
> On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote:
>> [...]
>
> Sigh, another attempt to sneak native code into the browser, rather than just admitting that the web stack blows.  I have to admit I was hopeful about NaCl, but it appears to have gone nowhere.
>
> [...]

afaik this is backed heavily by pnacl authors

On Thursday, 18 June 2015 at 08:07:47 UTC, Rikki Cattermole wrote:

> Would be pretty awesome to write both client side and server in D using it.

I just found about WebAssembly while having lunch and that was exactly my thought.

On Thu, 18 Jun 2015 08:05:46 +0000, John Colvin wrote:

> This appears to have involvement from all major browser vendors,
> which provides hope it might actually catch on properly. An llvm backend
> will be created which will compile to "wasm", hopefully LDC and/or SDC
> could glue to this.
> 
> https://www.w3.org/community/webassembly/
> 
> https://github.com/WebAssembly
> 
> In particular, see https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md https://github.com/WebAssembly/design/blob/master/FAQ.md and https://github.com/WebAssembly/design/blob/master/MVP.md

they will never stop, won't they? "modern web: building piles of shit on top of piles of shit". (sigh)

On Thursday, 18 June 2015 at 11:00:37 UTC, ketmar wrote:
> they will never stop, won't they? "modern web: building piles of shit on top of piles of shit". (sigh)

Indeed.

«Even before browsers ship native support for WebAssembly, developers can ship applications on the Web using a polyfill which converts WebAssembly to JavaScript. »

Basically binary asm.js... What are they thinking?

And whyyyyyyy are they calling a binary format "assembly"?

On 6/18/15 10:41 AM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= <ola.fosheim.grostad+dlang@gmail.com>" wrote:
> And whyyyyyyy are they calling a binary format "assembly"?

Because it sounds faster, of course :)

On Thursday, 18 June 2015 at 17:41:44 UTC, Ola Fosheim Grøstad wrote:
> On Thursday, 18 June 2015 at 11:00:37 UTC, ketmar wrote:
>> they will never stop, won't they? "modern web: building piles of shit on top of piles of shit". (sigh)
>
> Indeed.
>
> «Even before browsers ship native support for WebAssembly, developers can ship applications on the Web using a polyfill which converts WebAssembly to JavaScript. »
>
> Basically binary asm.js... What are they thinking?
>
> And whyyyyyyy are they calling a binary format "assembly"?

wow

I didn't even read it, I thought it was going to be like a standardized pnacl from the naming.

this is ridiculous, you could release /dev/null for the web and it would generate unlimited hype.

On Thursday, 18 June 2015 at 08:05:48 UTC, John Colvin wrote:
> ...

I hope this don't turn into this: https://imgs.xkcd.com/comics/standards.png

Matheus.