Native Client: A Technology for Running Native Code on the Web

Re:Native Client: A Technology for Running Native Code on th... by tptacek on Tuesday December 09, 2008 @04:21PM (#391784)

When I said "that", I think I meant, "all of it". ;)

ActiveX vs. NaCL is a false comparison, obviously. You can't do worse than ActiveX, and nobody promotes it.

I don't understand your last paragraph; setup time isn't going to be based on the X86 ISA, but rather the time it takes to fork a process, monitor it in a debugger, set up the system call interface, and then do whatever UI goop NaCL wants to do to give native code a window context. It could be faster than the Java applet plugin. It could be slower. And applets could get faster.

[ Parent | on HN ]

Re:Native Client: A Technology for Running Native Code on th... by stcredzero on Wednesday December 10, 2008 @04:42PM (#393520)

So your "that" referent consisted of two hypothetical parts and a 3rd statement that you agree is trivially true.

I meant setup from a user standpoint. I suspect that once such sandbox software was stable, updates would be less frequent than updates to the Java plugin. You meant setup time in terms of getting code JITed and actual execution.

[ Parent | on HN ]