Hello I worked on a JSF project last year. This year I worked on a wicket project. Both were approximately the same size and complexity.
Granted. You learn from experience. The second time around you do something (or something quite similar), you do it much, much better. AND I had previous experience with JSF (Nearly two years worth) and not with Wicket. AND I had good expertise on HTML/JavaScript, which I could leverage on Wicket, but not on JSF. It took half the time. I truly believe that JSF was meant to sell tools to developers, whereas wicket seems more "from programmer to programmer".... you know... pragmatic. I am yet to see how the new application performs on production. But, as far as I see, I am about to become a Wicket advocate. I think I am seeing the light. On Fri, Dec 12, 2008 at 5:55 AM, Martin Sachs <[email protected]> wrote: > > I'm looking for a little comparison of the development-time for Applications > in Wicket against other Technologies. > > > I think the development with Wicket is two times faster than Struts. But > what are your experiences on JSF, Rails/Grails, SpringMVC/SpringWebFlow. > > Anyone you know the development-time from experience ? > > > (P.S.: The applications must use AJAX and many custom components or tags in > JSP, not just a hello world sample) > -- > View this message in context: > http://www.nabble.com/What-is-your-experience-on-the-time-of-development---tp20971605p20971605.html > Sent from the Wicket - User mailing list archive at Nabble.com. > -- Marcelo Morales --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
