nowfound

Life & fun · December 9, 2015

Lua Prototype of Elm's Time-Travelling Debugger

Lua Prototype of Elm's Time-Travelling Debugger launched on December 9, 2015 with 53 votes, #1,637 of 3,505 launches that month and more than 90% of that year's launches. The site was not reachable when checked in September 2026.

Visit github.com ↗Alternatives

In plain words

This is a Lua implementation of a time-travelling debugger inspired by Elm's debugging capabilities. It allows developers to step backward and forward through program execution to identify issues. The tool is designed for Lua programmers who want to inspect their code's behavior at different points in time without re-running it. It's available as an open-source project on GitHub.

written from the facts on this page · September 2026

Does a similar job

all alternatives →
  • Lua-libuv – A Lua with libuv experiments2025 · github.com · ▲42

    laboratório de integração Lua com libuv para execução de scripts assíncronos e experimentação de POCs - joaoneto/lua-libuv

  • Time travel debugging AI for more reliable vibe coding2025 · nut.new · ▲129

    Hi HN, I'm the CEO at https://replay.io. We've been building a time travel debugger for web apps for several years now (previous HN post: https://news.ycombinator.com/item?id=28539247) and are combining our tech with AI to automate the debugging process. AIs are really good at writing code but really bad at debugging -- it's amazing to use Claude to prompt an app into existence, and pretty frustrating when that app doesn't work right and Claude is all thumbs fixing the problem. The basic reason for this is a lack of context. People can use devtools to understand…

  • CodeTracer – A time-traveling debugger implemented in Nim and Rust2025 · github.com · ▲334

    Hey! We are presenting CodeTracer - a user-friendly time-traveling debugger designed to support a wide range of programming languages: https://github.com/metacraft-labs/codetracer?tab=readme-ov-f... CodeTracer records the execution of a program into a sharable self-contained trace file. You can load the produced trace files in a GUI environment that allows you to move forward and backward through the execution and to examine the history of all memory locations. They say a picture is worth a thousand words — well, a video is even better! Watch the demo below to see…

  • Visual debugger for Rails system tests2024 · github.com · ▲131

    Hey all, I've been working on this side project to get a Cypress.io-like experience, but for Ruby developers. It's plug-n-play with Capybara system tests, with the following features: - visualize assertions/commands as they happen - view all API requests, errors, and logs in the timeline - pause/continue on any step - rewind through history with a recorded video This is brand new, so looking for people to start trying it out and leave feedback.

  • LuzoMar 2026 · luzoapi.vercel.app · ▲122

    Design and debug API workflows visually

  • Letting LLMs Run a Debugger2025 · github.com · ▲147

    Hey HN, I just built an experimental VSCode extension called LLM Debugger. It’s a proof-of-concept that lets a large language model take charge of debugging. Instead of only looking at the static code, the LLM also gets to see the live runtime state—actual variable values, function calls, branch decisions, and more. The idea is to give it enough context to help diagnose issues faster and even generate synthetic data from running programs. Here’s what it does: * Active Debugging: It integrates with Node.js debug sessions to gather runtime info (like variable states and stack traces). *…

More life & fun this month

the category →

Source: Show HN post ↗

Launched alongside, December 2015

the whole month →