That makes sense. I'd expected it to work more like Java, where the wrapping happens on-demand (though still at compile time), rather than universally. But no great loss either way. I'll trade a bit of performance for the ease of use.

Just last night I was reading that everything is an object in Groovy. If you declare something as a primitive, Groovy will silently wrap it in a class such as Long, Integer, etc.

Over lunch I stuck Groovy 1.6 in there. It knocked about 20% off the execution time versus 1.5.7 for the specific test I was doing. Brought the fully optimized version down to 1:20, so still not fast enough to break the minute barrier. On the same machine, the unoptimized Java takes right about 110ms.

No, still running 1.5. I created the project back in early February and haven't upgraded since the release. I know it's supposed to be significantly faster, but haven't given it a whirl yet. The Eclipse plugin is still serving 1.5.7, and I haven't dug into figure out how to set it up with a different JAR.

Cool that cfscript is faster, who woulda thunk it? =]