> From: Adam Rossi [mailto:[EMAIL PROTECTED]]
>
> Almost everything I
> have seen as to Avalon organization can be made simpler. It
> sounds like everyone agrees to this, but it also sounds like
> there is resistance to change.
Adam,
there is concensus as to that things can be made simpler. But
at least what I am afraid of that we will give up something by
simplifying. Things are complex for a reason, and unless we
know that our new solution solves the old problem that the
complexity was supposed to solve, we can't commit to it as
we would only repeat the previous cycle.
That, I think, is reason for much of the inertia.
> I am an outsider and new to Avalon, which means I have the
> gift of objectivity. I am not privy to political constraints
> or technical limitations.
As someone who has a clue about the technical limitations
and the politics, I can come up with a 80% solution that can be
100% implemented, as opposed to a 100% solution that can only be 80%
implemented. And I think politics will be the major factor in
coming up with that solution. Sad but true.
> I am just telling you that getting
> started with Avalon is extremely difficult, even for seasoned
> Java developers.
It is, and we have the same goals. Want to join in on it?
/LS
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
