I am personally quite excited about having a common standard for binaries on the web, that can be generated from C++ and I think there is a lot of potential and I am happy to see Qt going in that direction.
Regarding the load-times: WebAssembly supports dynamic linking, so browsers might cache Qt libraries, so they would only have to download them once. If the pages loaded the libs from a common location (say download.qt.io), they would even only have to load them once for all pages that use them. (I do have to say that I've had bad experiences with the caching of wasm files - sometimes they aren't even reloaded after new versions are on the server... but that should only be a temporary problem). About the threading: there are Web Workers in the HTML5 standard. These basically are threads, but they are harder to use (for example because of /*strict*/ ownership of objects), so it might not be feasible to map threads to Web Workers... Just throwing it into the discussion. -- Viktor Engelmann Software Engineer The Qt Company GmbH Rudower Chaussee 13 D-12489 Berlin viktor.engelm...@qt.io +49 151 26784521 http://qt.io Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B The Future is Written with Qt www.qtworldsummit.com
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
