> Remember how hard and verbose it was to hydrate records from a DB result and turn them into Java objects with pure JDBC? The language certainly was at fault.

> Remember how hard and verbose it was to hydrate records from a DB result and turn them into Java objects with pure JDBC? The language certainly was at fault. I don't blame the language for this. It wasn't that hard to read/write objects using JDBC (it did usually create a lot of boilerplate) Please name a major programming language that has built-in ORM features -- a library is the best place for this sort of stuff. For Java this was J2EE/EJB (stupidly over-engineered) and Hibernate/JPA (decent if you avoid the footguns). For Ruby you have ActiveRecord, Python has Django and SQLAlchemy, etc.