Yeah, being able to reliably preserve state between reloads is an incredible productivity boost. It's also fantastic for figuring out what's going on in the app. Any time you're not sure what a particular piece of code does, you can just run it and see the output.
I find the REPL removes a lot of stress and frustration from the development process. I run every function I write to see that it's doing what was intended. Then once I'm happy with it, I move to the next step, and so on. So, the only context that I need to keep in my head tends to be what the last function I wrote did, and what the current function that I'm writing is doing. In vast majority of cases any errors I see are going to be found in the last couple functions that I wrote.
Comments
It's a very good example of a front-end REPL. I used to think hot reloading was good, but to keep the state between reloads is a whole new level.
Yeah, being able to reliably preserve state between reloads is an incredible productivity boost. It's also fantastic for figuring out what's going on in the app. Any time you're not sure what a particular piece of code does, you can just run it and see the output.
I find the REPL removes a lot of stress and frustration from the development process. I run every function I write to see that it's doing what was intended. Then once I'm happy with it, I move to the next step, and so on. So, the only context that I need to keep in my head tends to be what the last function I wrote did, and what the current function that I'm writing is doing. In vast majority of cases any errors I see are going to be found in the last couple functions that I wrote.