Hacker News Reader

No no no. Obviously you should compile your existing Qt application to webassembly, put that in a QTWebView and have that be your application.

And we will run this all on nebulet, an OS being written for a pure web assembly user space [0].

But seriously, you say this like it's horrible, but a bytecode/VM that allows us to abstract over code that runs in a browser/code that runs a native app/code that runs in a device driver is really exciting. The fact that it allows infinite nesting is a inevitable mildly beneficial side effect to having interoperability.

[0] https://github.com/nebulet/nebulet

So basically Squeak, a 25 yr old technology that still runs bitexact across all it's virtual machines.

Yo, I heard you like browsers, so we put a browser in your browser, so you can surf while you surf.

This would be for the QtQuick backend.

The QTWebView is a separate plugin component with its own set of dependencies.

You wouldn't want to do that anyways, much more effecient to just communicate from Qt to Javascript webviews (but I'm sure you know that :))

What would be the security model of such a browser environment? Maybe like an iframe?

I suspect similar to wt c++

I think you should run your QT app inside Electron!