Devon Carew

It's good to know that we're not calculating the stack twice - that would have been the performance win. I think it's still worth returning the top stack first -...

> * separate callstack from variables: create a new VM API getStackOnly to return the stack with references to frame objects. This could certainly help. We could have the paused...

Attaching a log of vm service traffic to and from package:dwds, and chrome debugger traffic sent and received from dwds: [dwds_log_2.txt](https://github.com/dart-lang/webdev/files/4625350/dwds_log_2.txt)

To update here: I investigated caching the calculated `ClassDef`s (each requires a round trip to Chrome to calculate). This does not appear to be a win, as: - chrome is...

In our previous implementation of analytics it was possible to get a future for the last item sent, wait on that for a brief time w/ a 100ms-200ms timeout, and...

> around area-test might need to be made more explicit that it should prefer the affected functional area, or otherwise weighted down I agree with that (and thanks for the...

> The area should be `area-pkg` afaik (the tests in question are in pkg/_macros). Yes, but `area-pkg` is not a great `area-` itself. It's not triaged - there's no team...

I did look at some of the options here when this came up on discord a few days ago. I see the downsides of the (current) wiki being: - non-repo...

This is done now! We went with 'plain markdown files in an sdk directory', from above. All the files are now in https://github.com/dart-lang/sdk/tree/main/docs, and the old wiki (just link redirects...

We could, and lowercase would likely read better. We could also shorten file names, esp. if we categorized content into sub-directories. Doing a one-time update of the old wiki pages...