3 ms·
> The first complaint that you'll hear about St is: "where are my files and version control?" More like "Where's the program?" Early '80s Smalltalk did use ch
by igouy 5y ago
> The first complaint that you'll hear about St is: "where are my files and version control?"
More like "Where's the program?"
Early '80s Smalltalk did use change-sets in files.
p462 "Smalltalk-80 The Interactive Programming Environment"
https://rmod-files.lille.inria.fr/FreeBooks/TheInteractiveProgrammingEnv/TheInteractiveProgrammingEnv.pdf https://rmod-files.lille.inria.fr/FreeBooks/TheInteractivePr...
----
You're right, Smalltalk is about "modifying objects that represent classes and methods" rather than editing files.
So versioning means fine-grained "classes and methods" rather than versioning files.
https://www.google.com/books/edition/Mastering_ENVY_Developer/ld6E19QIMo4C?gbpv=1 https://www.google.com/books/edition/Mastering_ENVY_Develope...
----
You're right, we know what we like - we like what we know.
So (Pharo) "Manage Your Code with Git and Iceberg"
https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-Ma...
- diegof79 5y agoThis wasn’t a critique to Pharo. Don’t get me wrong I worked using Smalltalk professionally for 3 years, and I contributed a small library to Squeak and Pharo. My comment was about how difficult is to innovate in areas like the file system. Pharo had to use git because is popular, not because is the best way to handle object versioning (eg Envy was much better at handling the history of your classes)
- igouy 5y agoI understood that the Smalltalk remarks were kind-of incidental to the point you wished to make. So just some clarification for readers stuck at the big-blob Smalltalk no-version-control meme.