News for hackers. Stuff that matters.
Re:The Play Framework at LinkedIn by vorg on Thursday February 21, 2013 @07:54PM (#5261799)
> I wish they had gone with Groovy.

Play 2 stripped out all the Groovy code from Play 1. There must be a reason.

> Groovy 2.x offers pretty much all the benefits of static compilation and dynamic language features together

Groovy's dynamic compilation is reliable, but sloooooooooow. The static compilation added in Groovy 2 is much faster but still buggy e.g. http://stackoverflow.com/questions/14774709/groovy-2-1-0-wei... It was written by one developer, and first shipped in Grails only 2 months ago. And does Grails actually use any of Groovy's static compilation features? I haven't seen anywhere it's used: point me to somewhere in the Grails codebase if it does.

You don't get all the benefits of static compilation and dynamic compilation together, you can get bugfree (but sloooooooooow) code, or faster (but buggy) code.

Re:The Play Framework at LinkedIn by zmmmmm on Thursday February 21, 2013 @08:46PM (#5262000)
> Groovy's dynamic compilation is reliable, but sloooooooooow.

I guess you mean execution speed, not compilation? Compilation is fast enough I think. Execution certainly compares fine with other dynamic languages, at least, in my usage (and for some things it is much faster).

> The static compilation added in Groovy 2 is much faster but still buggy

The bug you mention is certainly bad, but it was addressed extremely quickly. Are there other examples?

> It was written by one developer, and first shipped in Grails only 2 months ago

A little misleading - static compilation has been in core Groovy for 9 months or so and is now supported by the core groovy team.

> And does Grails actually use any of Groovy's static compilation features?

I don't know, but it's not really relevant. I'm not advocating for Grails here, I'm advocating use of Groovy with Play. Part of the reason I want that is that I'm not extremely fond of Grails for various reasons.