No one needs to read this site. Publishing this content is meant to force me to research new things, thus helping me to grow as a developer. If you think the things I post about are cool, then well... cool. If not, no big deal.
Thursday, May 13, 2010
Git
Git is so much easier to work with than subversion, it makes me wish we had switched sooner.
For complex web sites, I was just reading Paul Hammond's "Always Ship Trunk: Managing Change In Complex Websites" (http://en.oreilly.com/velocity2010/public/schedule/detail/14145 and the slide pdf at http://www.paulhammond.org/2010/06/trunk/alwaysshiptrunk.pdf)
(forgot to finish the thought!) It talks a bit about how GIT is better than Subversion for branching and merging, but both (all version control) are designed for software that is installed on each target machine. He argues that Web Services are different and better served by supporting branching-in-code. i.e. using if/then checks to select different versions on the fly. Not sure how well that would work, but I'd still want some code repository.
For complex web sites, I was just reading Paul Hammond's "Always Ship Trunk: Managing Change In Complex Websites" (http://en.oreilly.com/velocity2010/public/schedule/detail/14145 and the slide pdf at http://www.paulhammond.org/2010/06/trunk/alwaysshiptrunk.pdf)
ReplyDelete(forgot to finish the thought!)
ReplyDeleteIt talks a bit about how GIT is better than Subversion for branching and merging, but both (all version control) are designed for software that is installed on each target machine. He argues that Web Services are different and better served by supporting branching-in-code. i.e. using if/then checks to select different versions on the fly. Not sure how well that would work, but I'd still want some code repository.