Consider shipping the components as an MCP.
Show HN: Ariana – A time travel debugger for PY/JS right in VSCode
11–16 of 16 posts
Re: Show HN: Ariana – A time travel debugger for PY/JS right in VSCode
#12Consider shipping the components as an MCP.
you caught me at the moment of coding this!
Re: Show HN: Ariana – A time travel debugger for PY/JS right in VSCode
#13This is very, very, very cool.
I implemented something like this once but had to use the typescript compiler to identify all the variable names and also use the typescript compiler to find valid moments they could change and insert code to capture their value at that time. Guessing you didn't go to that length in multiple languages. Sou how did you manage this? I'd be very interested in a technical write up and I suspect hn would too
Re: Show HN: Ariana – A time travel debugger for PY/JS right in VSCode
#14Did i read that right? What part of a debugger would require the use of an AI language model?
Re: Show HN: Ariana – A time travel debugger for PY/JS right in VSCode
#15Did i read that right? What part of a debugger would require the use of an AI language model?
Hey, yeah I know sounds weird. We're experimenting with small custom models <1B params to figure out which part of your code you'd probably not want to instrumentalize the normal way (e.g. logging absolutely everything) and instead in a more tailored way (and what that tailored way is), for instance a python for loop with 10k iterations.
Re: Show HN: Ariana – A time travel debugger for PY/JS right in VSCode
#16This is very, very, very cool. I implemented something like this once but had to use the typescript compiler to identify all the variable names and also use the typescript compiler to find valid moments they could change and insert code to capture their value at that time. Guessing you didn't go to that length in multiple languages. Sou how did you manage this? I'd be very interested in a technical write up and I sus…
Will def. do a technical write up! Wanted to do a more target approach like you around valid mutations only but I think users want to observe variables not only where they are written but also where they are read, so a low hanging fruit was to wrap all the expressions I could (hundreds of lines of AST queries and tricks per language) with functions/lambdas and some sort of "logging". Of course this is only 4 weeks in the making so there is so much more to do. And as you guessed you probably can't do the targeted approach well in Python and others.