As a side note, why is it that I have to sign in to Google in order to be able to see this? Is registration /really/ necessary for Google Groups?
You are right. It's very annoying. It's even worse than having links that are behind a paywall, because at least a paywall usually indicates that funds are flowing to the person (reporter, etc.) who created the content. The google groups situation is quite different, and quite annoying. I never login to google groups to see something listed on HN. I wonder whether HN could provide an option to let readers avoid such…
Traditional C "Hello World" working in NaCl
21–28 of 28 posts
Re: Traditional C "Hello World" working in NaCl
#22Re: Traditional C "Hello World" working in NaCl
#23[deleted]
Re: Traditional C "Hello World" working in NaCl
#24Earlier quoted context omitted.
Read the paper. It's a subset of x86 that retains better security properties for distribution. http://src.chromium.org/viewvc/native_client/data/docs_tarba...
Very interesting. The security features are very thorough. Of course, until someone finds a vulnerability, or a way through the validator, or an exploit on an abstracted function. Still, it's a good security model
Re: Traditional C "Hello World" working in NaCl
#25I'm a fan of fast native code, but I worry that this promotes sneaky code in the background once it gets widely adopted. With javascript we basically have open-source web apps. I often skim through js source to learn new tricks - and obfuscation doesn't really stop me (apart from google's java-translated js) . With compiled NaCl I probably wouldn't be able to find out a lot. I'm not talking about "stealing user data"…
Re: Traditional C "Hello World" working in NaCl
#26I'm a fan of fast native code, but I worry that this promotes sneaky code in the background once it gets widely adopted. With javascript we basically have open-source web apps. I often skim through js source to learn new tricks - and obfuscation doesn't really stop me (apart from google's java-translated js) . With compiled NaCl I probably wouldn't be able to find out a lot. I'm not talking about "stealing user data"…
I would assume the NaCl apps won't run by default. Maybe you get that "click to activate" thing that firefox is implementing for Flash and Java
Re: Traditional C "Hello World" working in NaCl
#27I'm a fan of fast native code, but I worry that this promotes sneaky code in the background once it gets widely adopted. With javascript we basically have open-source web apps. I often skim through js source to learn new tricks - and obfuscation doesn't really stop me (apart from google's java-translated js) . With compiled NaCl I probably wouldn't be able to find out a lot. I'm not talking about "stealing user data"…
I would assume the NaCl apps won't run by default. Maybe you get that "click to activate" thing that firefox is implementing for Flash and Java
[1] https://developers.google.com/native-client/community/securi... [2] m.yahoo.com/w/legobpengine/news/google-bringing-high-end-gaming-chrome-via-native-054102268.html
Re: Traditional C "Hello World" working in NaCl
#28Earlier quoted context omitted.
Read the paper. It's a subset of x86 that retains better security properties for distribution. http://src.chromium.org/viewvc/native_client/data/docs_tarba...
At best that takes care of the security issues. The other thing that makes ActiveX an affront to the web is the platform lock-in. x86 code is not suitable as a web standard. (And neither is the LLVM intermediate representation, for reasons expounded on in e.g. http://permalink.gmane.org/gmane.comp.compilers.llvm.devel/4... )
I see Native Client as being an extremely nice solution to several issues at once:
- runs fast
- the programs don't need an installer
- I can trust a Native Client program (that's me personally)