Just to roughly endorse this approach; in one of our applications we already
had an in-house JSON parsing/writing API, which isn’t going to be very feature
complete but majors in being very fast and efficient and meets the use-cases
we’ve hit so far. My first instinct in integrating Groovy was t
A couple other notes here, is that...
1) Groovy, with its modules, doesn't intend to replace the kitchen-sinks of
the categories (Groovy JSON won't do more than Jackson), and tries to stick
to the smallest useful feature-set that will make Groovy developers
productive,
2) and regarding the sortin
Hi Paul,
thanks for clearing that up :-)
(I did not refer to this evident water-under-the-bridge problem (which I
had never heard of before) in my post, but just wanted to confirm that
Groovy plays very well with & can easily be used to enhance established
Java frameworks, and people therefor
