I much prefer more modern languages that allow you to explicitly name the parameters when you need to, but other than that, never requires it (e.g. Kotlin and Swift).
I much prefer more modern languages that allow you to explicitly name the parameters when you need to, but other than that, never requires it (e.g. Kotlin and Swift).
For instance, seeing "public static void" all over the place in java is irritating.
On the other hand, if I'm doing a code review and I can't do a quick "jump to definition", I'm much happier reading code like:
t rotateAround: v by: 90 degrees toRadian.
Vs. t.rotate(v, 3.14/2)
Sure the former is slightly more verbose (not by much though), but it tells me so much more and I don't need to look anything up. Also even though it's longer, none of it is fluff or ceremonial.Yes, Java is excessively verbose. No disagreement there. But so is Smalltalk.
Your argument is basically whataboutism.
My point is that Kotlin and Swift both solve Smalltalk's mistakes elegantly by making the parameter name optional. Use it if you have to, but omit it otherwise. And as it turns out, most of the time, you don't need to mention the name at all.
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?