I think that Java 6 adoption was much faster than 1.5 adoption. Compatibility is pretty good, but you get an immediate 30% performance gain.
Martijn On Tue, Dec 15, 2009 at 12:36 PM, Carl-Eric Menzel <cm.wic...@users.bitforce.com> wrote: > On Tue, 15 Dec 2009 11:44:23 +0100 > Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > >> I was going to propose a vote in that direction... as JDK 1.5 has been >> shelved... >> > > It'll be years until Java 1.6 is as common as 1.5 is now. There are many > organizations who have only just completed the move to 1.5. I think > going to a strict requirement for Java 1.6 would be a really bad idea, > especially since it does not offer as many significant new benefits as > 1.5 did. > > Offering 1.6-specific features in a separate jar would be a simple and > pretty good solution, I think. Stuff like the typesafe model would thus > be available for those who need it, without leaving anybody needlessly > stranded. > > Carl-Eric > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
