3.0 is great. 3.1, which is coming up on it's first alpha will
streamline a lot of the more difficult aspects of Tapestry. For
example, you won't have to declare the types of properties in page and
component specifications and there will no longer be different
parameter directions for component parameters. In addition, HiveMind
will be built-in transparently, taking care of services and
configuration points.
At Darden Solutions (Darden is the University of Virginia's Business
School, and DS is a software group there), we have built our whole
suite of applications (except Alumni) using Tapestry 3.0.x and have
been extremely happy. The productivity gains over Struts (used for
Alumni) are fantastic, and the reuse of components is as well.
Jamie
On Feb 17, 2005, at 5:57 PM, Kevin Menard wrote:
> Hi Jonathan,
>
> On Feb 14, 2005, at 3:15 PM, Jonathan Carlson wrote:
>
>> Personally, I care more about productivity than saving a few megs of
>> memory. Granted, I'm sure Tapestry development is fast too, but I
>> got a
>> little frustrated with trying to scale the learning curve of the
>> required XML markup stuff in Tapestry a few years back.
>
> I don't know firsthand, since I started using Tapestry with the 3.0
> release, but from what I gather, 3.0 is much nicer to the developer
> than previous versions. The forthcoming 3.1 is supposed to be even
> more so.
>
> --
> Kevin
>
This archive was generated by hypermail 2.0.0 : Thu Feb 17 2005 - 22:12:03 EST