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.
