Do not base your decision based on the quality of the interface, but
based on the quality of the model. If the model fit yours, then
it's a fit for you. I doubt cvs/svn will be a fit for you based on
your distributed / disconnected nature of your workflow.
I will say that git is very cool, but workflow DOES make a huge
difference ... I haven't switched to GIT for our primary revision
control mainly because of this. For someone starting out, git is
pretty complex, and the best way to mitigate complexity is nice tools
integration. Someone mentioned it earlier, egit is a start, but it's
not there, yet. On the other hand, the SVN and CVS plugins in Eclipse
are excellent. For many scenarios, CVS/SVN are just fine -- certainly
coming from nothing, they would be a huge benefit. If you're a
hardcore commandline person and you like reading sorta-ok-tutorials
online, then git is very cool. If you'd rather have nice tool
integration, for now, I would recommend CVS/SVN.
I do agree, though, that your partial disconnectedness makes CVS/SVN a
bit of a tougher workflow. However, I would be nervous of turning you
off to version control by going to git out of the gates ("Brought to
you by the Makers of the Linux Kernel" :) ).
It matters far more that you use version control than which version
control you use, though.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
