On Tue, Nov 27, 2012 at 4:38 PM, Mark Hahn <[email protected]> wrote: > Also, could you go backwards and then continue from the final state in > order to avoid forking the history?
Yes > On Tue, Nov 27, 2012 at 2:36 PM, Mark Hahn <[email protected]> wrote: > >> > When you go backward what has already happened won't change. >> >> Awesome. So it is the answer to my dream of going backwards to see what >> caused some state change. >> > Hopefully :D Still working on some of the other parts, but currently individual scope objects can be go backwards. Haven't worked on it since the presentation. Funny how deadlines have a tendency of getting things done. > >> Could this be used in a real app? It seems the expansion of code would >> slow things down too much to observe a real app's behavior. Also the >> memory usage of all the data-structures would be excessive in long running >> apps. Maybe there could be a trimmed down version that only keeps a finite >> amount of history so the app could run forever? >> > Intuition tells me using it in a real app would be a no-go. Won't know the full overhead till I try through :) -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
