Thiago, No need to follow this up. You're not going to get anywhere. "Everything is simple to the man who doesn't have to do it." When other frameworks do half as much as Tapestry, then we can start performance and productivity comparisons.
On Tue, Mar 15, 2011 at 4:04 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Tue, 15 Mar 2011 00:46:18 -0300, AlexSerov <[email protected]> > wrote: > >> "At runtime, Tapestry parses the documents and only checks for >> wellformedness". >> So either Tapestry parses the documents at run-time or the Tapestry >> site is awfully wrong. > > Tapestry parses the templates once, at run time, but just parses again when > the template is changed, not for every render. > >> Usually rendering means rendering at run-time. What this text describes >> literary is that at run-time: >> 1) components render out DOM (tree of nodes) > > Correct. > >> 2) DOM is visited recursively with streaming HTML to the client >> (client is waiting for HTML, not for DOM). > > Incorrect. Tapestry rendering uses a queue, not recursion: "Rendering of > components in Tapestry 5 is based on a state machine and a queue (instead of > the tail recursion used in Tapestry 4)." > http://tapestry.apache.org/component-rendering.html > >> I often insist on measuring of results in such a situation. >> Unfortunately I have same much reasons to ask you to do the same. But >> in general I agree. I even have a small set of very small tests on >> HybridJava site that I suggest everybody to implement. I am afraid >> that implementing them with Tapestry may be a waist of time, > > Why would it be a waste of time? If you want to prove that your framework is > fast, write the performance tests. If we think there's something that could > be implemented in a better way, we'll tell how. > >> but if you agree to try to implement some of my tests (for instance >> "Components") using Tapestry than I may promise to implement a test of >> your choice in HybridJava provided it will be not much more complex than >> my test. > > There is at least once person which compared Tapestry's performance with > other framework (in this case, Struts 1) and it turned out that T5 was > faster, specially in more complex situations. > >> User's love may be an argument for commercial success, but not for >> scientific discussion. >> There are many users for instance that admire heroin. > > If you said Struts instead of heroin your words would be taken way more > seriously. > >> By the way - one of the features mentioned above is if fact "not >> recommended" by Tapestry site ... > > Which one? Template inheritance? It's as recommended as class inheritance in > Java: it's not recommended to abuse it, but there are scenarios in which > their use is recommended. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
