I agree with what you've said here. I actually use ST to illustrate the relationship between patterns and languages. "Fluent Interface" is the name of a pattern

I agree with what you've said here. I actually use ST to illustrate the relationship between patterns and languages. "Fluent Interface" is the name of a pattern wherein methods that are executed for their side-effects return the receiver, and callers then chain methods to a single receiver. This encourages writing many small methods while keeping code clear. It is not necessary in ST, because ST's syntax includes the semicolon operator for cascading messages to a single receiver. In effect, the pattern is "baked into the language."