You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Brian K. Wallace" <br...@transmorphix.com> on 2006/05/16 17:51:00 UTC
Relaying observations
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I pondered the right way to relay the following and decided this might
be the best. This is not meant to do anything other than relay
information, but if you see a correlation between statements I've made
and these observations there's a definite reason why.
The following were comments and observations I was given as part of a
postmortem on a project I just wrapped up. They are customer comments,
but I was given permission to relay them directly to whomever I felt
might want to know:
Background: They are sold on Tapestry - 3. They will not move to 4
unless there's a driving need due to monies expended to implement their
current solution (they rolled their eyes at the mention of 5.0 stating
the benefits didn't outweigh the costs) and lack of tooling. The
"initial learning curve" was discounted as it was completely different
from their previous framework and learning curves are everywhere -
although I did point them to Kent's book and sold them on that (Thanks
Kent!). The did feel this level of information should have been
considered part of the overall tutorial/example documentation.
Pros (for choosing Tapestry):
1. Tapestry allows separation of concerns
2. Component design allows different parts of the agency to have
access to a library of components
3. Web interface designers do not need to know anything except HTML
(conversely, Java developers do not need to know HTML)
4. Strong community support
5. An Apache project
Cons with moving forward (to future Tapestry versions):
1. Codebase changes too radically between releases (this comment was
made in discussions about 4.x and comments made about 5.0 - this brought
up more conversations about "initial learning curve" with switching to a
different framework having the same name)
2. Lack of documented reasons for change (they don't sharpen pencils
without documented reasons - and before the jokes fly, yes - they do
still use pencils :-))
3. Too many ways to do the same thing (too flexible: w/ regard to
Annotations vs. XML in 4.x conversations)
4. Lack of first-class tooling support within the framework
(discussions on Spindle - which they love in T3 [thanks Geoff] and its
lack of support in T4)
5. Perceived to be a "consultant's framework" in that it changes
enough - and (back to the tooling) without tool support - that only
consultants can keep up with how to migrate from version to version.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEafTkaCoPKRow/gARAs+yAKCyhzD0/y9GQIMwo6FYz/i1TTj3SACgtlP8
ghv9CBzskedeopIlbYGti4w=
=DIjM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Relaying observations
Posted by Geoff Longman <gl...@gmail.com>.
Something in your observations has struck a chord..
> 5. Perceived to be a "consultant's framework" in that it changes
> enough - and (back to the tooling) without tool support - that only
> consultants can keep up with how to migrate from version to version.
This is absolutely true and it goes way beyond Tapestry's wild
evolution path. Tapestry is now a framework built by constants and by
not choosing reasonable conventions and sticking to them Tapestry
panders to consultants. By that I mean consultants in the conventional
sense but also consutants in the sense of the guru guy everyone in the
company "consults" with about Tapestry as the guru knows more than
anyone else.
Here are observations I made working as that resident Tap guru in a
high pressure development group using T3:
There are too many ways to do things and people for the most part
don't care and continually ask why there these options exist. Or don't
ask 'cuz they stopped caring.
I was becoming like a folk story teller, explaining the options and
why they came to be. Sometimes I don't know why. So I stopped doing
that.
Not being a high paid consultant here there is no advantage to pumping
up my image by expounding on my vast knowledge of Tapestry. Everybody
knows that I know more about T than they do. They want that nugget of
info needed to solve the problem at hand and image pumping is seen as
waste of time.
As for T4 and migrating:
Not going to happen here. A huge investment has gone into the current
T3 apps. No funding is going to come for porting apps that work
perfectly well for no percieved, and immediate, advantage.
Plus there are aspects to T4 that I think also cause friction...
I know that having me as the only guru was considered a risk by the
powers that be. What if I bailed? The only other hire they had that
knew T before arriving punched out after 5 months. Turn over here is
not high but I expect it to rise as the industry picks up in town.
After a year they have 9-10 people proficient in Tapestry 3 and don't
want to repeat the growing pains we encountered previously when only 2
people in the room were comfortable with T. And that would happen if
there was a T4 port.
Hivemind is "yet another technology to learn" and when I described
that most could get by without using it the response was "Yes, but
that means only a few, probably just you, will know it and then we are
vulnerable if you leave"
We now have 5 large T3 products either in production or development.
Porting all at once is out of the question and that means some working
in T3 and some in T4 - not going to happen.
My 2 cents.
Geoff
--
The Spindle guy. http://spindle.sf.net
Blog: http://jroller.com/page/glongman
Other interests: http://www.squidoo.com/spaceelevator/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Relaying observations
Posted by Howard Lewis Ship <hl...@gmail.com>.
Those are good observations.
Building a system such as Tapestry and improving it for every release
is a challenge. In Tapestry's case, the inheritance imposition, and
the lack of a clear divider between internal/implementation and
public/api has been a growing problem from release to release.
Tapestry 5 aims to clear that up and, because of the nature of the
contract between the framework and the user code, may realistically
clear it up far, far into the future.
I also think that the new design will simplify the learning curve, and
I'm committed to building documentation and examples/tutorials as I
go.
Again, the things that cause minor-to-moderate compatibility problems
(between 3 and 4) can only be effectively fixed by introducing a
non-backwards compatible change (5).
In fact, many of their observations dovetail nicely with my plans for
5. For example, "too flexible" will be simplified by removing .page
and .jwc files (and just using annotations).
It's nice to know that a challenging, picky (in a good way) client
like this is also sold on Tapestry!
On 5/16/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I pondered the right way to relay the following and decided this might
> be the best. This is not meant to do anything other than relay
> information, but if you see a correlation between statements I've made
> and these observations there's a definite reason why.
>
> The following were comments and observations I was given as part of a
> postmortem on a project I just wrapped up. They are customer comments,
> but I was given permission to relay them directly to whomever I felt
> might want to know:
>
> Background: They are sold on Tapestry - 3. They will not move to 4
> unless there's a driving need due to monies expended to implement their
> current solution (they rolled their eyes at the mention of 5.0 stating
> the benefits didn't outweigh the costs) and lack of tooling. The
> "initial learning curve" was discounted as it was completely different
> from their previous framework and learning curves are everywhere -
> although I did point them to Kent's book and sold them on that (Thanks
> Kent!). The did feel this level of information should have been
> considered part of the overall tutorial/example documentation.
>
> Pros (for choosing Tapestry):
> 1. Tapestry allows separation of concerns
> 2. Component design allows different parts of the agency to have
> access to a library of components
> 3. Web interface designers do not need to know anything except HTML
> (conversely, Java developers do not need to know HTML)
> 4. Strong community support
> 5. An Apache project
>
> Cons with moving forward (to future Tapestry versions):
> 1. Codebase changes too radically between releases (this comment was
> made in discussions about 4.x and comments made about 5.0 - this brought
> up more conversations about "initial learning curve" with switching to a
> different framework having the same name)
> 2. Lack of documented reasons for change (they don't sharpen pencils
> without documented reasons - and before the jokes fly, yes - they do
> still use pencils :-))
> 3. Too many ways to do the same thing (too flexible: w/ regard to
> Annotations vs. XML in 4.x conversations)
> 4. Lack of first-class tooling support within the framework
> (discussions on Spindle - which they love in T3 [thanks Geoff] and its
> lack of support in T4)
> 5. Perceived to be a "consultant's framework" in that it changes
> enough - and (back to the tooling) without tool support - that only
> consultants can keep up with how to migrate from version to version.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFEafTkaCoPKRow/gARAs+yAKCyhzD0/y9GQIMwo6FYz/i1TTj3SACgtlP8
> ghv9CBzskedeopIlbYGti4w=
> =DIjM
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org