Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
The annoying about autosave is when you are in the middle in a change and want to check something in the browser but the rest of the pipeline is throwing errors... When manually saving Ive got full control on when to compile.
-
Guess who made a change in his editor.
It wasn't bothering me to hit ctrl+s but it's quite nice not to have to.
Thanks -
@Codex404 thats a fair point. I also don't like autosave. because it saves when only half the new method is done and everything is broken. but I never make changes and then think "wait. let's compile that old version. just to try it."
I either compile what I have, or if I need an old version, usually the binary from the last compilation is still there. so why would I not want compilation to save and compile? -
@deadPix3l most pipelines I use have a watch on the files and auto browser reload... As soon as one saves one is fucked.
-
I worked quite some time with the Delphi 2007 IDE wich dies approximately every 2-15 minutes. There I got the habit of slamming ctrl+s after every pause I take when coding... 😐 Still do it even in intellij... just can't change it anymore... bad habit
Related Rants
Doing pair programming while I was navigating on somebody else's computer, we hit a weird behavior that our code changes weren't reflected.
Trying everything it turned out: I forgot to save.
Yet: Why though would you make me save? And why did the IDE not warn me about compiling unsaved changes? I think it was eclipse for Java, oh well. What can I expect ...
Anyways, I have gotten so used to my editors autosaving content for me as I write it, that I completely forget about doing Ctrl + S myself.
I never understood the need to hit that key combination manually as if I break something: `get reset --hard` will help to get me to a working state. (And even if I mess it up differently, my IDE's local history also let me restore recent changes.) And if it is a workign state, then I like to commit early and often. and
I am really dumbfounded why people insist on hitting save themselves.
rant
hit save
why though
save
pair programming
eclipse