On Wed, Sep 1, 2010 at 9:20 PM, Ben Tilford <bentilf...@gmail.com> wrote: > It depends how much time you want to take to learn the language. With Groovy > you don't have to know anything but Java to start with and can learn more > about the language as needed or interested. Scala is nothing like Java or > any other language. > > The issues Groovy had with inner classes almost all been fixed since the > Stack Overflow posting so as long as your using 1.7.x you should be good > there.
I actually used 1.7.0 the moment it was released because until then inner classes in Groovy were not supported at all. You can look at the code / pom.xml and see for yourself. I didn't bother trying any later versions though. - Peter > > Whats better is going to come down to what your comfortable with, willing > to learn, and if squeezing a couple milliseconds of performance matters or > not. > > On Wed, Sep 1, 2010 at 11:38 AM, James Carman > <ja...@carmanconsulting.com>wrote: > >> On Wed, Sep 1, 2010 at 11:34 AM, Peter Thomas <ptrtho...@gmail.com> wrote: >> > >> > Done as an experiment a long time ago though, in a big hurry. >> > Personally, I didn't like the combination of Groovy + Wicket, for >> > reasons mentioned in the "Scala + Wicket" StackOverflow link below. >> > Others may have different opinions though. >> > >> >> So, you would recommend using Scala as opposed to Groovy, then? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
