- From: Bradley Meck <notifications@github.com>
- Date: Sat, 21 Mar 2015 14:42:07 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Message-ID: <whatwg/streams/issues/304/84456234@github.com>
Before shipping an implementation and forcing API stagnation / stabilization I truly believe we should profile this reference implementation and be ABSOLUTELY sure the VM implementors have a chance to check the profile of this API and not enter into a strange situation where some minute point prevents performance. Also, I truly hope we come up with resource finalization before that goes out... I am still reeling from not being able to have a cancelation route of promises. It just seem premature and ignorant to talk about performance being able to be optimized when no benchmark/profiling has been investigated. On Sat, Mar 21, 2015 at 1:34 AM, Domenic Denicola <notifications@github.com> wrote: > One big performance *win* will be #97 > <https://github.com/whatwg/streams/issues/97>, which is explicitly being > designed for. > > — > Reply to this email directly or view it on GitHub > <https://github.com/whatwg/streams/issues/304#issuecomment-84266091>. > --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/304#issuecomment-84456234
Received on Saturday, 21 March 2015 21:42:34 UTC