3 ms·
I think the reason that none exist is that they are incredibly difficult to implement. My armchair observation is that tracing the entire history of the virtual
by mlazos 8y ago
I think the reason that none exist is that they are incredibly difficult to implement. My armchair observation is that tracing the entire history of the virtual machine is probably slow/memory intense/complex when the model of computation is not simpler (like in an elm-like functional language) if you limit the number of ways the state of the VM can change I think this becomes an exponentially simpler problem. I’ve been debugging/simulating a hardware project at work, and even small bits of hardware can take a really long time to simulate. I’m using that as comparison because it does give a nice timeline of the entire state of the system which you can explore through the whole execution timeline.
- jasonlaster11 8y agoThat's a great point. Tracing quickly becomes slow and memory intensive. I think you would enjoy this write-up. WebReplay is explicitly not tracing for that reason. https://developer.mozilla.org/en-US/docs/Mozilla/Projects/WebReplay https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...
- mlazos 8y agoThanks for the post, I didn't even realize how large the design space for something like this is. I enjoyed the level of detail and the explanations of the design tradeoffs.