On Tue, Sep 28, 2010 at 2:41 PM, Chris Colman <chr...@stepaheadsoftware.com>wrote:
> The 'popularity' test is very vague but I understand it's purpose, they > want to ensure that they use products that are widely used and have an > active user community: which is very true of Wicket. Does anyone have > some numbers on this? Like how many Wicket developers there are, or how > many websites are Wicket driven? Is there a page on the wicket website > that contains a list of the companies/products that use Wicket - if not, > should we add one? > There's no way to quantify this metric. And don't let them use the false "job search" *technique* to think that they know. There are too many reasons that you don't get accurate numbers from this. There is a page on the wiki that lists a fraction of the sites using Wicket. https://cwiki.apache.org/WICKET/websites-based-on-wicket.html Ultimately, I would direct them away from this. It doesn't *actually* matter. What matters is this (in roughly this order): 1. Pick a technology that fits your needs 2. Pick a technology that is productive 3. Pick a technology that, when you hit a stumbling block, you can get help with. You've already demonstrated one and two. Number three can be demonstrated by asking them to subscribe to the dev and users lists here for a week. Then dare them to find an open source web framework that has better community support. I haven't seen one. -- Jeremy Thomerson http://www.wickettraining.com
