Taking about executing script as quickly as possible (threads from 1012
which I missed and tried to glanced through just get better educated about
previous conversations).
Wouldn't browsers be able to store pre-parsed/compiled' scripts in a
separate byte code cache,
with scripts promoted to the
On Mon, Jul 15, 2013 at 9:42 AM, Bruno Racineux br...@hexanet.net wrote:
Taking about executing script as quickly as possible (threads from 1012
which I missed and tried to glanced through just get better educated about
previous conversations).
Wouldn't browsers be able to store
On 7/15/13 3:42 AM, Bruno Racineux wrote:
Wouldn't browsers be able to store pre-parsed/compiled' scripts in a
separate byte code cache,
You mean like https://bugzilla.mozilla.org/show_bug.cgi?id=679942 ?
There's some discussion in there about whether this is a worthwhile
optimization with
On 7/15/13 6:12 AM, Yoav Weiss y...@yoav.ws wrote:
On Mon, Jul 15, 2013 at 9:42 AM, Bruno Racineux br...@hexanet.net wrote:
Taking about executing script as quickly as possible (threads from
1012
which I missed and tried to glanced through just get better educated
about
previous
It goes beyond frameworks if based on pure 'access frequency'.
For example, a site backend you use daily or you favorite web app would be
also benefit.
Including the G+, Twitter and Facebook site's scripts, Map APIs, Google
News, or whatever you access most frequently from your machine.
On 7/15/13 3:02 PM, Yoav Weiss y...@yoav.ws wrote:
It goes beyond frameworks if based on pure 'access frequency'.
For example, a site backend you use daily or you favorite web app would
be
also benefit.
Including the G+, Twitter and Facebook site's scripts, Map APIs, Google
News, or
On 7/15/13 7:28 PM, Bruno Racineux wrote:
The outline there suggest: - When compiling a lazy script with no inner
functions, do a table lookup for a script with the same source location
(filename, lineno, column, source begin/end
So just to be clear: that bug is talking about script in the
