Comment by shevy-java

10 hours ago

That part is also cool. I'd like this in ruby too, e. g. where we could have tons of objects reflect on that state, and just resume work there. Everything is an object. Squeak everywhere, but to also retain the "scripting" (light) commandline approach. Nobody in smalltalk really understood why "scripting" is important. Python showed why.

1 comment

shevy-java

igouy 7 hours ago

> also retain the "scripting" (light) commandline approach

Smalltalk developers preferred to do their scripting within the Smalltalk IDE, so they could use their familiar tools.

And then save their "scripting" as a text file ("fact.st").

    $ cat fact.st
    Stdio stdout 
        nextPutAll: 100 factorial printString; 
        nextPut: Character lf.!
    SmalltalkImage current snapshot: false andQuit: true!

And then "run" that text file ("fact.st") from the commandline.

    $ bin/pharo --headless Pharo10-SNAPSHOT-64bit-502addc.image fact.st

93326215443944152681699238856266700490715968264381621468592963895217599993229915608941463976156518286253697920827223758251185210916864000000000000000000000000