I like those. Lets hold them against the unfair criteria again (this is really fun):
- Developer team scalability: Nice, this is indeed something large companies need and/or struggle with. Who has never had revision 1285 of struts-config.xml? And many big companies like splitting up work over technical lines instead of functional lines (java vs. html). - Reusability: I have unfortunately never seen a big slow company that cared about this. Please tell me if you saw some. - Maintainability: I have not seen many big slow companies that cared about this deeply. Furthermore, the big companies I worked at 'maintainability' is usually associated with 'maintenance': keeping big databases and J2EE application clusters alive. I am hesitating whether this one should be on the list. Erik. Eelco Hillenius schreef: > I'm missing my favorites :) > > - Scales very well for development. Whether you're working in a team > of 2 people or 20, you'll have all the possibilities of breaking > functionality down in smaller pieces. Let your developers works on > whole pages, or just (reusable) panels, or even on highly specialized > components. Also, using separate HTML/ CSS people to mock up pages > works really well with Wicket (*). > - Reusability. Over multiple projects or in just one project: > reusability is great, and actually is exactly the same thing as what > makes OO great. You abstract a 'problem' with its data and behavior, > and make it available for users to utilize in multiple situations. See > related rant on custom components here: > http://chillenious.wordpress.com/2006/05/12/a-word-about-custom-components/ > - Maintainability. Same rules as OO apply. Changes are more local, > making refactoring easier. Reusability makes that you'll have less > copy 'n paste code. Etc. > > Eelco > > * There have been a bunch of discussions where some wind bags said > that this is something no-one actually does. But they are wrong, > because I've seen it work, and some of the projects I know of > currently are doing it with great success as well. > > > On 9/26/06, Erik van Oosten <[EMAIL PROTECTED]> wrote: > >> Okay, so we've got: >> >> Irrefutable arguments for using wicket in big slow companies: >> >> * Very small learning curve. >> Comment: Agreed. But I still think you need at least one more >> experienced Wicket developers for more advanced things like >> manipulating html generated by other components. Of course, books >> like 'Pro Wicket' help a lot but are not for every programmer. >> * Natural programming paradigm familiar to Java developers >> Comment: Changed that to _Java_ developers. >> * Excellent feedback messages of the framework when something goes >> wrong. >> * Robustness, no weird or unexpected behavior. >> >> * Limited knowledge required of web technologies (HTML, javascript) >> and still do advanced stuff in a fraction of the time it takes you >> with other frameworks (just consider e.g. something as tabs and >> paging). >> Comment: I am not sure so sure about this one. Do you mean that >> you only need limited knowledge of HTML and Javascript? And what >> do you mean by 'advanced stuff'? >> >> May I add: >> >> * Excellent clustering support. >> Rationale: even though you can discuss about this to death (as on >> the thread on JavaLobby), I think we agree that Wicket currently >> has sufficient knobs to make this is a problem solved. >> * Excellent mailing list support. >> >> I also thought about: * Good support for modern web pages (AJAX), while >> being compatible with older browsers. But this one is I am afraid not >> good enough. For example FireFox 1.0 is not supported. >> >> Anyone else? >> >> Thanks Erik, >> Erik. >> >> -- >> Erik van Oosten >> http://www.day-to-day-stuff.blogspot.com/ >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys -- and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Wicket-user mailing list >> Wicket-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wicket-user >> >> > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user