3 ms·
I used this, and it was a terrible ORM. NeXT did great software, NEXTSTEP and WebObjects were fantastic, but EOF was an exception. I’ve forgotten the details n
by adrianmsmith 8y ago
I used this, and it was a terrible ORM. NeXT did great software, NEXTSTEP and WebObjects were fantastic, but EOF was an exception.
I’ve forgotten the details now, but one thing was the naming. For example, who can guess what a “display group” is without looking it up? (Does it involve displaying things? A group of what?) Even the name “Enterprise Objects”, why should a database framework only be useful to enterprises?
- coldcode 8y agoI actually liked it, for its time it was great to point to a database and have it make a model. Not as useful for new dev though. Today its easy to see the flaws since you have other things to compare it to. But is Hibernate really any better, all I hear is the server guys complain about having to use it. ORM is hard but at the time EO was the best (which might have been because you got to use WO).
- adrianmsmith 8y agoI’m not sure it’s just bad in retrospect. I remember it being difficult to do simple things, and there were lots of ways you could trip yourself up. I wish I remembered more details.. I remember preferring Hibernate when I encountered it although I agree that’s far from ideal either and there’s plenty to justifiably complain about there. EJB Entity Beans were definitely worse than either, not supporting any kind of inheritance modeling, requiring altering many different files for a simple change like adding a field.