Speaker 3
We definitely have a lot of folks on our team who are super looking forward to any kind of debugger. And I think Jason, the last time we talked, we did talk about like a time traveling tool. I think that would be cool. I think we compared it to like Redux. And then I think I said at the time, I don't even really like, I kind of remember working with that, but not really because Redux is like a black hole in my memory. Yeah.
Speaker 2
It was just kind of brainstorming of things we could potentially do. It's just a lot harder in our scenario because we don't have a single thread, you know, Redux Elm, they have a single event thread. And it's always, we
Speaker 1
have a million of processes that can be happening on a page or whatever. It's maybe you can't, there is no stop the world. And they're all, you know, we can't stop the world.
Speaker 2
We can't just say stop the state.
Speaker 1
Yeah. We could show you like the history of the live view and stay the steps that went through. And theoretically, we could even replay those on a new process,
Speaker 1
like all the other concurrent processes happening in the background isn't going to necessarily give you a deterministic output if you rerun it. Right.
Speaker 2
And then we have to like, do we filter certain messages? Like your process gives a lot of messages that you just don't handle, let us handle implicitly. Do we show all those? Do we show? You know, maybe you have a process that's, you know, a pub sub that's just sending millions of messages and you filter most of them out. We don't know that you're filtering them out. You know, like, do we, how do we know that that's a message you care about? You know, so there's lots of questions about how to accomplish that. So, and there could be just really chatty things. The chatty stuff is where things get really messy, really fast. It's like everything kind of falls apart in that scenario, which there are lots of use cases for chatty things. So yeah, sorry, little diversion from the topic at hand, but yeah.
