native-messaging-quickjs VS native-messaging-c

QuickJS https://github.com/guest271314/native-messaging-quickjs (after strip the executable is less than 1MB; the last time I checked node executable is well over 80MB) to run ImageMagick and pipe the result to local file system, remote end-point, or to the browser as a stream.

Dynamically set arbitrary Web pages as "externally_connectable" and forward messages from the Web page to Native Messaging host the forward messages from Native Messagin host back to arbitrary Web page https://github.com/guest271314/native-messaging-quickjs/tree/dynamic-externally-connectable

I can ship qjs in a browser extension with no undue constraint on storage, and run qjs from the browser from any Web site https://github.com/guest271314/native-messaging-quickjs/tree/dynamic-externally-connectable. That is a different story for node and deno, when we really analyze the built-ins we use, do not amount to all of the built-ins, however, there is no way that I am aware of to reduce the size of V8 engine; even d8 is what, 20MB, and not simple to extend to actually use stdin, stdout.

Working JavaScript (QuickJS) version: https://github.com/guest271314/native-messaging-quickjs/blob/main/nm_qjs.js

A QuickJS Native Messaging host that echoes input https://github.com/guest271314/native-messaaging-quickjs from client. Have fun.

Ultimately what I am trying to do is test the simplicity and efficiency of using a local server versus using Native Messaging, which I have working https://github.com/guest271314/native-messaging-c, https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.c.

Yes. I use Native Messaging to do that as well https://github.com/guest271314/native-messaging-c. Far less overhead cf. HTTP. Nonetheless I am trying to improve the implementation.

I would suggest sending valid JSON. Here is a Native Messaging host written in C which sends JSON to the client https://github.com/guest271314/native-messaging-c.

I will probably adjust the variable names in your code and publish here https://github.com/guest271314/native-messaging-c including link to your answer.

For the C version which is now just an echo of input https://github.com/guest271314/native-messaging-c/tree/main repeat steps 1.-6. Instead of pinning the icon to address bar, navigate back to chrome://extensions, click "service worker" which will open a DevTools window for the background MV3 ServiceWorker context, then run this code in the console