4 ms·
I find the lack of ORM a feature in a web framework. Personally, I find them frustrating and an extra layer of abstraction that just gets in my way. Then again,
by mbreese 13y ago
I find the lack of ORM a feature in a web framework. Personally, I find them frustrating and an extra layer of abstraction that just gets in my way. Then again, I also don't mind writing queries. I usually end up using my own lightweight set of helper functions to manage queries, regardless of the language.
I still have Hibernate flashbacks from back in the day.
- masklinn 13y ago> I find the lack of ORM a feature in a web framework. There's quite a lot of stuff between "write raw SQL queries" and "full-blown ORM". http://docs.sqlalchemy.org/en/latest/core/tutorial.html http://docs.sqlalchemy.org/en/latest/core/tutorial.html for instance.
- boomlinde 13y agoI don't think that the argument is that ORMs are bad, but that it shouldn't necessarily fall into the scope of a web framework. I think you could reasonably argue that the primary task of a web framework is to be a meaningful abstraction layer over http requests and http responses, but on the other hand I can also see why someone would disagree. In some sense you could make the same argument against template rendering systems. Personally, I work a lot with a database setup that is managed primarily through REST and JSON-RPC interfaces, which makes a framework that lacks ORM a perfect fit, and I'd rather use something like Flask than something that sets me up with an ORM library whether I need it or not.