Exactly!
Also those organizations, which want to stay with very old and normally
unsupported software versions usually budget for extra support. Java 1.5
is not supported normally any more by Sun, so they will be bying Sun
"retirement" support anyway or running all their business systems on
unsupported software. Similarly old version wicket support can be
provided as extra service. I am sure there will be organizations willing
to sell it, if there will be enough demand for it.
So, I am for letting the developers make the choice ...
On 12/22/2009 11:19 AM, Erik van Oosten wrote:
I am afraid you miss the most important argument: whether the core
developer *want* to develop with Java 5. Its mostly their free time
and love they put in Wicket, we should never forget that. (Of course
they probably want to have users, etc. But in the end it is their
decision.)
Regards,
Erik.
Neil Curzon wrote:
-1 to JDK 1.6
The possibility of excluding even 1% of potential users for the
negligible
benefit of using 1.6-specific features would be a bad decision. 1.5 is
simply the right jdk to be developing frameworks in for now.
Pro 1.6 crowd: Understand that the argument is not that anybody's
organization *should* stay with JDK 1.5, but that some organizations
*will*
stay at 1.5 regardless of whether you think they should be up to
date. If
the jump from 1.5 to 1.6 was as big as the jump from 1.4 to 1.5, I
would be
firmly in the pro-1.6 camp, but the benefits just aren't worth the
costs.
