[igouy]

Do you understand that you are not answering `virtualized`s question?

The question is not about a Pharo commandline that exists as part of the Pharo GUI.

The question is about an OS commandline like "GNOME Terminal" with stdio.

[detaro]

They do. By saying "there is such functionality, but you should try this instead, because using it from commandline won't tell you why this is interesting". Which isn't directly answering the question, but pointing the asker in a good direction.

[igouy]

Until the asker has been shown that their commandline requirements can be met — they will not be interested.

[goatlover]

But it's entirely missing the point in that you don't use a Smalltalk environment so that you can run some hello world example from the command line.

[igouy]

A simple hello-world command-line example may be used to demonstrate:

— How to run a Smalltalk source code file as a script

— How to use stdio, How to use file handles

— How to load Smalltalk source code from files, save, deploy , and invoke on remote machines

Until `virtualized` has seen that basic stuff can be done, why should they care?

[goatlover]

But this is about Pharo, which is a Smalltalk environment, which is different from how most programing languages are used. So starting from those kinds of questions is missing the point, when the focus should first be on seeing what makes a Smalltalk environment different.

[igouy]

> a Smalltalk environment

A Smalltalk implementation.

> So starting from those kinds of questions is missing the point…

The questions `virtualized` asked are simple and clear.

Telling `virtualized` that they are missing the point — instead of answering their questions — makes the community seem arrogant.