4 ms·
ORM are frameworks that exist mainly as a way to avoid writing and maintaining thousands of lines of boilerplate. Like most frameworks (i.e. packages that forc
by pytester 8y ago
ORM are frameworks that exist mainly as a way to avoid writing and maintaining thousands of lines of boilerplate.
Like most frameworks (i.e. packages that force you to write your code to conform to their patterns) a really good one confers a massive boost in productivity while a really bad one is horrifying to work - it fails in bizarre unexplainable ways and straitjackets your development.
IME, passionate rejection of ORMs predominantly comes from people who have been scarred by experience with really bad ORMs.
- ken 8y agoBlaming it all in “really bad ORMs” without naming any sounds suspect to me. Can you name some good ones?
- l33tman 8y agoDjango's ORM has always served me well, it handles migrations and I've had almost zero SQL-hacks that needed to be done.
- pytester 8y agoFor example JPOX was an ORM that almost put me off the entire idea. It was horrendous. Recently I've used Django ORM and SQLAlchemy - both are warty but generally decent and better than not using any ORM. This is somewhat language dependent - certain language qualities inhibit the creation of decent ORMs (e.g. it's not really possible to create a decent ORM in golang due to its design).