Hi,
(this contribution is more related on Avalon
Framework)
I think the main problem with every framework
is that there are so many of them. Every has
the claim to be the one and only. And they
come and go (don't kill me now). I know
developers (Seniors) which refuses every
framework. They say, that frameworks steals
flexibilty and that they are producing more
problems as solutions.
Why?
Because there are ones which are so strict that you
have no flexibility as developer and there are
others which are so academic that you can't
use them.
What we need is something in the middle. Something
which takes away that annoying stuff from you as
developer, give you enough flexibility to react
one changing requirements (everybody in the project
business knows what I'm telling here)
and easy/quick to implement ('cause time and money
rules the world outside).
I think Avalon is going the correct way:
- it's flexible (you can use bits or the whole
thing)
- when it's correct implemented you can do a
very quick development.
- it's like developing by contract. This is the
point I like much. Because that's what we need
between devs in one team!
The obligative pathetic conclusion:
"Keep rolling and stay in touch with the real world"
Cheers
Gerhard
-----------------------------------------
All my life I wanted to be someone;
I guess I should have been more specific.
(Jane Wagner)
-----------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
