4 ms·
I wonder how most people work with their source control system. In general, I find it far easier to use git or svn from the command line because when I'm bounci
by h_r 9y ago
I wonder how most people work with their source control system. In general, I find it far easier to use git or svn from the command line because when I'm bouncing around between editors and OSes, it's always the same user experience so you get to leverage that experience better. Works for me anyway.
- deleted 9y ago[deleted]
- petre 9y agoWe're also using it from the command line. I at least expect the text editor to warn you when a file has changed on disk and you try saving over it as Vim or Micro do or to reload it automatically like Atom and Sublime do, as opposed to happily continuing to use the old version and allowing you to save it over the update without any warning, like VS Code <= 1.18 for macOS does.
- Matthias247 9y agoI’m using Vs Code pretty much exclusively for git commits. The reason is that it really quickly lets me review all my changes als diffs before committing. From time to time I find some stuff there which I added for debugging but which shouldn’t be pushed. I don’t think watching diffs in the console is a great experience. And other IDEs always felt more heavyweight in that regard.
- petre 9y ago> I don’t think watching diffs in the console is a great experience Depends on the console and on what you're used to. If you can maximize it in full screen and especially if the diffs are colored like git's, then it's a very pleasant experience. What I like about Atom is that it's not an IDE. It's an editor. If you want it to be an IDE, then you can add language specific plugins that turn it into an IDE. Even the integrated git/github plugin is useless to me because we're using fossil. In contrast, VS Code comes packed with features for Js/Ts which make it an IDE rather than an editor.