Live data from Hacker News

Show HN: Time travel debugger for web development

replay.io

181–190 of 223 posts

Re: Show HN: Time travel debugger for web development

#182

Earlier quoted context omitted.

Which debugger do you use because I live in JetBrains tools and their debugger front-end support for conditional or on exception break points is phenomenal

What I mean is coming up with a condition to make as a watch/breakpoint isn't always obvious. Especially with errors that happen "sometimes randomly".

If an error causes an exception there is an option to suspend execution when one is thrown.

Re: Show HN: Time travel debugger for web development

#183

Co-founder here. It feels incredible to be sharing Replay with all of you. It's been a labor of love the past five years! Replay started off as a simple experiment in what would happen if we added a step back button and rewind button to the Debugger. We quickly realized two things. First, nobody uses breakpoints. Second, being able to share is so much more powerful than being able to rewind. Here’s how Replay works t…

Doesn't replit have a similar feature? Where you can link to different debugging states? Are you aware of that? If yes how is it different?

(Replay engineer): Yes, replit has been working on adding similar functionality (https://blog.replit.com/debuggest).

In fact: we've been collaborating with them on it! :)

Re: Show HN: Time travel debugger for web development

#184
Sorry to be blunt. That's a cool toy for nerds who have too much spare time at work. Real projects don't care that much about quality, they care about adding features as fast as they can while keeping the quality bar slightly above "completely broken". Nobody's going to look at these replayable traces because by the time such a bug gets seen by a dev, the project would've been half rewritten. This level of quality is just unnecessary in web.

Re: Show HN: Time travel debugger for web development

#185
This looks exciting and I’m going to give it a try.

For what it’s worth, if it helps with marketing: I am immediately skeptical that it’s going to be some mix of tedious to get working with my specific webpack dev server setup, be slow or unreliable, or never actually keep the state I need.

I’m hoping to be wrong on all of that. But when I scrolled the (beautiful) website, I would have loved to see some really nasty example in addition to the very elegant introductory “show don’t tell” example.

I want to see the first and think “okay I get it” and then be shown something really complicated to illustrate just how durable the tool is.

Re: Show HN: Time travel debugger for web development

#186

Co-founder here. It feels incredible to be sharing Replay with all of you. It's been a labor of love the past five years! Replay started off as a simple experiment in what would happen if we added a step back button and rewind button to the Debugger. We quickly realized two things. First, nobody uses breakpoints. Second, being able to share is so much more powerful than being able to rewind. Here’s how Replay works t…

The problem with breakpoints is my loop runs 1000 times and I only care about the one time it errors. Making watch logic for that sometimes is too complicated or changes the outcome (race conditions especially). This seems like a great solution. I'll be checking it out!

For Python, but only if execution is deterministic, I made a small library that tries to address that issue: https://github.com/breuleux/breakword (it prints data alongside a deterministic list of words and you can set a breakpoint on a word of interest in a second run).

It's really a poor man's replay, though. That tool looks really slick, I'll definitely give the Python version a go if/when it comes!

Re: Show HN: Time travel debugger for web development

#187

Dan Abramov 2015 https://www.youtube.com/watch?v=xsSnOQynTHs But there was one earlier presentation I cannot find it, guy was showing live debugging of the video game. Not sure is it TED or one of conferences ... Edit: This is it: Bred Victor: https://youtu.be/EGqwXt90ZqA?t=1006 2013 Future of programming https://www.youtube.com/watch?v=8pTEmbeENF4

*Bret Victor: http://worrydream.com/

Many past threads on HN: https://hn.algolia.com/?q=worrydream

Re: Show HN: Time travel debugger for web development

#188
post #135

Windows has this for time travel debugging : https://docs.microsoft.com/en-us/windows-hardware/drivers/de... . Visual studio also supports TTD https://devblogs.microsoft.com/visualstudio/introducing-time...

Only the enterprise edition though.

Windbg-preview supports TTD too.

Re: Show HN: Time travel debugger for web development

#189

Co-founder here. It feels incredible to be sharing Replay with all of you. It's been a labor of love the past five years! Replay started off as a simple experiment in what would happen if we added a step back button and rewind button to the Debugger. We quickly realized two things. First, nobody uses breakpoints. Second, being able to share is so much more powerful than being able to rewind. Here’s how Replay works t…

> First, nobody uses breakpoints. It saddens me that a lot of people don't use debuggers and default to adding print statements. As far as I can tell, it's for several reasons: 1. The debugger is primitive (e.g. Godot GDScript - no conditional breakpoints or watches). 2. The debugger is unstable (e.g. Android Studio - frequently hangs, or takes a long time to populate data needlessly) 3. The debugger's UI is not frie…

I’ve used good debuggers in the past, but the main downside to me is that the workflow improvement is relatively minimal compared to print debugging. The “live programming” aspect of Common Lisp and Clojure, as well as the way Cider implements tracing for Clojure _is_ a major improvement, but only because they let you be more precise in what needs to be re-run for print debugging.

Re: Show HN: Time travel debugger for web development

#190
post #53

I am a JavaScript framework author, and was one of those fortunate to get early access and honestly it is the most useful tool I've ever used in the debugging space. Sometimes things are complicated. Often there is a need to do digging to uncover the issue. Being able to move forward and backwards and even jumping between seemingly disjoint parts of the timeline are all at your disposal with Replay. Replay has saved…

Now I'm even more excited. Replay Team - please consider charging a reasonable amount ($10/mo) for individuals/small teams. I want this to be viable as a business.

What, no! I'm a broke college student, I don't want to pay for this, at least not yet.
Post reply on HN