updates vs. images -- limiting squeak to code

Michal michal-list at auf.net
Thu Oct 13 08:49:19 UTC 2005


> Isn't the real point that it should be relatively easy to transfer
> this stuff from image to image? 

Maybe it 'should', but in actual fact transferring non-code objects is
*harder* than transferring code in current Squeak. That's because
there is a lot of infrastructure dedicated to code (changesets, the
.changes file, mc, etc.) but very little dedicated to non-code.

So de facto, if you kill smooth upgrades (which is what we are talking
about), you come close to killing the use of squeak for non-code
objects. Modifying my initial reaction slightly: please don't kill
updating images, unless you have solved the issue of "easy transfer
[of] this stuff from image to image". (Though I suspect that when
you've solved that, you've also solved the initial problem about
upgrading code ;)

Michal




More information about the Squeak-dev mailing list