> I generally find that an ORM makes easy things easy and difficult things indescribably hard or impossible.
I agree, but raw sql makes the easy thing hard (or at least cumbersome), so the nice middle ground is to use hibernate for the easy things and sql for the hard things.
With respect, I just don't find SQL that difficult, especially for the simple things that an ORM does a nice job with. "select foo, bar, baz from quux where uuid = '8bd67f1e-6bb8-4ccb-8ad4-fa631b36ab8e'" is easy.
Re:How Hibernate Almost Ruined My Career
by Gaelan on Thursday February 16, 2017 @10:44PM
(#13665751)
> makes easy things easy and difficult things indescribably hard or impossible
I've found that nearly every abstraction does this in some form. In general, the easier the easy things are, the harder the hard things are. The trick is finding a good balance for your project.
Re:How Hibernate Almost Ruined My Career
by RhodesianHunter on Thursday February 16, 2017 @11:01PM
(#13665820)
"Welcome to Java …"
Maybe in giant non-tech company legacy systems, or written by Indian off shore teams.
These days with Java 8 there is almost none of that bull shit.
Welcome to Java …
I generally find that an ORM makes easy things easy and difficult things indescribably hard or impossible. Honestly, the relational model is great, and it's worth understanding well. Frankly, if you're a software developer and you can't learn SQL … you're not really a software developer.