For some background: We are using cached data since a while in VS Code and are quite happy with it. It's one of the simpler things to improve start up time. The only downside is the slow down on first start when we generate and store the cached data and I was thinking about making our build machines do this.
Thanks again for clarifying the API contract. I won't try some lucky shots with prebuilt data for the relatively monotone mac world ;-) Actually, we ran into this a while back. Our minifier had changed, producing slightly different code which didn't get rejected but causing things to go south [1]. We now use a stronger cache key such that we don't attempt to reuse bad cached data... Thanks and Happy Coding, Joh [1] https://github.com/Microsoft/vscode/issues/23841#issuecomment-291457502 On Friday, April 21, 2017 at 11:00:04 AM UTC+2, Johannes Rieken wrote: > > Thanks for clarifying! > > On Friday, April 21, 2017 at 10:00:03 AM UTC+2, Ben Noordhuis wrote: >> >> On Fri, Apr 21, 2017 at 9:51 AM, Johannes Rieken >> <[email protected]> wrote: >> > Does the data depend on things like endian-ness, CPU etc or only >> > on v8-locals like v8-version and v8-flags? >> >> All of the above; it's machine-, version- and invocation-specific. >> > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
