On Saturday, October 25, 2014 10:42:24 PM UTC-4, tbc++ wrote: > > "What if my file had been corrupted, or truncated and only the first 42 > bytes of the new version written thus far, or something like that at the > moment when the hang started?" > > So there's this new cool thing out there called a "version control > system". One of the more popular programs in this category is known as > git...check it out sometime, it'll help you relax when programming, knowing > that previous versions of your file are only a few keystrokes away. >
That's not an excuse for IDEs to be crashing or otherwise wigging out in the middle of file saves. Besides, it's stupid to expect everyone to use a version control system, particularly just to ward against bugs that have no business existing in the first place. Using it as mere file insurance is like swatting a fly with a nuclear-tipped ICBM. And also requires a much higher degree of formality, ceremony, and general fiddling around than many people's projects warrant, either at all or at a sufficiently early stage. Really, you expect me to create an account and publish every little bit of code I play around with on github? And then to top it off it wouldn't help that much if I saved much more frequently than I committed changes and then re-checked-out the code. And I do save much more frequently than I'd be willing to do that. I often save code that won't work, and even code that won't compile, and even code with unbalanced delimiters. Sometimes I write some function or big static map or vector or something out a line at a time, saving every couple of minutes or if I pause for any reason. I'm certainly not about to commit code in such a state to a VCS, let alone publish it where others can see it. I'm used to hitting control-S in almost any idle moment when editing just about anything, so as to be nearly up to the minute if anything goes wrong. But that does mean relying on application developers to at least make sure the file save command is stable! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
