3 ms·
> … nontrivial to extricate a finished program from the environment and ship it to customers in a "tamper-proof" opaque form. 1) source code management Even a
by igouy 4y ago
> … nontrivial to extricate a finished program from the environment and ship it to customers in a "tamper-proof" opaque form.
1) source code management
Even ancient Smalltalk-80 provided —
"Within each project, a set of changes you make to class descriptions is maintained. … Using a browser view of this set of changes, you can find out what you have been doing. Also, you can use the set of changes to create an external file containing descriptions of the modifications you have made to the system so that you can share your work with other users.
…
The storage of changes in the Smalltalk-80 system takes two forms: an internal form as a set of changes (actually a set of objects describing changes), and an external form as a file on which your actions are logged while you are working (in the form of executable expressions or expressions that can be filed into a system). … All the information stored in the internal change set is also written onto the changes file."
1984 Smalltalk-80 The Interactive Programming Environment page 461
https://rmod-files.lille.inria.fr/FreeBooks/TheInteractiveProgrammingEnv/TheInteractiveProgrammingEnv.pdf https://rmod-files.lille.inria.fr/FreeBooks/TheInteractivePr...
2) deployment
Not all software was shrink-wrap — plenty of high-value enterprise software.
- walnutclosefarm 4y agoSmalltalk images were fine for one-person development of single programs. Not really very manageable for teams, and modular development though. Not that these things couldn't be done - we certainly did it at IBM, when SmallTalk was the "thing" there for a while - but it never was very satisfactory. A lot of developers significantly younger than me seem to think that source code control was developed in the the last couple of decades, but in fact we did source code control, modular development, and build pipelines way back in the 70s - mostly with home built tools, but the capabilities began to be built out as soon as source code left card decks for permanent residence and in place modification on rotating storage. And SmallTalk was at best hostile to all those techniques.
- igouy 4y ago> … at best hostile… Strange that you don't mention ENVY/Developer? Method-level source-code version-control and configuration-management implemented for VisualWorks, IBM Smalltalk and Digitalk. "Mastering ENVY/Developer" https://www.google.com/books/edition/Mastering_ENVY_Developer/ld6E19QIMo4C?hl=en&gbpv=1 https://www.google.com/books/edition/Mastering_ENVY_Develope...