Hi everyone,
I would like to have your vote on this design constraint on Avalon 5:
all possible efforts should be done to avoid avalon forking
The rationale behind this is *very* simple:
if you make it *harder* to use Avalon and you simply use elegance
reasons, people won't follow you and keep what they have. Then, needs to
change emerge and two different branches are setup.
This is bad enough for applications (see Tomcat 3.x vs Tomcat 4.x or Ant
1.x vs Ant 2.x) but it would be *terrible* for APIs, it would simply
kill the project.
When you are designing something new, you must make it appealing for old
users to switch, because that take time energy and effort.
Many of the proposals I've see so far go toward the 'elegance cleanup'
direction and very few to the 'usability/functionality' direction.
If we keep this direction, nobody will switch to Avalon 5, they will
simply keep on patching Avalon 4 and all our effort is useless.
So, what do you think?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
