[e1ven]

Regardless of any technical merit or reasoning, one big advantage is that Javascript/WASM is not controlled by any one large company or organization.

This provides substantial differentiation from .Net/Java/Flash/etc.

That said, this advantage risks diminishing if Google's influence continues to grow.

[dmitriid]

> Javascript/WASM is not controlled by any one large company or organization

It’s disproportionally affected by Google.

[vorpalhex]

Given that Mozilla has done tons of WASM work, and that one of the earliest implementors was Rust, comparing WASM to Oracle's iron fist over the JVM doesn't seem to jive with reality...

[TimTheTinker]

> Oracle's iron fist over the JVM

Still doesn't compare to the Sun God and his silicon fist.

(With apologies to Steve Yegge.)

[blacksmith_tb]

Jive != jibe[1] (but agreed about Moz's role in WASM)

1: https://www.merriam-webster.com/words-at-play/jive-jibe-gibe

[dmitriid]

I didn’t say Mozilla, I said Google.

I didn’t say iron fist, I said disproportionately affected.

[BubRoss]

And it isn't true, because Mozilla is very involved, and every browser engine will have to get on board.

[dmitriid]

First and foremost Chrome has to get onboard. Hardly anyone cares if Mozilla implements anything.

A few people will care if Safari does.

Edge is out if the picture and is being replaced by Chromium (aka Chrome).

On WebAssembly specifically. Here’s WebAssembly working group: https://www.w3.org/2000/09/dbwg/details?group=101196&order=o...

I count 18 people from Google, and only one from Mozilla. The second largest representation is from Microsoft (8 people), but their input is now Chrome/Chromium input.

[ashleyn]

Exactly, did we ever move beyond monoliths dominating a standard or did they simply evolve to calling something "open" while exerting disproportionate influence on the standards body?