4 ms·
Why do people need IDE source control integration? On windows there is a perfectly good explorer integration, on OSX there is perfectly good command line. Explo
by UnFleshedOne 15y ago
Why do people need IDE source control integration? On windows there is a perfectly good explorer integration, on OSX there is perfectly good command line.
Explorer integration on windows beats any IDE integration simply because you don't need to launch IDE with a correct project/workspace just to see if you have local changes or something. Once you have multiple sandboxes of different projects of a decent size, IDE integration doesn't cut it.
(and an unrelated rant: how come xcode can't build two completely unrelated projects at once?)
- nupark2 15y ago> Why do people need IDE source control integration? ... So that I can hit cmd-option-C (in Xcode), review my diffs and commit, all in less than ~10 seconds. > Explorer integration on windows beats any IDE integration simply because you don't need to launch IDE with a correct project/workspace just to see if you have local changes or something. Once you have multiple sandboxes of different projects of a decent size, IDE integration doesn't cut it. If I'm working on a project, I'm going to have the IDE running anyway. It sounds like you have a significantly different working model. On OS X I'll fall back to the terminal for VCS without the IDE running, but it's not a replacement for in-IDE VCS.
- smackfu 15y agoI really value being able to see a real time diff vs. the latest version under source control, and to hover over the sidebar gutter to show me the previous code. Check in / check out isn't too valuable, but having add/delete automatically ripple through to source control is nice.