I remember hearing about Chronon, another time traveling debugger for the JVM way, way back but no idea what happened to it. Were you familiar with or inspired by it? Can't even figure out if it still exists.
It seems pretty much dead though, here is a page from the way back machine
https://web.archive.org/web/20180118111950/chrononsystems.co...
The only difference which I am thinking here is (based on just their front page), seems they are recording only function parameters and return values. If that understanding is correct, videobug is recording down to local variable level data (so lets say if you return a list from a db query and iterate over it in your business logic function, you will be able to see execution inside the loop.
Also, in the FAQ, it says the pre-production/production env is likely to be years away. While we are very early, we are definitely aiming videobug in pre-production to begin with.
Debugging and catching bugs has always been a fun game for me, but as the team size grows it becomes very tidious
1. Run into too many “works-on-my-machine-but-not-in-production” cases.
2. Logical errors were hard to catch with logging tools. We often added more logs to trace back where the issue was. This involved several production deployments.
3. Race conditions were rare and hard to recreate, and remained unresolved for days. Combing through logs for days was frustrating.
4. Logging tools offered stacktrace for crashes - we needed to figure what data led to these crashes. This was time-consuming.
Adding the links here again to make them clickable for mobile users
https://bug.video
2 min demo explaining how to use Videobug.
https://www.youtube.com/watch?v=U53IQifMt54
discord channel
https://discord.gg/Hhwvay8uTa