On Tue, Jan 28, 2014 at 10:11 AM, Tom Schuster <[email protected]> wrote:
> * Dev Tools improvements > IIRC we have been discussing this for the last two work weeks, but the > actual result of JS specific features seem to be rather low. I know we > landed some stuff like setMetadata, but I am not sure if it's even used? > Recently I saw some things about Memory maps that seem very exciting. > There's lots of work going on regarding better devtools support. Ranging from getting a much better story for memory reporting over better support for dynamically-created (i.e., evaled) code in the debugger to debugging workers. Plus, reducing the overhead of instrumentation such as SPS. Having said that, what would be great is if we could somehow make use of the fact that the devtools team is having a work week shortly before ours. Maybe someone could go there and collect information that can the inform our planning? > > > I would like to see optimizations of JS for Chrome use on the agenda. > Currently people are rewriting JS code to C++ to make it smaller, > especially around workers. We need to fix that. > I just saw at ton of bugs related to worker memory usage, but maybe it's > too late already :/ > There is indeed a lot of work going on for that, and even more planning and discussion of ideas. I don't see how this can ever be "too late": not only is there a ton of existing code that'll benefit (is benefitting) from it; there will be more code in the future. The better we can make the situation, the more, I guess. > Why is this on the intranet? Good question. Naveed, maybe we could move it somewhere Tom can see it? If not, I just subscribed to changes to the page, and can update Tom of any important changes. _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
