On 8/24/07, Vincenzo Vitale <[EMAIL PROTECTED]> wrote:
> Yes I see your point and you are absolutely right but please consider
> that a lot of companies (included mine) have been using Spring MVC for
> a long time and there are a lot of projects already in production
> using that technology and working fine with the IT infrastructure now
> available.

The easiest 'sell' is to look at the problems you had with frameworks
like Spring MVC. Some of us (including me) have actually been involved
in such frameworks before, and decided to go the Wicket route as it
solved actual problems. For me, the initial reason was simply the fact
that model 2 (Spring MVC is a model 2 framework) doesn't scale for
complexity. I had seen too many projects being bogged down by stacking
hack up hack (often involving ad-hoc session usage) to get things done
like wizards, tabs and pageable list. I saw all the money lost on the
fact that we could not create reusable components (so when we had a
similar search function in an app four times, the closest thing to
reuse would always be copy n paste), and after a few months of
developing, these projects got very very brittle due to all these
hacks and code duplication and lack of abstraction. Wicket has been a
ten fold improvement for me when it comes to scaling for complexity.

A secondary reason back then was the fact that I saw many guys just
out of university struggling with model 2. They just learned all these
nice things about object oriented programming, and here they were
procedurally programming in Java (as that is I believe what you do
when you use model 2 frameworks). I believe Wicket helped out a lot
here too, as I saw new programmers picking up web app development more
easily, and as a bonus learning a thing or too about OO programming as
well. The other side to this of course is that if you have people
coming from a PHP background for instance, they actually might find it
harder.

/end rant :)

Eelco

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to