+1 on this point of view On Feb 1, 2014, at 7:09 AM, Pharo4Stef <pharo4Stef@free.fr> wrote:
@ Igor
I guess that I know pretty well poolDictionaries I do not need an explanation. I even found bugs in the previous lookup and now we have recompilation bugs when changing pools.
Now how many times gave one lectures to newcomers? Why do we have new calling initialize? Because after first lecture we HAD to explain metaclasses. Do we want to continue to stay a close club of smart asses?
NOOOOOOOOOOOOOOOOOOOOOOOOO
NOT ME at least
@others
Now people hear me well: you are ready to hear well. Lower the music
WE WILL change the class definition in Pharo 4 because we want slots. So be prepared.
This is not because you did not read nor type this class definition since years (because you do not even look at it) that - it will not change - students do not get overhelmed with it.
I DO NOT WANT MY SONS TO PROGRAM IN PYTHON/RUBY/JS BECAUSE THIS IS âEASIERâ. Is it clear? It is BORING to have to say to kids: - do not care of classvar - do not care of pooldictionaries
COME ON when can we open our eyes? So yes Iâmad at the lack of vision **you** have. But do not worry I have the vision for Pharo. If you do not like it, I cannot do much for you. Continue rambling how cool was smalltalk 30 years ago. Not me. We are INVENTING the future here.
So please focus your energy on how to make pharo simpler, nicer and sexier.
Stef
---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile