It makes you much more credible if you understand what you are talking about. You should read Tapestry's documentation before posting such a blog.
First of all, if you would spend 5 minutes learning Tapestry you would come across the "static structure, dynamic behavior" principle. Tapestry is not "rescanning templates and building DOM of the page before each rendering". All the page instances are singletons, which are smart enough to care for multithreading aspects. So, your expectation on efficiency is naive. If you want to speak about performance, create two similar apps with both technologies and measure the results. Show me the results, but please don't come up with something like "All in all it’s hard to expect Tapestry to be fast in production.". Also your statements on Tapestry's IoC, mixins, template inheritance and annotation-based approach are sweet and naive as you don't provide any arguments. These features are why Tapestry users love the framework. Nice try, but not professional. On Mon, Mar 14, 2011 at 1:34 AM, AlexSerov <[email protected]>wrote: > Tapestry framework by its ideas seems to be the most close framework to > HybridJava. > > Comparison of HybridJava and Tapestry: > http://hybridjava.blogspot.com/2011/03/hybridjava-vs-tapestry.html > > It would be nice to know everyone's opinion. > > HybridJava team. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/How-about-a-5-2-5-tp3414983p3555809.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Best regards, Igor Drobiazko http://tapestry5.de
