Things are winding down on Tapestry for the moment. The
code is stabilizing and I'm working just on bug fixes,
documentation and some improvements to the JBE.

I'm also planning my next framework: Sabertooth. It's yet
another approach to accessing database data. It borrows
some ideas from NeXT/Apple EOF and J2EE Entity EJBs but is
architected to work well in a web application environment.

I once read a quite from someone on the Quake team who
said "all computer science is caching" at that's very true.

Just released Tapestry
0.2.7.. I'm definately getting to the point where I
have to ask the question: How does it end? ... in
other words, when is it finished, when does it start to
really bloat?

Of course, bloat really started at least a month ago;
some of the new components, ValidatingTextField, FieldLabel
and Script, are far more than the "really basic" set of
components I initially envisioned ... but I want Tapestry
applications to really differentiate themselves and the
text field components, at the least, are important for that.