RE: [Hibernate-devel] SQL Server 2000 questions

[Anton v. S. <an...@ap...>]

> But yeah, support for instance variable access never went in so
> far, simply because it seemed like it would support a "worse"
> coding style. Now I'm sounding real indecisive, huh? :)

When in doubt, procrastinate?  :)

To add a decision factor: if it could be added as a feature without any
cost, maybe some people would find that useful (although not me).  But even
if it only takes an hour of your time to implement, there are other costs:
documenting it, explaining why it shouldn't really be used, adding choices
which the user needs to understand and take into consideration.  Choice is
good if it provides important flexibility, but in this case it seems like it
would fall more on the side of gratuitous bloat.

BTW, I realize my argument may seem overly impassioned for an arguably minor
issue, and if you add the feature anyway, I won't really mind.  But when I
said "don't give up your principles so easily", I was thinking of one of the
features which attracted me to Hibernate in the first place: it seems to
have almost everything I need, and very little I don't, and it works the way
I expect it to.  I don't get the same feeling when I use EJB frameworks, for
example - which is why I avoid them when I can.  Limiting user choice can be
a good thing...

Anton