On 30 Jan 2014, at 20:03, Eliot Miranda <[email protected]> wrote:

> 
> 
> 
> On Thu, Jan 30, 2014 at 10:58 AM, Esteban Lorenzano <[email protected]> 
> wrote:
> 
> On 30 Jan 2014, at 19:43, Torsten Bergmann <[email protected]> wrote:
> 
> > I checked: it was introduced in update no. 30711 with #issue 12163
> > including the following statements:
> >
> >> "Who uses poolDictionaries? I suspect extremely few of us."
> >> ...
> >> "It would be a bit cleaner. I know us old timers don't even see the  
> >> poolDictionaries: line anymore, but >I dislike having to explain it to 
> >> students."
> >
> >
> > <humor>
> > I would also vote for not displaying Traits anymore. It confuses me when I 
> > see them.
> > Instance variables are also overvalued - we should remove them from the 
> > default
> > template too. It's just too confusing to have them there.
> >
> > And categories now make no sense either - we now have real packages. Let's 
> > remove them
> > since nobody understands them.
> 
> he, humor or not, is our objective to replace them for real packages. Is just 
> that we still do not have the time :)
> 
> So VMMaker will get completely broken :-(.  Has everyone forgotten IIABDFI?

it will be compatible, when we do it… and will be compatible for a long time. 
but don’t worry, in any case it will not happen in a really *long* time :)

and the problem of brokenness, is that it depends a lot on points of view and 
purposes. 

Esteban


> 
> >
> >    Object subclass: #Foo
> >
> > would be much easier to understand! Maybe we should remove superclass as 
> > well - lets
> > inherit from Object. Would also avoid deep hierarchies like Morphic ;)
> > </humor>
> >
> > But for real:
> > If it is too complicated for students one could build a custom "teaching" 
> > image.
> >
> > From the info I see on the issue tracker it sounds to me like an "academic" 
> > change
> > - still do not understand the real reason...
> >
> > Bye
> > T.
> 
> -- 
> best,
> Eliot

Reply via email to