News for hackers. Stuff that matters.
Re:JOOQ: an alternative approach to traditional ORMs by eropple on Monday January 11, 2016 @02:26PM (#10882608)
> Its an extremely well maintained and documented library.

I find its documentation coverage to be good but its quality to be lacking, being mostly written by non-native English speakers. Which is fine, if there are good examples and tests to use--but jOOQ actually deleted unit tests from the open-source release of the library (declaring them "an enterprise feature") to remove the easiest and best way to investigate the library, as well as the only unambiguous documentation the project has. ("Ask a question on our Google Group" was suggested with a straight face. Because in 2015, it's better to wait on an email than look at code, I guess.)

Re:JOOQ: an alternative approach to traditional ORMs by vtman2002 on Wednesday January 13, 2016 @08:57PM (#10899146)
that is shady. bit it looks like they're still there in the git history: https://github.com/jOOQ/jOOQ/tree/fc7afb40760246153da4a2334c...

even the stuff that has been xxxed out: https://github.com/jOOQ/jOOQ/blob/63717b517fccf475089648ca3c... and it's still under the APL.

Re:JOOQ: an alternative approach to traditional ORMs by eropple on Thursday January 14, 2016 @02:42AM (#10900085)
Yup. I ended up using the last version of them I could when I had to use jOOQ, but I didn't feel at all comfortable endorsing the behavior going forward.