Universal Binaries Using WASM

Re:Universal Binaries Using WASM by titanix2 on Tuesday February 26, 2019 @04:09AM (#19252963)

> Build Once, Run Anywhere.

Build once, run where the runtime in available.

[ Parent | on HN ]

Re:Universal Binaries Using WASM by krapp on Tuesday February 26, 2019 @05:24AM (#19253232)

>Build once, run where the runtime in available.

To be fair, that's true of everything. We only take for granted that some runtimes are more common than others.

The only reason the web is a "universal" runtime is that browser vendors ship to every conceivable platform and more or less agree on standards.

[ Parent | on HN ]

Re:Universal Binaries Using WASM by ubercow13 on Tuesday February 26, 2019 @04:12AM (#19252969)

Kind of like Java

[ Parent | on HN ]

Re:Universal Binaries Using WASM by thefounder on Tuesday February 26, 2019 @05:06AM (#19253166)

Java is slow(to start) and memory hungry. That's why it failed so badly. Compare that with JavaScript/Electron.

[ Parent | on HN ]

Re:Universal Binaries Using WASM by krapp on Tuesday February 26, 2019 @05:15AM (#19253194)

>Compare that with JavaScript/Electron.

Electron is heavier and even more memory hungry.

[ Parent | on HN ]

Re:Universal Binaries Using WASM by StavrosK on Tuesday February 26, 2019 @05:49AM (#19253312)

I don't know what the GP was thinking. Hopefully exactly that.

[ Parent | on HN ]

Re:Universal Binaries Using WASM by fetbaffe on Tuesday February 26, 2019 @07:18AM (#19253653)

Build once, eat memory anywhere.

[ Parent | on HN ]

Re:Universal Binaries Using WASM by protomyth on Tuesday February 26, 2019 @05:10AM (#19253175)

Please explain how Java “failed so badly”?

[ Parent | on HN ]

Re:Universal Binaries Using WASM by thefounder on Tuesday February 26, 2019 @05:14AM (#19253185)

It failed so badly "on the web/in browser".

[ Parent | on HN ]

Re:Universal Binaries Using WASM by sagartewari01 on Tuesday February 26, 2019 @04:25AM (#19253016)

*Build once, run almost Anywhere

[ Parent | on HN ]