On 07/14/2017 03:18 AM, Thiago Macieira wrote:
On quinta-feira, 13 de julho de 2017 17:32:58 PDT Phil Bouchard wrote:
You just helped me figure something out: people want speed, right?
- You offer a service which converts and compiles all Javascript files
for most popular architectures (i386, x86_64, ARM, MIPS, ...)
- You cache these executables on the webserver in question
- The client just downloads and caches the respective executable and
executes it in the browser
Except for the fact that no browser would ever download and execute untrusted
binaries like that.
The closest is Native Client (NaCl).
You force that Javascript executable (".jex" file) to run inside some
embedded virtual machine with restricted access to the system.
Because let's face it: WebGL is not going anywhere. It had the slowest
progress I have ever seen!
What progress does it need? It needs to implement the OpenGL ES API. Once that
is done, they don't need to do anything. All the work is in the GL drivers and
GPUs.
Where are the WebGL games then? We don't need OpenGL ES on x86.
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
