4 ms·

The problem used to be the language. Java used to be extremely rigid in the way it forced the developer to write classes everywhere, factories and what not. Thi

The problem used to be the language. Java used to be extremely rigid in the way it forced the developer to write classes everywhere, factories and what not. This and the std lib API as well which was quite verbose. And let's not get started on Java EE which was the recommended way to develop Java applications. All of that are certainly part of the language. 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.

cobbzilla 6y ago
> 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.