Hacker News new | past | comments | ask | show | jobs | submit login

I've never understood why this isn't a more common approach.

JDBC is an old standard, but it's also perfectly functional. The addition of try-with-resources has made it fairly terse once you know your way around it.

And half the time with an ORM, you are trying to figure out what SQL is ultimately being generated and tweaking to get what you want. So, cut that middle layer out and just write what you want.




Yes, tried that once and every other developer in my team complained.

I would stick with JDBC if I were the only developer.


If I have to use something like an ORM, then I push for JDBI or JOOQ. I've not ran into too much pushback using raw jdbc at my current employer though.


Yeah, forgot about JDBI.

Developers are lazy and just throw hibernate everywhere.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: