Hacker News new | ask | show | jobs
by igouy 18 days ago
> … so that, when you look at an image, or when you use it, browse the code, you can easily see what are changes and what is the base image…

You seem to be asking about something that is in documentation from 1984.

http://stephane.ducasse.free.fr/FreeBooks/TheInteractiveProg...

> i am not suggesting that smalltalk needs to be changed…

Smalltalk has been changed, several times.

"With ENVY/Manager the image becomes a discardable by-product of development, secondary to the repository that stores and coordinates all work."

https://www.google.com/books/edition/Mastering_ENVY_Develope...

"The way ChangeSets are created and managed in Cuis is different from Squeak."

https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/blob/ma...

1 comments

thanks. it's going to take a while to find time to read those. likely longer than the two weeks available to reply here. let me just say that my experience with smalltalk is limited to playing with squeak and doing some coding with pharo. (i made some video workshops life coding through some tasks, if you are curious).

i am also not suggesting that smalltalk can't be changed, just that i didn't want to assume that my suggestion is the right way, and has to be done, or else. more like: how about this? is that feasible?

cuis is interesting, there are other branches that i find interesting too, such as strongtalk. it's a pity that they receive even less attention than smalltalk itself.

i wish i had more opportunity to work with smalltalk, but nobody is hiring ;-)