News for hackers. Stuff that matters.
Re:The Emterpreter: Run asm.js code before it can be parsed by jdmichal on Monday February 23, 2015 @06:05PM (#9097644)
Binary sizes, which would even further improve startup times, along with reducing network usage (and thereby hosting costs). GZip works just as good on binaries as it does on JavaScript.
Re:The Emterpreter: Run asm.js code before it can be parsed by beagle3 on Tuesday February 24, 2015 @12:17AM (#9098868)
There are two things here:

1. [citation needed] and a [specific bytecode] needed. Details are everything: an uncompressed .dex file is comparable to a gzipped compile jvm class file; Also, with a specific bytecode in mind, if you compared minified+gzipped gs to gzipped bytecode, I suspect the difference will be small.

2. Regardless, the benefit of binary size is already provided, yesterday, with the emterpreter, without requiring any buy in from any browser vendor.

So, again - what's the benefit, other than startup time (which might be solved in other ways) of a universal browser bytecode?

Re:The Emterpreter: Run asm.js code before it can be parsed by iopq on Tuesday February 24, 2015 @04:05AM (#9099503)
If you read the article, it downloads the full sized binary later. So actually the size with the emterpreter is higher
Re:The Emterpreter: Run asm.js code before it can be parsed by beagle3 on Tuesday February 24, 2015 @10:51AM (#9101272)
I commented on another thread, that I believe a future version of the emterpreter will generate the full JS back from the bytecode, thus eliminating that problem - it will increase the emterpreter size by a few tens of Ks, but that will probably by cached everywhere through CDNs.

And even if it never does - it's politically close to impossible to agree on a universal bytecode, so it is extremely unlikely to happen. (Google already tried with PNaCl - if they can't pull it, I doubt anyone else can)