> Thats fine as long as the one abusing the framework does not start > inflicting others with their design choices. Then they go from hurting > themselves to hurting others.
Of course. But that is where I miss a cristal clear vision of what Avalon should be - and one much less abstract than the current ones. If you have such vision in place you can point it to that kind of "abuser" and rapidly stop the noise. Otherwise a lot of energy will be wasted, including the "abuser"'s energy, because he will take longer to realize what he can get and what he can NOT get from Avalon. Regards, Paulo > -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 21, 2002 1:54 AM > To: Avalon Developers List > Subject: RE: [desperate plea] RE: The need for 'hints' > > > At 01:24 PM 6/20/2002 +0200, you wrote: > >I agree. > > > >Avalon should be as "abusable" as possible. > > > >One can always have a strict layer and an abusable one, or > >can we not? Each project would use the most convenient one. > > Thats fine as long as the one abusing the framework does not start > inflicting others with their design choices. Then they go from hurting > themselves to hurting others. > > > Cheers, > > Peter Donald > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > "Faced with the choice between changing one's mind, > and proving that there is no need to do so - almost > everyone gets busy on the proof." > - John Kenneth Galbraith > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
