The rough user goal is to provide an alternate UI ...
# thinking-together
j
The rough user goal is to provide an alternate UI for the step buttons, that encourages exploration over precise continue to here operations.
g
this may be a completely off-topic point but if (in general) prefer replay UI’s to be superimposed over the thing i’m trying to replay (in this case, the webpage)
j
Oh interesting. Would you want the player to be an overlay?
d
For visualizing and exploring call stacks, I think I’d really like a flame chart (with “pauses” filtered out)
(Especially if you could highlight scopes that aren’t eligible for GC)
g
my honest preference would be an overlay in the style of the track controller on eg a youtube video
j
@Don Abrams for sure. I'd love to design a flame chart UI with more visual real estate, display names, arguments
a bit like seymour's macro ui -- https://harc.github.io/seymour-live2017/
👍 1
@Garth Goldwater what goals would you hope to achieve with a video style player? i think our top timeline could be more track like...
w
All depends on the level of detail you want. I find most imperative programming errors come from some supposed invariant becoming invalid. So the two main operations you want are: (1) after this line of code executes, it all goes to hell (often with an exception but not always) so let's step back from here, and (2)
(Darn return...)
the value of this instance variable is wrong, how did that happen, or why didn't it get updated by some other thing.
Even the thorniest bugs I see end up being a few iterations between (1) and (2). Following a stack (1) leads to a bad variable value (2) caused by a by a stack (1) with another bad variable (2) mistakenly passed from over here (1).