3 ms·
Reading the article, this sounds _very_ similar to what we do at Replay ( https://replay.io https://replay.io ), which is time-travel debugging for web apps. I
by acemarke 4y ago
Reading the article, this sounds _very_ similar to what we do at Replay ( https://replay.io https://replay.io ), which is time-travel debugging for web apps.
I'm a front-end dev, so I'm not nearly as familiar with the magic happening on the backend, but this looks like it matches what I know about how we manage jumping to specific points in time: many forks of the browser process, run from the beginning up to various pause points.
- mark_undoio 4y agoThat makes sense - the principles seem to be quite general. But, as I understand it, replay.io records languages that use a VM by modifying the VM to help capture the non-determinism. We started by recording languages without a VM - C/C++ - so we've implemented things at a lower level (which has advantages and disadvantages). Coincidentally that means our tech could probably be used to record yours - and now we're doing more web stuff we ought to be using yours :-D
- jasonlaster11 4y agoSuggested this to Greg a couple of months ago! We sometimes use Pernosco to record the Replay Chromium and Firefox. Would love to see how Undo does in comparison. Likewise, if you're building more web apps, we'd love to hear how Replay.io works for you. We're on a shared journey to bring TTD to the world.
- mark_undoio 4y agoHi there - I actually suggested it to Greg recently too! Would definitely be interesting to do this as we've got the same goals in mind. I also like the technical blog posts, etc you guys produce.