Hi Torsten,
I think it is a design decision / tradeoff, and therefore there is no fundamentally "right way" to do it. For me, it is the same case as the uses: message for Traits. It's not in the template by default because it is used very infrequently. So for language simplicity it should not be there. For me, simplicity is one of the core points of Smalltalk so this is why I feel strongly about it.
I donât see how this change make Smalltalk (the language) simpler. For me this change looks more like an obfuscation than a simplification.
How many lectures did you give? It is annoying to have to explain something that usually people do not need to know.
When I say "very infrequently", this is of course a fuzzy metric, I know. And I understand that you do not agree with this design decision.
But on the other hand, I don't think that it is too hard to remember where to add the pooldictionaries: line if you need it, and the old message with this line still works, so all old examples still work.
How should newcomers know how to enter pool dictionaries? I rarely use pool dictionaries and if I will need it I surely have forgotten about this change and expect irritation and frustration.
Newcomers do not use pooldictionaries. In 10 years smalltalking I used them twice.
So, a -1 for this change from my side.
We just need a full class template menu item.