are there metrics on how es6 and future proposals affect javascript load-time for webpages?

kdex kdex at
Thu Jun 22 00:20:16 UTC 2017

I don't think that this is a well-defined question. Is "load time" equivalent 
to "parse time"? Is it "compile time"? Is it both? Is it something else? Are 
we talking about engines that don't generate native code and thus maybe 
"interpretation time"? What are we measuring when you say "JavaScript load 

First of all, ECMAScript requires an environment, which may or may not be a 
browser. So it might not necessarily make sense to assume "web pages" or 
browsers in the first place.

Aside from that, a great deal of "load time" (?) will likely consist of the 
time needed to parse the source code. Anything else is mostly implementation-
specific and thus varies from engine to engine.

Could you state your question more precisely, please?

On Thursday, June 22, 2017 1:59:05 AM CEST kai zhu wrote:
> and should future proposals take load-time performance into account?
> hi, i’m a new subscriber, and apologies if this seems like a newbie
> question.
> a bit of trivia - i remember long ago (maybe 2010?) a website called “great
> computer language shootout” or something had d8 consistently having the
> fastest load-time of all interpreted languages benchmarked.  i recent
> google-search led me to maybe the same website
> (, but i can no longer find
> load-time stats.
> -kai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the es-discuss mailing list