News for hackers. Stuff that matters.

A comment on Making WebAssembly better for Rust and for all languages. Parent comment

Re:Making WebAssembly better for Rust and for all languages by AgentME on Wednesday March 14, 2018 @02:03PM (#16586876)
While some of those were open standards, most/all of those only ever had a single implementation each. JVM's startup time is painful, and its sandboxing abilities have been frequently broken. Wasn't Microsoft p-code interpreted, or are you referring to something else? NaCL was still architecture-specific until PNaCL. PNaCL is pretty comparable to WebAssembly besides that PNaCL was driven by Google alone, and WebAssembly was worked on by many players after it evolved from asm.js.
[ Parent | on HN ]
Re:Making WebAssembly better for Rust and for all languages by seanmcdirmid on Wednesday March 14, 2018 @05:01PM (#16588254)
> most/all of those only ever had a single implementation each.

At its peak, there were many different vendors delivering JVM implementations. How we forget Kaffe, even.

[ Parent | on HN ]
Re:Making WebAssembly better for Rust and for all languages by pjmlp on Wednesday March 14, 2018 @06:29PM (#16588917)
There are still quite a few JVM implementations still, they just tend to be specialized in embedded, military or factory automation systems.
[ Parent | on HN ]