I mostly agree with you that current tooling gets us pretty far, but there's a lot to be said for turning the most frequent "runtime" errors into "compile-time" errors, something that often requires special Tapestry awareness.
On 8/29/06, Konstantin Ignatyev <[EMAIL PROTECTED]> wrote:
My point is that in case of Tapestry/Wicket there is no need to worry much about tools, because existing ones provide pretty good environment to work within. Therefore focus on APIs and conventions seems very reasonable to me.
