[Pharo-project] Smalltalk for small projects only?

Sven Van Caekenberghe sven at beta9.be
Sun Jan 29 13:16:51 EST 2012

On 29 Jan 2012, at 18:48, Philippe Marschall wrote:

> 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.
> 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.
> [1] http://jenkins.lukas-renggli.ch/job/Seaside%203.1/buildTimeTrend
> [2] http://jenkins.lukas-renggli.ch/job/Seaside%203.1/lastCompletedBuild/testReport/

I thought the thread and your remark were about the fact that it was functionally not possible to scale to larger teams. That is where is see no real difference.

If you refer to scaleability purely on technical terms, speedwise, then yes we have room to improve ;-) 
I worked with Pharo slices, I have built images containing Seaside.
Building bigger well known open source software from scratch usually takes quite some time too.

We, as a community have to improve our tools, it will be a lot of work but work _is_ being done right now, think of the compiler, loader, networking, file access, package management. 

This very small hack already makes a difference: http://code.google.com/p/pharo/issues/detail?id=5222 and we need many more.


More information about the Pharo-dev mailing list