Peter, I started answering, but as I worked through your message I found unfounded assumptions about my project, my experiences and about what I'm actually suggesting, which made me angry enough that that response would have been of little general interest and I scrapped it. Instead, I'm going to discuss basic principles, taking your use case just as the spark for a general line of thought.
What I have to say is that I'm seeing Jooq acquiring features, and I just hope that this isn't going to develop feature bloat. The problem with feature bloat is that features can interact. If you have N features, there's a potential for N(N-1) interactions, most of them usually unwanted. Even a one-liner change is a new feature; the problem isn't in the one-liner, it's in the ramifications elsewhere. Now you can say that Jooq is well-designed, and the list of actual interactions is small, and I'd agree with that - mostly; even the best library designer can't keep up with an arbitrary number of things to consider, and the quadratic behaviour will reach that point very quickly. Also, learners have to explore the full N(N-1) space to know which approach of using features is best - that's one of the reasons why learning a large, feature-rich library like Hibernate can easily take a year or more until you're finally reasonably sure about what to do and what not to do with it. The traditional technique do deal with that quadratic explosion is modularity. I.e. make class naming a separate tool, apart from and visibly independent of Jooq. That way, learners can take out naming issues as a potential problem, cutting down on the number of possibly unwanted interactions. Or, alternately, make the various features of Jooq visibly separate and independent. I'd be all for adding class naming under such a structure. At this time, however, I'm seeing a lot of stuff getting integrated into Jooq's core. Maybe that's just because I'm missing a lot; that's a very real possibility since I haven't had the opportunity to use Jooq for production yet. My instinctive gut feeling to all these extensions that are being proposed and integrated right now, however, is: "Oh dear I'll have to learn ALL THAT, that's going to be another Hibernate experience where I can't know what I'm actually doing, Jooq promised to be easy and in 1:1 correspondence with SQL but it's not picking up new features at an alarming rate, where is this whole thing headed??" I'm not taking that gut reaction as the real thing, but it is nourishing a growing concern. Regards, Jo TL;DR: I still think that bloating Jooq just to cover up for Maven's shortcomings is madness. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
