I'll have to say I looked at Lift, and although it was greatly improved since 1.0, it doesn't have the awesome separation of concerns that wicket does. Even in the tutorial, the markup and the templates leak into each other. Wicket's greatest asset was always IMO the fact that the HTML itself can be almost unmodified between designer and programmer (of course, usually it pays to create components).
I've made a couple of toy projects in Scala/Wicket, and the biggest pain was to get the collections and generics right. I don't much like the implicit conversions (anywhere, even boxing and unboxing end up doing weird stuff once in a while), so I always ended up having to do it by hand. It made life easier to keep using the Scala collections, and just convert it to Java collections in the Wicket Models, but once in a while it still messed me up... I would love to see a wicket api that used the Scala collections and made models use SModels or something like that. PS.: that's my opinion as a lurker... not a Wicket dev On Thu, Jan 6, 2011 at 12:19 PM, Jonathan Locke <jonathan.lo...@gmail.com>wrote: > > Not so sure that doing a simple fork of Wicket into Scala is such a great > idea. And at the end of the day you probably couldn't call it Wicket > without > Apache permission, which seems unlikely. But creating a Wicket-inspired > framework in Scala sounds like a good idea to me. Have you taken a look at > David Pollak's Lift project? > > Regarding Scala, I think it's a good sign that people are interested in > advancing the state of the art. And I think Martin and company have found > some of the problems that need solving and to their great credit done > something about them, even if only 0.4% of programmers are using Scala so > far. Unfortunately, I don't think a large or powerful or killer set of > features is what makes or breaks a language in terms of widespread > adoption. > And I *especially* don't think that economy of expression makes a language > "better", particularly where large teams are concerned. Clarity, precision > and simplicity are far more important than brevity and power. > > Jon > > "Less is more." > http://www.amazon.com/Coding-Software-Design-Process-ebook/dp/B0042X99SA/ > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Scala-Wicket-Help-and-Advice-tp3174601p3178126.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
