Lets not forget the stats we're all aware of (or should be) that 80% of resources in software development are in maintenance... If I'm looking at my ROI, then my developers can type a few extra words in order to reduce that resource load.
And lets face it; it *all* comes down to maintenance (and the cost of), despite effort on the initial development. One thing that means for me, is generics... Just like TDD, it reduces the issue count (among other things). - Brill Pappin -----Original Message----- From: Martijn Dashorst [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2008 11:47 AM To: users@wicket.apache.org Subject: Re: users, please give us your opinion: what is your take on generics with Wicket Question is, how many of those users are core committers. Not everybody is a generics wizz you know, nor has the need to become one. Most users want to just build web apps in a clean, self-documenting API that doesn't put too much burden upon them - conceptually and number of characters to type, read and understand. Martijn On Mon, Jun 2, 2008 at 5:28 PM, Matej Knopp <[EMAIL PROTECTED]> wrote: > On Mon, Jun 2, 2008 at 5:22 PM, Jan Kriesten <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >>> I'm not sure I like where this discussion is going. I don't see >>> anyone having any particular objections against current state. >> >> @matej_k: >> >> ugh - you should count again... if I counted right, most of the >> responses yet prefer 'Component' /not/ being touched by generics. > > Question is, how many of those users actually use generified wicket on > day-to-day basis. > > -Matej > >> >>> +1, I agree. I think this discussion might be counter-productive if >>> folks who aren't using the generified versions are voting. >> >> @jwcarman: >> >> There is an issue with generics on components which is leading into a >> big mess - and as far as I can see, many objections are especially on >> that topic! It might not be Wicket's fault, though, it might be a >> language problem (i.e. Java's to blame). >> >> But IMHO putting generics on Component is a bad design, since it per >> se touches all of Wicket's Components without urgent need. >> Boilerplate over and over. If I look at my components and libraries >> (and yes, i have tried out >> 1.4!) - I have at most 30% of my components containing a Model! >> >> Best regards, --- Jan. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
