On Fri, Jan 28, 2011 at 11:59 PM, Ted Byers
From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Eric J. Holtman Sent: January-28-11 8:56 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] What's happened to Ryppl?
You can check in while you work. Which means you don't have to worry about "breaking the build", or anything like that.
Write some code, test it, seems to work, check it in. Come back after lunch, discover it's fubar, revert. Lather, rinse repeat.
This may be adequate IF you're working alone and if you have all the time in the world, but it will become an unmaintainable nightmare when the number of programmers contributing to the project increases significantly and as time pressures grow. Imagine the chaos that would result from this if you had a dozen programmers doing this independantly to the same codebase.
One project to look at: Linux. Time pressure? Couple of weeks to merge upstream. Programmers contributing to the project? Thousands. Programmers doing this independently on the same codebase? Absolutely. 'nuff said. [snip tl;dr] -- Dean Michael Berris about.me/deanberris