The Bytecode Alliance: Building a secure, composable future for WebAssembly

Re:The Bytecode Alliance: Building a secure, composable futu... by danielearwicker on Tuesday November 12, 2019 @05:30PM (#21518916)

That future possibiilty reminds me of https://en.wikipedia.org/wiki/Singularity_(operating_system) - where process/address-space isolation was replaced with fine-grained static verification of high-level code (presumably not the first experiment in this area).

[ Parent | on HN ]

Re:The Bytecode Alliance: Building a secure, composable futu... by tschneidereit on Tuesday November 12, 2019 @05:39PM (#21519001)

Indeed: that and many other things are prior art in this space. And there is a lot of prior art for what we're working on—this is not meant as an academic research project! :)

[ Parent | on HN ]

Re:The Bytecode Alliance: Building a secure, composable futu... by lambda on Tuesday November 12, 2019 @05:56PM (#21519154)

Yes, one of the answers I want to give any time someone asks "why will WASM succeed when the JVM didn't" is that there is 25 years more experience and research to draw upon.

[ Parent | on HN ]

Re:The Bytecode Alliance: Building a secure, composable futu... by pjmlp on Wednesday November 13, 2019 @02:09AM (#21521755)

And yet bounds checking access validation was left out of the design, something that most of previous research projects took care to taint as unsafe packages when present.

[ Parent | on HN ]