On Wed, Jul 1, 2009 at 12:40 AM, Tom_G<
springmethods@...> wrote:
>
> Prototype a small part of the application using each technology. Then compare
> the advantages and disadvantages of each.
I like that one - especially in terms of doing things that are
actually the best for the project's success :)
Some measures to check for:
* tool support - do all major IDE's or at least all in use in your
company support the framework?
* learning curve - as well as for getting started a simple project as
for doing more advanced things?
(you could actually find answers on these when doing as Tom suggested)
* Are there well working (security) update processes?
* community support - partly also in the first category - you could
count members on a mailing list, numbers of messages, numbers of
actually answered questions or requests for help (and really think
about what each of these would mean)
* proven production use - are there recognizeable examples of people
using the framework - preferably with similar requirements and
environment as you have?
* long term development chances - will the framework be supported for
the lifetime of your applications?
And then some...
These could be hard to measure, I think, but interesting aspects - I'm
not even sure, which of the two contenders would win there.
G'night,
Henning
--
Henning Sprang
http://www.sprang.de---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
