On 29 January 2012 18:48, Philippe Marschall <kustos@gmx.net> wrote:
On 29.01.2012 17:02, Sven Van Caekenberghe wrote:
On 29 Jan 2012, at 15:30, Philippe Marschall wrote:
As for scale.. monticello scales well.
No, it does not.
Please elaborate: I really can't see the difference between doing a merge (either an easy one or a more diffucult one over multiple files, spread over a couple of days, with intervening changes by others) using either Monticello or Git.
The scalability limits of Monticello are well understood. PackageInfo doesn't scale, at all. You put too many classes in a package, and snapshotting gets really slow. Don't believe me? Make a change in Morphic which has only 200 classes and save it.
so don't make too many classes in one package.
And it's not like loading is any faster. Seaside takes 10 minutes to build from locally cached [1] packages, only 12 seconds go to running tests [2]. This makes C++ compilation times seem fast by comparison.
Bah.. read this http://marianopeck.wordpress.com/2011/09/24/importing-and-exporting-packages... Soâ¦. if you have followed the previous steps, then just open âFuel.imageâ (a new Pharo 1.3 image where Fuel is loaded but seaside is not), paste the previous code into a workspace and execute it. Of course that it depends on the machine, but here (Mac Book Pro i5), it only takes 10 seconds. And we can store packages serialized by Fuel. Actually we're not speaking about scale in same sense. It is not about package size or time they load (i can always put an infinite loop in one of #initialize methods of my class, so it will take an infinite time to load a package with it ;) , but putting a bunch of developers to work on a single project. MC has some deficiencies, but not in that regard.
 [1] http://jenkins.lukas-renggli.ch/job/Seaside%203.1/buildTimeTrend  [2] http://jenkins.lukas-renggli.ch/job/Seaside%203.1/lastCompletedBuild/testRep...
Cheers Philippe
-- Best regards, Igor Stasenko.