I have to agree with Ted: use git. I disagree with the learning curve, I don't think it's any steeper than other VCSs. It's just that most people start with a server-centric system like CVS or SVN and then have a harder time wrapping their heads around a new model (decentralized) of VCS usage.
I've used Git, CVS, SVN, RCS, Perforce, and a number of others over the years and Git is by far the best one. My #1 reason to use Git is the fact that the repo is in your local workspace. Every other system you have to be connected to the network in order to do simple things like reading the commit logs, diffing versions, etc. Even if you are forced to use some other centralized system, you can use git on top of it locally to manage your own workspace before pushing to the "real" SVN or CVS repo. If you do any work on the Linux kernel, git is mandatory. It's becoming so for many more projects also. For example, Drupal is migrating to git as I type this. What many people consider git's "advanced" features are actually fairly natural and are only considered advanced because the same features are so painful in other VCSs that people avoid them. For example, branching and merging. Merging branches in CVS is painful. In SVN (in my experience) it's even worse. In git, it's everyday practice and easy to do. Maybe I sound like a Git zealot. I'm not, it just works so much better for my workflows than other VCS systems. I use SVN extensively also for various reasons, but even when using SVN for my server, I usually use git-svn locally. Many would consider the lack of good graphical tools as a downside. Perhaps, but a programmer should be comfortable from the commandline. There's several GUIs for OSX if you're interested: http://stackoverflow.com/questions/83789/what-is-the-best-git-gui-on-osx But I just use git from the commandline. BTW, I believe there is a git integration for BBEdit, done by the Ruby guys. If you want a decent SVN client for OSX I recommend Cornerstone. Whatever you choose to use, by all means, use something! No serious project can be written without a VCS. - Steve On Thu, Dec 9, 2010 at 8:55 AM, G. T. Stresen-Reuter <[email protected]> wrote: > On Dec 9, 2010, at 4:33 PM, Eric Ridgley wrote: > >> I've just started working with two other developers on several PHP MVC >> (model-view-controller) solutions for some of our client's websites and I'm >> thinking we need to move to some kind of version control system. Does anyone >> have any advice on what to use? I started looking at Subversion but have to >> admit I'm rather intimidated by implementing it. Any advise on what to use >> or where to get started would be appreciated. >> >> -Eric > > Subversion is actually a good place to start since it does fairly advanced > version control with a minimal learning curve. You can hire subversion > hosting to make the server setup and maintenance easier and then use any > number of GUI Subversion clients (or the Subversion command built into > BBEdit) to interact with the server. > > If I were just starting out with version control at this point I would > definitely go with git. The learning curve is significantly steeper but the > payoff can be inestimable as the one significant feature "lacking" in > Subversion is implemented in overdrive in git. > > In all fairness, though, there are only 2 times in the past 7 years that I > can recall wishing I had been using git, but who knows how much better my > code would be had I fully understood git and been able to take advantage of > it. > > I should also point out that just because you use git doesn't mean you need > to use the advanced (complex) features. It works pretty well as a basic VCS > too ;-) > > My 2ยข. > > HTH, > > Ted Stresen-Reuter > > -- > You received this message because you are subscribed to the > "BBEdit Talk" discussion group on Google Groups. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > <http://groups.google.com/group/bbedit?hl=en> > If you have a feature request or would like to report a problem, > please email "[email protected]" rather than posting to the group. > Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> > -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
