> From: Leo Sutic [mailto:[EMAIL PROTECTED]] > > > From: Leo Simons [mailto:[EMAIL PROTECTED]] > > > > > Leo Sutic wrote: > > > > Carsten, > > > > > > > > you are right - everything gets a little bit more complicated. > > > > > > > Yes, and this is the thing that worries me - I know a lot of people > > > saying "Avalon is too complicated" and this makes it even a > > > little bit > > > more complicated, > > > > hmm. Is it more complicated? > > As Vadim said in a comparison of Cocoon and Struts: Cocoon developers > come from the "pattern hell" school of thought. (That was a point > against Cocoon, if anyone missed it.)
It was not me! :) > Worth thinking about, as I have seen some people here accusing > Cocoon of not following patterns cleanly enough. > > As a matter of fact, I think we scare the shit out of most people > with the complexity of the framework already. Patterns within > patterns... It is not whether there are patterns or not - it is > the fact that you have patterns of patterns, and you must somehow > grasp them all. > > So I completely understand Carsten. We will lose users. I see > before me someone saying "F*** it. (1) They are obviously not committed > to API stability, (2) just about when we've finally learned to use > the framework (given how complex it is that may be a while), the next My current client isn't even there yet :) > change will come along, > (3) the cost of maintenance and keeping up > with that will kill us. Let's roll our own framework." > > If it is more complicated or not does not matter - what matters is > what it is *percieved* as. > > For all its faults, A4 is *easy* to *use*. (Although I confess I never > ever understood the RoleManager.) Automatic pooling and transparency of component implementation to client is two great features I like most in A4. Vadim > /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
