Re: [JS-internals] How JS team members decide what to work on

2017-04-19 Thread Nicolas B. Pierron
On 04/11/2017 07:34 PM, Jason Orendorff wrote: I have no plans to type in my notes from the JS meeting. If you want them, ping me on IRC. But one thing I want to think about is how we decide what to work on, especially performance work. Today, it's like this: - If you're a volunteer, of course y

Re: [JS-internals] How JS team members decide what to work on

2017-04-12 Thread Shu-yu Guo
On Tue, Apr 11, 2017 at 12:34 PM, Jason Orendorff wrote: > I have no plans to type in my notes from the JS meeting. If you want them, > ping me on IRC. But one thing I want to think about is how we decide what > to work on, especially performance work. Today, it's like this: > > - If you're a vol

Re: [JS-internals] How JS team members decide what to work on

2017-04-12 Thread Steve Fink
On 04/12/2017 06:55 AM, Kannan Vijayan wrote: It's possible to expose in the profiler UI, although the granularity might be too high and skew might be an issue. Really this is more of a telemetry-style metric - we can accumulate counts for how often fallbacks are hit (or how often we generalize

Re: [JS-internals] How JS team members decide what to work on

2017-04-12 Thread Kannan Vijayan
It's possible to expose in the profiler UI, although the granularity might be too high and skew might be an issue. Really this is more of a telemetry-style metric - we can accumulate counts for how often fallbacks are hit (or how often we generalize into a polymorphic stub) and report that as a si

Re: [JS-internals] How JS team members decide what to work on

2017-04-12 Thread Ehsan Akhgari
On 2017-04-12 5:33 AM, Jan de Mooij wrote: > On Tue, Apr 11, 2017 at 11:25 PM, Steve Fink wrote: > >> The juxtaposition of telemetry and the IC logger makes me wonder -- is it, >> or could it be, lightweight enough to report on via telemetry? It would be >> pretty cool to be able to drive work of

Re: [JS-internals] How JS team members decide what to work on

2017-04-12 Thread Jan de Mooij
On Tue, Apr 11, 2017 at 11:25 PM, Steve Fink wrote: > The juxtaposition of telemetry and the IC logger makes me wonder -- is it, > or could it be, lightweight enough to report on via telemetry? It would be > pretty cool to be able to drive work off of what the bulk of our users > could make use o

Re: [JS-internals] How JS team members decide what to work on

2017-04-11 Thread Steve Fink
On 04/11/2017 02:05 PM, Jan de Mooij wrote: On Tue, Apr 11, 2017 at 9:34 PM, Jason Orendorff wrote: - Bigger projects, like Waldo's work on parsing and djvj et al's work on GC scheduling, are undertaken when we have stuff that has been showing up on profiles "forever". This kind of work isn't

Re: [JS-internals] How JS team members decide what to work on

2017-04-11 Thread Jan de Mooij
On Tue, Apr 11, 2017 at 9:34 PM, Jason Orendorff wrote: > - Bigger projects, like Waldo's work on parsing and djvj et al's work on GC > scheduling, are undertaken when we have stuff that has been showing up on > profiles "forever". This kind of work isn't driven by any one particular > measuremen

[JS-internals] How JS team members decide what to work on

2017-04-11 Thread Jason Orendorff
I have no plans to type in my notes from the JS meeting. If you want them, ping me on IRC. But one thing I want to think about is how we decide what to work on, especially performance work. Today, it's like this: - If you're a volunteer, of course you decide what to pick up—we're just glad you're