I hear you, and I agree that we have to balance polish with shiny new
features (and that our balance has perhaps been less than optimal
historically).
I won't speak for others, but I'm not trying to say "we need devtools to be
a part of every new platform feature and ship them ASAP along with the new
platform feature."
What I'm saying is that when going through the intent-to-implement process,
we should be a part of the conversation and not an after thought
​. ​
We can't do everything ourselves; we need to get platform feature
implementors thinking about what devtools APIs would make sense, and how it
would be best implemented too. Implementation of the
​platform ​
feature should be
​architected for adding instrumentation/debugging down the line. There
should be tracking bugs filed so it doesn't slip through the cracks.
It's good to be realistic about workloads and trade offs, but we should
remain optimistic as well. I am hopeful that participating in
intent-to-implement conversations now will make our lives much easier later
when we determine it is time to add tooling for those new platform features.
On Tue, Mar 31, 2015 at 2:19 AM, Panos Astithas <
pa...@mozilla.com> wrote:
>
> There have been some cases where we were quick to support new platform
features (promises and animations come to mind), but I don't see us being
able to meaningfully promise tool support any time soon, unless it comes at
the cost of papercut fixing.
FWIW, one of our returning prodigal intern
​'s (Gabriel Luong) potential projects will be a promise tool. In this
specific case, we have all the platform work done, and it is a matter of
making actors and UI now. Usually it's the other way around.