Steve, Yeah it might be a lack of understanding, but I know the tools on Windows are not for the faint hearted. I have had better success with SVN than I have ever had with Git. I tried using smartGit which the programmers have a very good version called smartSVN and the most basic of rolling back was a pain in the butt or keeping in sync with the master repository. But yes it might be me, but the tools really do suck for Git and I have found that I am forced to go back to a command prompt to do anything with Git.
Especially when something goes wrong, I had an issue with an Open Source product just recently where I forked the repository, and ran into an issue where it stopped pulling from the master branch and all the new changes would never get merged from master to the local repository, and the only solution that a Google search provided was delete the fork and start fresh. That was a few years ago, so it might be different but I think that is important, because you can end up in serious trouble for the new user. That to me this is a productivity killer, once I am forced to leave the IDE then I am no longer interested in that tool. And is one of the things I don't like about Git at the moment, the last I also looked was that you also need 3rd party tools to even run Git on Windows to begin with, which is something I personally don't like Now don't get me wrong, I do understand its benefits across distributed developers that is a great part of these type of source control systems. But distributed systems like Git are not the answer in all scenarios either, in extremely closed teams I would highly recommend SVN any time of the day over Git. In Open Source and the like I would recommend Git or the like, but expect a very huge learning curve. -- Regards, Andrew Scott WebSite: http://www.andyscott.id.au/ Google+: http://plus.google.com/113032480415921517411 On Thu, Jan 31, 2013 at 2:10 AM, Steve 'Cutter' Blades < cold.fus...@cutterscrossing.com> wrote: > > And I'll have to disagree with you, Andrew... > > Having worked extensively in both Subversion and Git, I find Git to be a > much more robust tool, providing a lot more flexibility, and huge gains > in overall workflow. Anytime I have to move back towards Subversion it > is somewhat painful. All of that aside, Git is not for the faint of > heart. It can take a while to wrap your head around task workflows that > are very basic in Subversion. It's a complex tool, for enterprise > development, and very affective. The larger the team, the more valuable > it is. > > Steve 'Cutter' Blades > Adobe Community Professional > Adobe Certified Expert > Advanced Macromedia ColdFusion MX 7 Developer > ____________ > http://cutterscrossing.com > > > Co-Author "Learning Ext JS 3.2" Packt Publishing 2010 > > https://www.packtpub.com/learning-ext-js-3-2-for-building-dynamic-desktop-style-user-interfaces/book > > "The best way to predict the future is to help create it" > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:354138 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
