Can chrome native client do something that javascript can't do?

Question

I got confused about the usefulness of my own client in Chrome, except that I used the language of your choice and worked faster.

Is it possible to do something in your own client that you cannot do in javascript? In everything, I mean functionality, not a better / faster way to do the same. For example, javascript cannot open a UDP socket, but can use its own client.

Answer 1

On the first line, you will find two points where the Native Client provides the utility. NaCl is good for C / C ++ / assembly encoders to bring an application written in their language of choice on the Internet, and NaCl helps applications run faster / with better performance / more efficiently (also with less battery usage). The native client also provides multi-threaded applications, allowing you to program models (and the performance that come with the threads) to run from the Internet (aka not with web workers).

The Sockets API is available for all chrome-plated applications. The difference is that the API makes sockets directly in the NaCl application, which is faster and has the advantage of transferring existing native applications to the browser without changes. There are also many other APIs such as game controllers, hardware decoding (coming soon), and Fullscreen / Mouselock. Find the full list of Pepper APIs that provide NaCl features here: https://developer.chrome.com/native-client/pepper_stable/c/index#pepper-stable-c-index .

For a portable native client, the most notable features are the ability to use streams and portable built-in functions (SIMD). It’s possible that writing the main logic that can run the cross platform (for example, the C / C ++ “model”, which can interact with different views on different platforms) is not a strict possibility, but it is useful to use NaCl, especially for developers who also use the Objective C / Android NDK to create their own mobile versions of their application.