Re:Why are Smalltalk images considered bad but Docker images...
by davelnewton on Friday July 29, 2016 @12:49PM
(#12188081)
Because Docker lets you put arbitrary things into an image. Smalltalk images let you put arbitrary Smalltalk into an image.
It's apples and oranges: I can't mix-and-match technologies in Smalltalk images.
(I'd also argue that it isn't so much that Smalltalk images are considered "bad", rather that Smalltalk images don't suit the needs of a lot of people. Or problem spaces.)
Re:Why are Smalltalk images considered bad but Docker images...
by prodigal_erik on Friday July 29, 2016 @02:06PM
(#12188650)
Smalltalk expected the image to hold the authoritative copy of your source code, adding friction to the use of any tools that were not first ported to the Smalltalk you were using (e.g., your favorite editor, version control, code review).
Re:Why are Smalltalk images considered bad but Docker images...
by cpg1111 on Friday July 29, 2016 @11:06AM
(#12187295)
My understanding of Smalltalk is extremely small, but, this is an apple to well a tree, so smalltalk images and docker images are both ways to persist some sort of state at runtime, however, Smalltalk images are more like configuration while docker images are more of an entire environment.
It's apples and oranges: I can't mix-and-match technologies in Smalltalk images.
(I'd also argue that it isn't so much that Smalltalk images are considered "bad", rather that Smalltalk images don't suit the needs of a lot of people. Or problem spaces.)