native-messaging-cpp VS requestNativeScripts

Working C++ version: https://github.com/guest271314/native-messaging-cpp/blob/main/nm_cpp.cpp

C++ Native Messaging host https://github.com/guest271314/native-messaging-cpp does not have that problem.

Technically you can launch and control the Qt and C++ (and any other programming language) applications from the browser, pass input as stdin and get stdout from the native application using various means, including Native Messaging https://github.com/guest271314/native-messaging-cpp.

That is already possible using just window.open() with a local server or WebRTC, or Web Bluetooth, or WebTransport, or Fetch, e.g., without using extension code https://github.com/guest271314/requestNativeScripts/blob/master/Explainer.md, and with extension code using Native Messaging https://github.com/guest271314/sw-transfer-stream, https://github.com/guest271314/offscreen-webrtc.

Technically you can use a variety of means to execute arbitrary shell scripts. One approach is to use inotifywait to check for file changes, which can be written to local filesystem using File API and where implemented File System Access API, for an overview of this particular approach see https://github.com/guest271314/requestNativeScripts/blob/master/Explainer.md, for implementation see https://github.com/guest271314/captureSystemAudio#usage, where I use the process to execute PulseAudio's parec to capture system audio and stream the raw PCM to the browser in real-time by opening and closing local files.