Ups, didn't mean to submit it like that! * akligman's benchmark automation; Tom's Hardware's WBGP benchmarks I am curious about this, could we use it for awfy? I also had this plan of putting IE on awfy. Or maybe just run the benchmarks in the browser instead of the shell. * Exact Rooting retrospective And future with b2g? :) * ES6 and ES7: TC39's roadmap and our implementation plans Test262 now accepts public contributions: https://github.com/tc39/test262. We should make sure we stay on top of all the failures there (currently it's 48). We had plans to run test262 in our test suit. I think Waldo actually imported all the internationalization ones. * 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.
> 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 :/ Cheers, Tom On Tue, Jan 28, 2014 at 9:50 AM, Tom Schuster <[email protected]> wrote: > Why is this on the intranet? > > > On Tue, Jan 28, 2014 at 2:33 AM, Andreas Gal <[email protected]>wrote: > >> >> 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. >> >> Thanks, >> >> Andreas >> >> On Jan 27, 2014, at 3:39 PM, Chris Peterson <[email protected]> >> wrote: >> >> > Below are some random ideas for topics we might want to discuss at the >> JS work week. Are there other talks you would like to see or give? Feel >> free to add them to the wiki: >> > >> > https://intranet.mozilla.org/JavaScript_Work_Week_-_2014 >> > >> > * GDC trip report (from Martin/Naveed) >> > * akligman's benchmark automation; Tom's Hardware's WBGP benchmarks >> > * Beyond GGC: moving, compacting, G1 improvements? >> > * Exact Rooting retrospective >> > * ES6 and ES7: TC39's roadmap and our implementation plans >> > * Parallelization and concurrency plans >> > * Dev Tools improvements >> > * Firefox OS features and optimizations >> > * Competitive analysis of other browsers and VMs >> > * Development processes: Balancing priorities of incoming feature >> requests; FxOS and Metro teams' experiences with Scrum; Firefox desktop >> team's plans >> > >> > >> > chris >> > _______________________________________________ >> > dev-tech-js-engine-internals mailing list >> > [email protected] >> > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals >> >> _______________________________________________ >> dev-tech-js-engine-internals mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals >> > > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
