>On 5/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>I'd love to see more comments. Honest comments about your experiences
going
>from 3 to 4, your thoughts on better adoption, how you feel about
Tapestry 5
>(especially if you are in a situation where you'll need to upgrade).
Please
>avoid any comparisons of Tapestry to other frameworks (that just causes
>flame wars).
Answering without some comparisons to other frameworks is very
difficult, because people base their evaluations on their experience. In
the ten years I have been developing web apps I have used many decent
web technologies including .Net, Perl, ColdFusion, and each of these
platforms had stuff I liked, and so too does Tapestry.
I personally believe the secret to adoption is 1. Ease of use, and 2.
Productivity. Tapestry in my opinion is neither. Needless to say this
comment I sn't intended as an insult, because Tapestry is a wonderfull
framework and does many things far better than its competitors, but I am
not an idealist... I prefer like most people just to get my work done as
quickly and efficiently as possible.
Tapestry 4 was not easy to use because of the following: a lack of
quality and up-to-date documentation; a lack of working examples; a
shortage of published information; too much configuration; too many
dependency and deployment problems, and worst of all the class reloading
inefficiencies.
Improving Tapestry is not just about the technology, but also about all
those very time consuming extras that surround it. Tapestry 5 is awesome
in comparison to 4, I would even say that the new class reloading
mechanism is totally innovative making it so much more productive than
version 4, but this is offset by the time it takes to get everything
going, getting all the configuration and deployment issues sorted, and
of course not having a good online reference to work with as a start. Ok
granted Tapestry 5 is still in pre-release, but if it goes anything like
Tapestry 4 then I am sure I will feel more of those dark moments as my
deadlines approach and I am stuck on some issues that aren't documented.
I originally scheduled an upgrade to Tapestry 5 this month, but I had to
push it back for a while until I feel confident enough about 5. Our
software systems are already running on Java 6 which also appears to be
an obstacle, especially in development so I am stuck with 4 until it is
resolved. Although this now leaves me with the problem that we have to
keep developing new features in 4 so upgrading is becoming more and more
difficult as time goes on.
Best wishes,
Peter
--
Peter Stavrinides
Albourne Partners (Cyprus) Ltd
Tel: +357 22 750652
If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Please visit http://www.albourne.com/email.html for important additional terms relating to this e-mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
