tag:blogger.com,1999:blog-4110180.post6597652506748703577..comments2025-07-21T06:33:41.604-07:00Comments on Tapestry Central: Tapestry 5.2 leaves the gateHoward Lewis Shiphttp://www.blogger.com/profile/04486596490758986709noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4110180.post-9012815325906542432010-08-20T03:11:23.996-07:002010-08-20T03:11:23.996-07:00To my mind this is an example of one of the great ...To my mind this is an example of one of the great benefits of Tapestry compared to Spring, as I become more familiar with Spring. Spring offers many different ways of achieving goals, it therefor hints and guides less. The choices must depend on the integration task to hand. There will be a negotiation between skills, preferences and demands of the task. Flexibility here is good. But building an application - pretty well any application I think, not just the very client side focused ones that Tapestry excels in, really needs many hints and guides, if you don't want to create long lists of essential features yourself. Here one needs knowledge and consistency, a clear voice. This is what Tapestry has with Howard and the T community.<br />Howard has just introduced a fundamental change to how Tapestry solves the problem of the balance between memory usage and processing speed in a high usage site.<br />I may be quite wrong, but my understanding is that to do this sort of architectural change in Spring (MVC) would be very difficult. And to have that solution tested and adopted who knows how much more so?<br />Howard, thank you.Anonymoushttps://www.blogger.com/profile/14276724887861380619noreply@blogger.com