| Re: [platform-ui-dev] M2 is next week and some experiences with Android Studio |
|
On 09/14/2015 11:39 AM, Lars Vogel
wrote:
What I fear the most with autosave in Eclipse is how it would interact with the debugger. I always use "Debug As..." and modify code on the running application because it reduces significantly the feedback loop over a restart, and I often hit breakpoints. Usually, I do modify code is several classes when breakpoint is hit and save only when I believe my changes are good enough to update the classes in my running application. Before I save, my code is often bad, showing red crosses and so on, I wouldn't like this code to be injected in my application under development.Max Rydahl Andersen <manderse@xxxxxxxxxx> wrote:. I personally disliked auto-save too, but must say that now that OS X "force-feed" autosave in most of its applications I started to enjoy it. One just don't realise it >since it "just works".I fall in the same camp. Originally, I disliked auto-save, until I realized that I anyhow press CTRL+S all the time without thinking about it. And I rely on CTRL+Z to undo everything, if I made an error. With auto-save, I believe we would lost this workflow, which is IMHO the ideal workflow for a Java developer. |