I have been comparing prototyping of code within Pluto and within VS Code and I have a way of working that seems to be okay. But, I’d like to point out some failings of the tools available:
Debug within VS Code is sadly lacking. When comparing against MATLAB, I find that the debugger lacks the right user-friendliness. I would like the debugger to expose variables within the Julia session in the lower window as though the code was being executed within. I also want the debugger to have access to plotting on the command line, instead of the debug prompt elsewhere. I would like break points in the source listing to be automatically registered with the julia session, and for the julia process to not end when the debugger has completed.
Pluto is really useful for small efforts and quick investigation but I have not really figured out now to be disciplined in the Pluto notebook. The temptation to try out wild stuff in the next cell is too great, and I always end up with a mess that makes it very difficult to differentiate between what I want to achieve and all the stuff I tried out along the way. This is more a statement on my failings than Pluto’s because I see any code I write as a source of future cut-and-paste economics for later.
Pluto could use with a save-as button instead of a move button. But maybe this is because I don’t understand what you can do from the code window. It would also be good if the notebook is oipened in another tap on the browser and the main Pluto menu was retained. If there is a way by which I can specify the browser that Pluto should use in Windows, that would be good as well. If there is one, I apologize for not looking first.