3 ms·

Thanks for your reply! I don't agree that concurrency is a mess with Core Data, it has good support for this. Of course you need to be careful to get things rig

Thanks for your reply! I don't agree that concurrency is a mess with Core Data, it has good support for this. Of course you need to be careful to get things right, but this goes for whichever technology you are using. As for upgrading the app, if you are doing anything else than a lightweight migration you need to know what you are doing, but that problem doesn't at all go away if you roll your own database layer. I believe Core Data is actually of great help in solving those pretty complex problems.

bsaul 10y ago
The whole managed object context paradigm is clunky. It's meant to be a system of nestable sandboxes for performing discardable operations on the database, but when you start to mix concurrency inside, it becomes intractable. Reading the documentation on concurrency and managedobject context would make any people's eyes go blank (https://developer.apple.com/reference/coredata/nsmanagedobjectcontext https://developer.apple.com/reference/coredata/nsmanagedobje...). IMHO, i don't think that 80% of the people using core data understand the concept of managed object context properly. For example, i'm pretty sure everyone wonders what's going on when they try to reuse an object from a context in another and get weird behaviors. My main point isn't that one should recode a database manually, but that it's extremely rare to need that kind of system in a mobile app in the first place. Also i think that performing a set of sql query in an sqlite database is much much simpler than creating a correct process for a core data model migration.
- antonholmquist 10y ago
  Appreciate your thoughts on this! Core Data is far from trivial but can also be incredibly powerful. I actually think a lot of apps can benefit from the persistence and advanced notification system it offers.

3 ms·

Thanks for your reply! I don't agree that concurrency is a mess with Core Data, it has good support for this. Of course you need to be careful to get things rig

by antonholmquist 10y ago

bsaul 10y ago
The whole managed object context paradigm is clunky. It's meant to be a system of nestable sandboxes for performing discardable operations on the database, but when you start to mix concurrency inside, it becomes intractable. Reading the documentation on concurrency and managedobject context would make any people's eyes go blank (https://developer.apple.com/reference/coredata/nsmanagedobjectcontext https://developer.apple.com/reference/coredata/nsmanagedobje...). IMHO, i don't think that 80% of the people using core data understand the concept of managed object context properly. For example, i'm pretty sure everyone wonders what's going on when they try to reuse an object from a context in another and get weird behaviors. My main point isn't that one should recode a database manually, but that it's extremely rare to need that kind of system in a mobile app in the first place. Also i think that performing a set of sql query in an sqlite database is much much simpler than creating a correct process for a core data model migration.
- antonholmquist 10y ago
  Appreciate your thoughts on this! Core Data is far from trivial but can also be incredibly powerful. I actually think a lot of apps can benefit from the persistence and advanced notification system it offers.