The point, in my estimation, would be to have all of the Javascript libraries you have accessible in node (which you use already on other projects, and are very

The point, in my estimation, would be to have all of the Javascript libraries you have accessible in node (which you use already on other projects, and are very familiar with) accessible while also having access to a full desktop GUI in that environment. This is a reasonable alternative to Electron, without requiring you to have another copy of Chromium on your machine for every Javascript-based desktop application you write. I suspect it will perform much better than Electron also, assuming the author has done a decent job integrating Qt's API with node. All of that being said, I have not tried Node-GUI, so I don't know how well it works. EDIT: I have also not looked at QT's built-in Javascript support in a long time, and was not aware that later versions support ES6. I have never written a Qt app using javascript, I've only used C++, and a small amount of python. It would be interesting to explore the implications of having the node ecosystem available to a Qt app, and how that compares to the built-in Javascript support alone.