Re:The Absolute No-Frills Quite Ignorant Incomplete Beginner...
by Rochus on Thursday October 08, 2020 @03:15PM
(#24722706)
Well, you were asking.
Re:The Absolute No-Frills Quite Ignorant Incomplete Beginner...
by igouy on Thursday October 08, 2020 @04:40PM
(#24723709)
From your answers so far, it doesn't seem at-all obvious that were considering disadvantages of "virtual image based systems" rather than particular disadvantages of the ST80 implementation.
Would a Smalltalk image without gui classes not be feasible?
Re:The Absolute No-Frills Quite Ignorant Incomplete Beginner...
by Rochus on Thursday October 08, 2020 @05:26PM
(#24724108)
I spent much of my life in an with Smalltalk images (some would say too much), and there were also the big names and figures when I did Smalltalk projects in the nineties. Some of the issues could be handled spending a lot of money. The basic concepts (and issues) are the same in all Bluebook offsprings. You probably mean GNU ST; it has the advantage that there is a compiler and library available outside of virtual images and you can use it like a "normal" compiled language and easily re-assemble a virtual image with the objects and versions required. This allows you to use the image as a cache to reduce startup times like e.g. Dart does it. But this is not the original Smalltalk virtual image idea, i.e. not the "whole environment" the fellow referred to.
Re:The Absolute No-Frills Quite Ignorant Incomplete Beginner...
by igouy on Thursday October 08, 2020 @06:26PM
(#24724596)
> You probably mean GNU ST
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.
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, …)