Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even if that's true (and I share the sibling's skepticism), vendor A's incompetence and poor product quality is not meaningfully described as "lock-in" to vendor B - especially so when there's a readily available vendor C (Firefox) that doesn't share these ills.


Firefox doesn't support NacCl, Mozilla has show no intention of integrating it and they even criticized the technology.


Yeah but that's because Mozilla loves javascript and NaCl provides a working alternative.


How is NaCl not just "Google's version of ActiveX"


Here's an overview:

http://static.googleusercontent.com/media/research.google.co...


NaCl runs in a sandbox


it's secure and open source.


Nothing is "secure".


It's more secure than JavaScript, which is a start. Dropping the need for just-in-time compilation while gaining performance is nice.


When has JavaScript itself (and not the APIs, unless it's a JS-specific problem) last enabled an exploit in a major browser? I can't remember it.

Meanwhile, here's a NaCl sandbox escape exploit from March: https://www.exploit-db.com/exploits/36311/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: