The inside scoop on what's happening with Tapestry ... from the creator of the Apache Tapestry framework. Plus all the normal, random thoughts on coding and technology.
Friday, July 30, 2010
Choosing the Right Web Framework
Thank you Google Alerts, for pointing out this article on choosing a Java web framework. It's over a year old, but I think the things that make Tapestry special have only gotten stronger in the intervening time.
I would especially recommend this article for students. Because 3 out of 5 criteria the author uses are those of a sophomore: Popularity, Community and abundance of killed trees.
@Alex It's an impossible task to quantify deeply nuanced information such as quality, elegance, performance, complexity, and so forth, so give him a break!
If you stuck to the quantifiables, we'd all be using Struts until the end of time. And EJBs.
@Howard Your amendment to the criteria list looks fair. But serious things are difficult to evaluate, while such thing as the number (and size) of books is pretty easy. So he started with an easy end. Many so did and did they move on?
BTW regarding books. Say, take two technologies of approximately equal power. One needs 700 pages to be explained but another - only 50. Which one is more elegant, simple and giving faster running sites?
If you do want to postpone the end of you time and not to indeed die of overusing Struts see HybridJava and tell us what you think.
Please note that this is not a support forum for Tapestry. Requests for help will be deleted. Please subscribe to the Tapestry user mailing list if you are in need of support, or contact me directly for professional (for pay) support.
Spammers: Don't bother. I delete your comments and it's a waste of time for both of us. 垃圾邮件发送者：不要打扰。我删除您的评论和它的时间对我们双方的浪费
I would especially recommend this article for students. Because 3 out of 5 criteria the author uses are those of a sophomore:
ReplyDeletePopularity, Community and abundance of killed trees.
@Alex It's an impossible task to quantify deeply nuanced information such as quality, elegance, performance, complexity, and so forth, so give him a break!
ReplyDeleteIf you stuck to the quantifiables, we'd all be using Struts until the end of time. And EJBs.
@Howard Your amendment to the criteria list looks fair. But serious things are difficult to evaluate, while such thing as the number (and size) of books is pretty easy. So he started with an easy end. Many so did and did they move on?
ReplyDeleteBTW regarding books. Say, take two technologies of approximately equal power. One needs 700 pages to be explained but another - only 50. Which one is more elegant, simple and giving faster running sites?
If you do want to postpone the end of you time and not to indeed die of overusing Struts see HybridJava and tell us what you think.