click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis M. J. Yerger" <>
Subject RE: [DISCUSS] Retirement into the Attic
Date Fri, 20 Sep 2013 15:07:20 GMT
Earlier this year I joked about the inactivity of Click being due to its being the perfect
framework. The comments so far on this discussion illustrate why I made that joke. Click just
works if you're a Java-centric developer who prefers to rapidly build a Web application with
minimal HTML. However, I do believe Click has room for growth, and I would hate to see it
retired at this point. I would be on board to continue the project, but I would need some
guidance on the overall process. I hope others will join in too.

Subject: RE: [DISCUSS] Retirement into the Attic
Date: Fri, 20 Sep 2013 12:08:58 +1030

I agree with Mikhail at several points - Click works - its very basic, very usable and very
stable - and that is why it rocks. If I were after a bloatware web-framework there are endless
number of examples out there, but what I - and most probably the majority of us here - really
need is a simple and usable one.
Moreover, as it was pointed out well in several emails that the stalled development is probably
originated from the fact that the framework does what it needs to do without any hiccups.
I strongly believe that what works well and serve it purposes with high efficiency should
not be compromised, or made to work "even better". 
Last but not least, should the framework goes to the attic, it wouldn't stop me using it in
the future. On the other hand I am sure that should the Attic will be the final decision -
which is not exactly the best way to promote any product - there will be several developers
out there, who will need an easy solution for web development and they will just start making
their very own simplistic stateless framework based on servlets and perhaps some open-source
template engine, which will essentially pretty similar to Apache Click. Correct me if I am
wrong, but is this really what ASF is likely to want from developers, reinventing the wheel?
Probably not...

Subject: Re: [DISCUSS] Retirement into the Attic
Date: Thu, 19 Sep 2013 11:39:14 +0400

Dear Chris,

I use Click for several apps for years. I started with 2.3.0 and now I use.... hm..... 2.3.0

There are number of reasons that makes this project different.

1. Not so many bugfixes as usual. Because it's JUST WORKS. Apps based on Click are very stable.
2. Lack of activity in discussions, no documentation updates, no new examples. Because it's
REALLY SIMPLE. Look at Cheat Sheet pdf. It's the only documentation I read years ago. And
that's enough.
3. No releases. Because it's PERFECT. It's minimal stateless framework for developers who
needs minimal stateless framework. 

>From the other side.
It's really no difference for me, for example, is the project retired or not. (Sorry) Because
framework is perfect and just works. Next project I will start I will use Click. I will not
go to Apache site for newest version. I will not use Wicket, for example. I already have one,
that fits my needs. So, I think Attic is not the place for Click. Attic is the place for projects
with no future. Click is the project with no further development. Maybe it's different things.
For the first 2-5 years.

Kind regards,

Mikhail Peresypkin

Среда, 18 сентября 2013, 11:00 -07:00 от Chris Mattmann <>:






			Dear Apache Click PMC,

Based on your board report for September 2013, I'm

starting a thread here on the dev list for retirement

of Apache Click.

If you have any opinions, for or against retirement,

please make them known. If discussion doesn't really

urge against retirement in the next week I'll call

an official [VOTE] thread with resolution to retire

the project to the Attic.

Thank you for your attention to this matter.



(on behalf of the Apache Board)



View raw message