10 ms·
Edit: After a little more reading, everything he's posting about seems to be Java specific. It would have been nice for him to point that out somewhere. After
by epochwolf 17y ago
Edit: After a little more reading, everything he's posting about seems to be Java specific. It would have been nice for him to point that out somewhere.
After reading the ORM article, I've come to realize this guy is using ORMs to completely ignore the SQL Layer. Also, I don't see any references to any ORM except Hibernate. A single datapoint isn't enough information to draw these conclusions about all orms, just Hibernate.
Coming from Ruby on Rails (and having used NHibernate for a project), I see this guy as an idiot. I use ActiveRecord to skip writing full sql for every statement, not to ignore sql completely. I check the generated queries, I only load the fields I need on high traffic pages, and I dip into raw SQL when I need it. I'll admit to being lazy with my edit screens but they aren't loaded nearly as much as other pages. And when I hit a bottle neck, I will do whatever incantation (SQL) to the database is required to fix the problem.