Rater than using a bunch of superlatives such as 'utter nonsense' and 'useless', could you please explain better the use case?
What has capturing a call stack has anything to do with performance timers? Why is allowing the programmer to group a set of queries into one array of results through a callback any limitation?
But I guess the main issue is that there is no consensus of what are the issues to be solved for this API to be useful. So until this is resolved, there is no point having a discussion about API design.
From: Florian Bösch <firstname.lastname@example.org>
Date: Friday, April 12, 2013 11:12 AM
To: Rémi Arnaud <email@example.com>
Cc: Rémi Arnaud <firstname.lastname@example.org>, Ben Vanik <email@example.com>, "firstname.lastname@example.org" <email@example.com>, Kenneth Russell <firstname.lastname@example.org>, Gregg Tavares <email@example.com>, Public Webgl <firstname.lastname@example.org>, Brian Cornell <email@example.com>, Glenn Maynard <firstname.lastname@example.org>
Subject: Re: [Public WebGL] For review: ANGLE_timer_query extension
On Fri, Apr 12, 2013 at 8:06 PM, Arnaud, Remi <Remi.Arnaud@amd.com> wrote:
That's utter nonesense. You didn't think this trough. A so inclined programmer might capture a call stack of his drawing. Where's your "known order" now? Nowhere. It's gone. It had structure before you mangled it into a flat list. A flat list is not the only usecase of queries. Stop dictating application structure to people wanting to use timer queries. Think trough what people might want to do with them before assuming "A list is what anybody will ever need".