Just read some of the features he proposes on his blog. He seems to make a big deal on getting the DI right with @InjectService. Maybe someone should tell him about @SpringBean? ;) I'm sure he does fancier things, though I doubt it's something you really need for the user interface. Furthermore: 'This is the theme for all of Tapestry 5: Simpler, easier, faster, more understandable, more powerful. Avoid XML. Improve productivity. Make the framework adapt to your classes and your methods, rather than the other way around.' ... So what's new/ different? :)
If someone can point out some really drastic improvements I'd certainly be interested to learn... And before this is getting to be a flamewar. No-one of the team has a big problem with Tapestry, though some are ex-Tapestry users. I still hope component oriented frameworks like Wicket, Echo, GWT, and Tapestry will eat up the model 2/ web mvc frameworks, cause imo that's where the real evil is. >8-| Eelco On 8/25/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > It's understandable that he gives a strong opinion to a direct attack > on his framework. He's probably as ill informed about Wicket as we are > on Tapestry 5 though. So what she should do is take a look at what he > is doing and see whether we can learn something from it. Unlikely > though as it'll still be the difference between an unmanaged framework > (Wicket) and a managed/ declarative one (Tapestry). That, together > with some of the other major differences, makes that we'll likely be > improving our frameworks in very different directions. > > Eelco > > > On 8/25/06, Francis Amanfo <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > I found this current post on Howard's blog. I quote it here: > > > > "Wicket has a nice community and a few nice ideas, but it does not compare > > to what I have planned for Tapestry 5. I believe Java is going to thrive at > > the high end and performance is going to be one of the differentiators from > > Ruby on Rails. In addition, the Wicket model can't address the kind of > > short-cycle development issues that will be part of Tapestry 5. I think > > Wicket is fairly broken in that it stores the component model inside the > > HttpSession. This has been a critical flaw for JSF as well, where they've > > realized that they don't have a proper approach to handling true > > scalability. Wicket is a neater, cleaner version of Tapestry 1.0 or maybe > > 2.0. I've said in the past that I found it quite unambitious for starting > > from scratch. I'm now working on Tapestry 5 which is quite ambitious." > > > > Either this man is jealous of the success and popularity of Wicket or he > > might have forgotten to take his pills before hitting his fingers on his > > keyboard. Go remind him to do so the next time at: > > > > http://www.blogger.com/comment.g?blogID=4110180&postID=115393199327621322 > > > > Regards > > ------------------------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, security? > > Get stuff done quickly with pre-integrated technology to make your job > > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > > _______________________________________________ > > Wicket-user mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > > > > > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
