hysterical consequences

[Raoul Duke]

it is FUNNY how even today there is no good mainstream way to work on web based GUi code. You can stare at static JSX or whatever and try to guess and simulate in your head. You can run the code. You can "inspect" in the browser. And it all still just sucks because of there being too much indirection, too many layers, too many transformations and expansions, and too many things that get in the way of iterating.

vs. what an actually good, interactive, helpful, development system could be. 

(Mind you, is like a billion light years ahead of any old crap like Qt/C++.)

[Raoul Duke]

no way to see or manage the full state space. 

[Mike Austin]

What specifically? While I've been writing my app, I try to refactor it every version until there's nothing else to do. With my development using GraphQL, I would agree the tools are primitive. If I get an error, I just get an empty screen. I need to look at the endpoint call and figure out what the error is. "Field doesn't exist" or something like that. I remember Microsoft tools being able to debug SQL in the middle of a C# call for example where at least the two languages know about each other.

[Raoul Duke]

highest level statement about is that we do not have good enough tools to manage the state space e2e, or even in-the-small.