wait.
right.
I see the problem.
Qt works fine for me!
Building native versions on the developing end is a foolish idea not suitable for programs in general, and it is time we abandoned the approach. It made sense at the time, but much time has passed since then. Some software might benefit from the increased obfuscation, but other than that it's just shit.
An IR-esque approach is good, just not LLVM. Then you're back to something like the JVM.
[1] https://developer.chrome.com/native-client/reference/pnacl-b...
I'm curious how Microsoft killed Java. I assume you mean Java on the desktop?
And by "library" maybe I meant "runtime"? I mean you just have to send the HTML and JS to the client, and everything else for running the app is already there. I guess now, you could send a Python file written to use QT and it would work equivalently on many platforms.
I was thinking more desktop (non-web) apps, really.
It's still easier than rewriting all of the development tools, libraries, etc in javascript and for the browser, and your app will be responsive and fast.
If you want to get fancy, and you're willing to sacrifice compatibility with less-cool platforms, JS is generally within 2x of native performance, which is plenty fast enough to feel "responsive". http://asmjs.org/faq.html