The way I derived the information to show in REPLugger was empirically — by actually coding in that codebase for a while and noticing each time that I couldn't see if the lines I was working did what I expected under different conditions.
-
-
Cool! Also in making REPLuggger I was trying to make a tool that someone like
@Jonathan_Blow might find useful — I’ve watched enough of his coding live-streams to know that there are many times when he could benefit from seeing some live values and be able to play with them0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @Jonathan_Blow @azmreece
Yeah, I agree that REPLs don't tend to be super useful in larger programs. This is the prototype for context: https://www.youtube.com/watch?v=F8p5bj01UWk … (demo at 1m30s) Please ignore that I use JS if you can. I think this kind of thing would work for Jai too since the compile times are fast enough
2 replies 0 retweets 1 like -
This Tweet is unavailable.
-
What do you think of this compared to unit tests? E.g., they seem to have the same limitation: They they don't work well for testing a large complicated program while it's running. But they seem to have found a usefulness in the industry in spite of that?
1 reply 0 retweets 1 like -
This Tweet is unavailable.
-
Replying to @Jonathan_Blow @robenkleene and
This statement has some validity for software with a final version (like games) but not for large ever evolving software like enterprise systems.
0 replies 0 retweets 2 likes -
This Tweet is unavailable.
"You are wrong because you do not make things like these things." "Actually I also make those things." "Oh... well then you are wrong for some other reason I will now try to think of." - Twitter
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.