Hi Stef,
Now people hear me well: you are ready to hear well. Lower the music
Beside the fact that I like listening to loud music I really lowered it ;) But even with silence in the room your response told me nothing new regarding the topic discussed. It is not a discussion about "who has the vision" or "who want to get stuck" I think we all share the SAME VISION to move forward with a fresh dynamic programming environment and are not afraid if we move away from our original roots. Otherwise we would'nt be on this list or do even radical changes. Therefore: please stay on topic and stop arguing by pointing to visions because it will move us away from the original discussion and one can easily get the impression that opposite opinions on the topic are cut down as if people are either grumpy old Smalltalkers or betrayers on the Pharo movement - which is simply not the case! So lets continue discussing about the topic - because I see no violation agains the Pharo vision here. ---------------- OK, back to topic and to summarize: we now all fully understood that the original message including pools is still there, will not break code loading or other things and that the change is on the Nautilus level. But still the simple question left to be anwered here: what will this change of reducing the class template in the default browser give us? What problem did it really solve? The answer given so far is that it may be problematic when teaching because you want to introduce to language features step by step. But you said yourself in your own post that <quote> It is BORING to have to say to kids: - do not care of classvar - do not care of pooldictionaries </quote> So my question: if you are bored of the "complexity" of BOTH (!) - why do we hide pools now - and leave class variables still left in the template? I really do not understand because with the change it now looks in Pharo3.0 Latest update: #30732 like this: Object subclass: #Foo instanceVariableNames: '' classVariableNames: '' category: 'Bar' So why do we keep class vars then? According to your mail we would have to remove them too. Additionally this change violates the intention of a template (which one usually just has to fill out) and one now has to remember the original full keyword and have to type it in again - which is IMHO really awkward and stupid. So with all respect: I still can not see the introduction of the reduced template as a step forward or an improvement. Music is still lowered and ears are all open... Thx T.