> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
>
> You know what?
> I would REALLY like to see AF 5 be a big fat bugfix release
> with regards
> to A4.
>
> That is:
> - real-life examples, with ready to use containers (Merlin,
> Phoenix, etc)
> - better interfaces, like the Service ones, based on real life needs
> (not only mental masturbations)
> - Examples, examples, examples, examples
> - Usecases, usecases, usecases, usecases
> - Documentation with images, images, images, images
>
> It will have to *look* new, but will be what AF4 wshould have
> been all way long.
>
> If we change interfaces too much again we will loose our
> users. We will. Believe me. Many told me.
>
> This is not a rant but a proposal.
> I want to see votes on this proposal, because we are playing with the
> life of this project.
OK - can you rewrite your points as a proposal. That is, what
exactly is it you are proposing? Especially "better interfaces"
is a bit vague in combination with "If we change interfaces too
much again we will loose our users."
I agree with your vision, I think, but I'd like you to
specify exactly what that vision means in terms of Avalon code:
What interfaces do we change, and how? What else needs to change,
and how?
That said, I think we do need a bit more user-orientation and less
obsessiveness about what consitutes "good architecture" and "proper
SoC, IoC" and other fancy terms... Sometimes I think we're getting
a bit overboard and justify our architecture with statements regarding
what we consider "good architecture/philosophy etc." and not in terms of
how good and useful for our users. If this is the "less wanking" point
on Nicola's list, then I am
+1
just for that reason. I think we risk building all these air castles
that no one will ever find useful irrespective of how mathematically
or academically correct they may be unless we start checking ourselves.
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
