Sven Van Caekenberghe wrote
This is not that different from the C world I guess.
I think the C world is slightly different in one important respect. In the C world layers are rather cleanly separated from one another: C (or C++) compiler, standard library, framework + application specific libraries. In the C (or C++) world it is possible to - more or less freely - combine compiler A with IDE B, using framework C and external libraries D. After compiling the executable does not depend e.g. on the IDE anymore. In smalltalk, if I decide to use dialect A then I feel more or less bound to using library A, IDE A and GUI framework A. The program still depends on the image type I was using in development (or even on the VM) unless I limit myself to a well-defined kernel like ansi which doesn't provide portable graphics + network APIs. My tool developed in squeak 4.1/pharo 1.1 in this spring does not run in squeak 4.2/pharo 1.3 without modifications. -- View this message in context: http://forum.world.st/portable-smalltalk-how-tp4118832p4156504.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.