The big difference is that you lose state every time you do that, the main goal ...

voidlogic · on April 30, 2013

If there is a way to consistently inject the input to the program (to lead to the same state), I would be OK with editing a Go program to cause (behind the scenes):

  1. moving a break point 
  2. recompile
  3. run
  4. stopping at new break point

I think that happening behind the scenes could be made to appear like live editing in other languages. Go is fast enough compiling and fast enough executing that I think it could be pulled off as not appear laggy as well. But maybe I'm wrong and I don't understand well enough how LT handles other langs.

pjmlp · on April 30, 2013

Have you ever used a REPL?

It is an interactive process. You are build pieces of the application bit by bit.

There is no complete application state where to set breakpoints.

peterwaller · on April 30, 2013

Relevant: https://github.com/jteeuwen/mitosis