But let's not temper wild-and-crazy _too_ much.  Classes are just
objects in the system.  I would not want to discourage it if some
really dynamic system that "enhances itself" could be reailized, even
if it resulted in 10 thousand dynamically-generated classes..

Ok, one would think there would be a better organization of behavior,
but a similar point can be made about Tweak. Doesn't it blaze new
trails in its use of Processes and perhaps also pragmas?  (Sorry, it's
been years since I looked at Tweak).

I continue to be amazed at the creative implementations this community
puts out; like Generators and piping and Continuations, etc.



>> Generally speaking, yes. If you dump everything in a single class or two
>> then you're going to end up in a mess. However, if most of your classes
>> end up having a single method or two for no tangible benefit, there's a
>> bad smell there as well.
>
> Exactly. Extremes are always bad. And both extremes lower the simplicity
> and therefore maintability of the code and specially, comprehendibility
> by newcommers. That's why also wanted to show with my code stats
> comparison between Aida, Seaside and Iliad:
>
> https://spreadsheets.google.com/ccc?key=0Atnb1W9vuq9ndG4wbUpxNXpKQnFZRlFyQXpHclhZa2c&hl=sl#gid=1
>
> >From "Methods in classes" distribution graph, then from number of
> packages and categories you can clearly see two schools of thought here.
>
> I of course claim that Aida "school of thought" with its balanced
> distribution of code between methods, classes, categories and packages
> is more comprehensible and therefore more simple.
>
> Best regards
> Janko
>
> --
> Janko Mivšek
> AIDA/Web
> Smalltalk Web Application Server
> http://www.aidaweb.si
>
>