On a somewhat similar note, sometimes the code I write is not for a
specific product, it may be for a library or component I want to reuse
across any of my company's projects. Or I may be writing for a specific
project with the thought that I might push it into such a library or
component later, or I may have no idea when I'm writing it and the thought
to do so may come later. Or, in the imperfect real world, a piece of such
code may get reused by being copied to another project.
The context where decisions in writing code get made ("hey, I could use
JOOQ for this!") and decisions at a much higher level ("What database do we
use? How do we sell this and how much can we charge?") are often highly
disconnected, and it is often highly desirable that they remain
disconnected. You are making it such that the former decisions cannot be
made without consideration of and visibility into the latter. For many of
us, this is a strong motivator for the decision not to use JOOQ as the only
safe decision.
To put it another way, the set of people unable to use JOOQ is not simply
those who answer "no" to the two questions "can we use a non-commercial
database" and "can my sales model support the cost of this licence." There
is a vast grey area of different shades of "I don't know", "maybe today but
I can't swear to tomorrow" which also equates to "can't afford to tie my
code to JOOQ". I hope you don't underestimate the complexities that go into
creating that grey area.
--
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.
