Do I remember correctly that the original target was that Wicket 2.0 would be released before 2007? But now to be realistic considering previous projections, the date looks more like late 2007?
Yeah, we're way over our planning :). Due to many things, including starting incubation and building in many more features than we first thought off, but also - last but not least - because we decide to back port a couple of the most important 2.0 features to 1.3 so that the projects that were/ are on 1.2 have a reasonably easy transition path (just a couple of breaks) while enjoying some major new features that we at first only planned for 2.0. So the time line for 2.0 got less important. Another factor is that it takes much longer than we thought to write Wicket In Action, and we want to keep that in sync with 2.0. I'd say half way 2007 should be realistic. We plan to put 1.3 in maintenance mode pretty quickly once it is out, after which we'll focus on 2.0. Keep in mind that most of 2.0 (at least in my opinion!) has been beta ready for months, even more so because we backported and subsequently tested many of it's features. So at this point, it wouldn't be much more than making an official release. There are some areas to be worked on, but not that many.
Makes me a little nervous that Tapestry can completely turn around their code base, pick up lots of Wicket's formerly distinguishing checklist features, and do it all before Wicket does even a lite rewrite ala 2.0 much less a serious rewrite like maybe 3.0 would be. Hopefully I'm just being paranoid.
That's apples and pears really. We're less official about new features as we're typically quick to incorporate them, but I'm pretty sure that we've moved *a lot* faster in the last in the 2.5 years of our existence than our dear competitors. Not that it matters much though. The end of the day what matters is what is on your plate.
Tapestry 5 is a totally new code base for the groundbreaking Tapestry framework.
Those improvements are improvements for Tapestry and are not relevant for Wicket. It's good for them they made drastic improvements and I hope it works out for them well. However, the two frameworks are based on very different assumptions and therefore - no matter what optimizations - they will provide a different programming model. So... they keeping tweaking theirs, we keep tweaking ours and in the end of the day you'll have choice :) Eelco
