Just the development tools included in the base Smalltalk implementation — we can choose whether or not to include other stuff.
> Of course it doesn't matter for …
Apparently, it doesn't matter for the whole range of business critical applications that do not need to be DO-178 certified.
> In ST80 source code is just an external dump file …
Do you mean that in ST80 source code can be saved as a text file and versioned like other text files?
> Bootstrapping a virtual image …
We can use a base virtual image someone else implemented. (Like we use a JVM someone else implemented, …)
Would a Smalltalk image without gui classes not be feasible?
I mean that "deploy all development tools used to develop the software" seems to be a separable from "Bootstrapping a virtual image from source code in ST80 is very difficult or nearly impossible".
bootstrapped image + libs + gui + tools + app ==> development environment
bootstrapped image + libs + gui + app ==> gui deployment
bootstrapped image + libs + app ==> headless deployment
> smalltalk is not just a language, but a whole environment
I mean could the fellow have his "whole environment" for development - and - have his no-gui no-ide boostrapped image + libs + app for deployment.
Well, not every software manufacturer want's to deploy all development tools used to develop the software and possibly code which is only meant to be used inhouse. And if you e.g. deploy to safety-related targets you even have to demonstrate that there is no "dead code" (e.g. DO-178). Of course it doesn't matter for hobby or non-critical applications.
> So application source code isn't just text that can be saved in text files and versioned like other text files
In ST80 source code is just an external dump file; the actual configuration unit is the virtual image. Bootstrapping a virtual image from source code in ST80 is very difficult or nearly impossible.