Re: Estimated number of developers in the Wicket community
On Wed, Feb 9, 2011 at 2:10 PM, Bruno Borges wrote: > > Does anyone have an update over this? > > It seems the website > > http://people.apache.org/~coar/mlists.html#wicket.apache.org > > does not show anymore the Wicket dashboard. > > I'm looking for a number of active members on the mailing list (also, > number > of messages). > I wrote the person that generated that and asked about it since it appears that it is way out of date and is obviously missing many lists. -- Jeremy Thomerson http://wickettraining.com *Need a CMS for Wicket? Use Brix! http://brixcms.org*
RE: Estimated number of developers in the Wicket community
Does anyone have an update over this? It seems the website http://people.apache.org/~coar/mlists.html#wicket.apache.org does not show anymore the Wicket dashboard. I'm looking for a number of active members on the mailing list (also, number of messages). -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Estimated-number-of-developers-in-the-Wicket-community-tp2717811p3298036.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Estimated number of developers in the Wicket community
> http://people.apache.org/~coar/mlists.html#wicket.apache.org Wow, looks like Wicket is one of the most popular projects of the Apache Software Foundation! > > Maarten > > On Tue, Sep 28, 2010 at 10:49 PM, Frank Silbermann < > frank.silberm...@fedex.com> wrote: > > > Chris Colman Tue, Sep 28, 2010 at 2:41 > > PM: > > >> > > >> 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? ... > > > > Jeremy Thomerson Tue, Sep 28, 2010 at 2:53 > > PM: > > > There's no way to quantify this metric. ... 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 > > > > That page would help, but a mere fraction of the sites might give the > > wrong idea. > > > > Jeremy: > > > 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. > > > > Not really. He has yet to demonstrated that Wicket meets their > > popularity needs. In lieu of having them subscribe to the message list, > > maybe he can direct them to the archived messages on Nabble. > > > > Is there a way a program could extract a count of the participants (i.e. > > distinct e-mail addresses) in the archived mailing list for a variety of > > time periods (to show growth in user base)? > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Estimated number of developers in the Wicket community
> Is there a way a program could extract a count of the participants (i.e. > distinct e-mail addresses) in the archived mailing list for a variety of > time periods (to show growth in user base)? That sounds like a good idea. It looks like they're moving towards Wicket: I built a sample app and they were impressed with the very small amount of code required to build the UI and the fact that the UI/Model interface is direct, simple Java method invocation on the POJO model objects is an extremely compelling productivity advantage that's hard to resist. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Estimated number of developers in the Wicket community
http://people.apache.org/~coar/mlists.html#wicket.apache.org Maarten On Tue, Sep 28, 2010 at 10:49 PM, Frank Silbermann < frank.silberm...@fedex.com> wrote: > Chris Colman Tue, Sep 28, 2010 at 2:41 > PM: > >> > >> 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? ... > > Jeremy Thomerson Tue, Sep 28, 2010 at 2:53 > PM: > > There's no way to quantify this metric. ... 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 > > That page would help, but a mere fraction of the sites might give the > wrong idea. > > Jeremy: > > 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. > > Not really. He has yet to demonstrated that Wicket meets their > popularity needs. In lieu of having them subscribe to the message list, > maybe he can direct them to the archived messages on Nabble. > > Is there a way a program could extract a count of the participants (i.e. > distinct e-mail addresses) in the archived mailing list for a variety of > time periods (to show growth in user base)? > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
RE: Estimated number of developers in the Wicket community
Chris Colman Tue, Sep 28, 2010 at 2:41 PM: >> >> 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? ... Jeremy Thomerson Tue, Sep 28, 2010 at 2:53 PM: > There's no way to quantify this metric. ... 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 That page would help, but a mere fraction of the sites might give the wrong idea. Jeremy: > 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. Not really. He has yet to demonstrated that Wicket meets their popularity needs. In lieu of having them subscribe to the message list, maybe he can direct them to the archived messages on Nabble. Is there a way a program could extract a count of the participants (i.e. distinct e-mail addresses) in the archived mailing list for a variety of time periods (to show growth in user base)? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Estimated number of developers in the Wicket community
A couple that come to mind, but aren't on that list are: www.springer.com - publisher mobile.walmart.com - retailer Scott On Tue, Sep 28, 2010 at 12:53 PM, Jeremy Thomerson wrote: > On Tue, Sep 28, 2010 at 2:41 PM, Chris Colman > 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 > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Estimated number of developers in the Wicket community
On Tue, Sep 28, 2010 at 2:41 PM, Chris Colman 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
Estimated number of developers in the Wicket community
Hi fellow Wicketers, I've been using Wicket for about 4 years now and, as predicted, I'm addicted to the productivity I get by being able to perform unconstrained object oriented design and development at both the model and user interface layers. My company has been contracted by a very large multinational company to build a website for a government body. Naturally I want to use Wicket as the code is so optimal and so development will be much more productive but some at the company are pushing for GWT even though they have zero Java experience and obviously no experience in either Wicket or GWT. To counter the problem of doing all the ugly RPC normally required by GWT to bind UI elements with domain objects they are proposing to use a third party tool that manages some of that 'object marshalling RPC madness" through some XML configuration and some specific interface implementations. It sounds like the third party tool is there to 'workaround' the 'hack' that is normally required when binding UIs to models when coding with GWT. My philosophy is "if you don't use a hack in the first place then you don't need to work around the hack". I showed them Wicket and I built a sample app and they were impressed with the small amount of code required to build UIs that interact with underlying domain models but they seem to be desiring the GWT + third party solution because they need to be able to satisfy unit test/verification and non specific 'popularity' criteria to their client. Given that a significant part of the third party tool is commercial/closed source, I'm not sure how they will perform the unit test/verification testing. 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? Any other points I should bring to the customer's attention to help them in their decision?