Why WebAssembly is innovative even outside the browser

1

Uno Platform

#Development Tools #Rapid Application Development #Cross-Platform Development 62 social mentions

2

CheerpX for Flash

They did not fail, politics killed them, the same politics that pushed for WebAssembly, but thanks to the WebAssembly pandora box, they couldn't be more healthy. https://leaningtech.com/cheerpj https://leaningtech.com/cheerpx-for-flash Enjoy.

#Online Services #Game Engine #Audio Player 12 social mentions

3

CheerpJ

They did not fail, politics killed them, the same politics that pushed for WebAssembly, but thanks to the WebAssembly pandora box, they couldn't be more healthy. https://leaningtech.com/cheerpj https://leaningtech.com/cheerpx-for-flash Enjoy.

#Online Services #Cloud Storage #Software Development 13 social mentions

4

Hacker News Search

Yes, WA has a defined security scope: it's right between the host and the WA program, and if you choose to sidestep it by eval-ing the output of a potentially malicious WA program, or simply handing it secrets, <i>obviously</i> you can get poor outcomes. No, WA has not solved the halting problem and fixed all bugs in sandboxed programs. Yes, it's important for people developing WA-based systems to acknowledge the above limitations. You've been brandying about this paper for the last year as if it means something that it doesn't [1-12]. Every time someone actually reads it they come to the same conclusion that this paper says nothing about the WA-host memory barrier -- and "everyone" includes the authors themselves [13]. And every time you respond by moving the goal posts with "but but WA isn't magic security pixie dust that solves all security problems". If I sound annoyed it's because I've been pushing back on your FUD with nary a direct response that acknowledges these limitations to your narrative and I <i>am</i> annoyed. Also, it's been a year now, where are all these papers that break WA that you keep promising? Are you privy to WA-host memory barrier breaking results that have yet to be published (and aren't just repackaged CPU vulnerabilities)? I'm open to evaluating the claim of such a break being found in the future, but there's no evidence for it yet. [1-12]: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=pjmlp%20Everything%20Old%20Is%20New%20Again%3A%20Binary%20Security%20of%20WebAssembly&sort=byPopularity&type=comment [13]: https://news.ycombinator.com/item?id=24223979.

#Search Engine #Web Search #Internet Search 1903 social mentions