5 ms·
I use Git on Windows with Visual Studio and I don't face any issues whatsoever. Yes, Git is not integrated with VS but I have no trouble switching to explorer
by solutionyogi 17y ago
I use Git on Windows with Visual Studio and I don't face any issues whatsoever.
Yes, Git is not integrated with VS but I have no trouble switching to explorer and commit my changes using TortoiseGit. TortoiseGit scans my working directory and presents list of all the changes made in a session.
And yes, to be on safer side, I copy and store my working directory + Git to a different location.
- nearestneighbor 17y agoCheck out these replies: http://stackoverflow.com/questions/1500400/is-tortoisegit-ready-for-prime-time-yet http://stackoverflow.com/questions/1500400/is-tortoisegit-re... It's not just the fragility and lack of integration, but also I'm just not seeing much of a benefit to counterbalance the complexity and awkwardness.
- solutionyogi 17y agoWell, I have been using it for 'production' work for last 6 months and I have not found any issues. I am not suggesting that everyone will have the same experience but I think you should give it a try before dismissing it outright based on someone else's experience. Also, if you could provide some real details on the 'complexity and awkwardness', I could share my experience which could be helpful.
- nearestneighbor 17y ago> give it a try before dismissing it Giving it a try can only prove the presence of fragility, not its absence :-) Generally, people are very reluctant to criticize "hip" tools like e.g. Clojure, Haskell, Google Go, Git or its accessories. So, when 3 out of 4 people say they had problems with it, to me it weighs very heavily on the negative side.
- wvenable 17y agoFor the record, I agree with you on Git (on Windows at least). It's improved at a rapid pace but it's still a bit awkward. However, that's no reason to dismiss all version control.
- nearestneighbor 17y agoI'm glad you agree, because for the rest of the equation (Tarballs > CVS > SVN), Linus agrees with me. So you see, I embody the combined wisdom of both of you, as far as version control goes.
- wvenable 17y agoYou have his equation wrong. He says in this article that SVN is still better than CVS. And really, I would agree that tarballs are better than CVS. So the equation is more likely SVN > Tarballs > CVS. Don't put words in Linus's mouth. Also Subversion no longer stores it's data in a database so Linus's objection in this article has been resolved. Finally, Linus's needs are pretty unique in the world. Linus isn't satisfied with Subversion for the same reasons it might work perfectly well for you.
- nearestneighbor 17y ago> He says in this article that SVN is still better than CVS. He says SVN is better, but is more fragile (which for source control, I interpret as being worse): SVN fixes (supposedly) those "implementation suckiness" issues. ... I think it's also a much more fragile setup and there's apparently been people who lost their entire database to corruption Even if SVN = CVS, clearly Tarballs > SVN, according to him. His actual quote was Tarballs >> CVS. I can dig it up if you can't.
- wvenable 17y agoThousands of companies (and millions of developers) use Subversion. It's 10 year old. It's an Apache project now. It's solid. It's a simple and easy to use tool that will make your life better. That's all. If you find that personally offensive, so be it.