@ 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
> Guys, can you explain me, why you hating pools so much?
> Because you cannot find good use of them, or because you don't know how to
> properly use them? Or because you don't understand what is it?
>
> Pool dictionary is just a namespace, which you can share among different
> parts of your code (on a per-class basis).
> And one of most used form of it is a global one, where all public classes
> are.
> The only difference is that access to global pool is implicit (you don't have
> to mention it in class definition), but it has same nature as shared pool.
>
> As long as you need to give names to things you using, you gonna need
> namespaces/pools.
>
>
> --
> Best regards,
> Igor Stasenko.
