3 ms·
Personal take after quite a few years of experience: ORMs are great for quick and easy prototyping. But in no way I would ever use another ORM in any applicati
by m_st 6y ago
Personal take after quite a few years of experience:
ORMs are great for quick and easy prototyping. But in no way I would ever use another ORM in any application again. Simple helpers like Dapper (C#/.NET) are fine. But nothing more than that.
Learn SQL and handle it yourself. You will be thankful sooner or later.
- chrischapman 6y agoI'm really not sure why this was downvoted. I completely subscribe to this opinion. Been a SQL coder since 1997 (C# since 2003) and had my run in with ORMs in the last decade. There is no way I'd voluntarily use an ORM. I just don't see the benefit.
- blacktriangle 6y agoFinally made an account to respond to this. I completely agree with your take on ORMs and learning SQL. One thing that people get confused with about CoreData is treating it like an ORM; it is not. CoreData is an object persistence framework more in line with object databases than relational databases. The ability to use SQLite is just an implementation detail. It's like how Datomic can use a SQL db as a datastore however does not present data relationally. When porting apps back and forth between Android and iOS, the biggest thing I miss on Android is CoreData. CoreData is exceptional at what it does and its a shame that more iOS education doesn't focus more on CoreData.
- rimliu 6y agoCoreData is not ORM.