I know your trying to make a point about extra work for no gain, however I can't see why I'd bother to create a list and never put anything inside it (maybe and edge case or two)... And I couldn't think of any case where I'm not going to use a component or model I add to a page... Why would I even bother to implement it at all?
- Brill Pappin -----Original Message----- From: Igor Vaynberg [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2008 11:25 PM To: users@wicket.apache.org Subject: Re: AW: users, please give us your opinion: what is your take on generics with Wicket i guess my question is: if you have a list and you are never going to put anything inside it, do you think a generic type is still useful? there are plenty of usecases where component's default model slot is not used, so why do we have to generify it? even if the mix is 50/50 that means 50% is complete noise... verbousity might not be wicket's problem, but using a verbose api sucks. generics fit for collections because there is never a case where you would want a collection without putting/getting something out of it. -igor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
