Re:Show HN: RootCause – Record, Replay and Reproduce JavaScr...
by mankz on Wednesday April 04, 2018 @04:07PM
(#16758506)
You could, but the point is that the stacktrace is useless in most apps (unless you have stateless minimalist website). As soon as you make a web app and you have state - stacktrace doesn't help reproduce the bug.
Re:Show HN: RootCause – Record, Replay and Reproduce JavaScr...
by kerkeslager on Wednesday April 04, 2018 @04:32PM
(#16758739)
> As soon as you make a web app and you have state - stacktrace doesn't help reproduce the bug.
It does in a reasonable language. That's my point.
Re:Show HN: RootCause – Record, Replay and Reproduce JavaScr...
by brlewis on Wednesday April 04, 2018 @04:52PM
(#16758934)
What's an example of a reasonable language that has state? I figured you had to be thinking of a pure functional language.
Re:Show HN: RootCause – Record, Replay and Reproduce JavaScr...
by kerkeslager on Wednesday April 04, 2018 @05:06PM
(#16759091)
Python, Ruby... the concern isn't so much state as that it throws the exception where the mistake actually happens instead of failing silently.
Eh, I don't think that logging runtime-in-the browser is the value added here. I can wrap my codebase in a try-catch that catches exceptions and calls home with the stack trace in < 100 lines of code. Avoiding that < 100 lines of code isn't the value added.