Explicit? Sure.
But verbose?
There's no good reason for that, except that when Smalltalk was designed, we thought it was a good idea.
We know better today.
Explicit? Sure.
But verbose?
There's no good reason for that, except that when Smalltalk was designed, we thought it was a good idea.
We know better today.
What if you are a "sometimes" programmer -- you write some code, then come back to it months later. In many ways this was the intent behind the development of early personal computing. Verbosity is an advantage in these cases because in theory it becomes easier to discern what is going on without having to be immersed in the language, frameworks, and environment all the time.
Keep the verbosity to a minimum while making the code easier to read, understand, and maintain.
There is not an objective universal boundary between explicit and verbose. Some readers will need more, some can guess correctly with less.
Usual method in Smalltalk, including its definition, is shorther than this sentence.
Do you mean in base Pharo, or do you mean in an enterprisey system built using Pharo?