On Jun 13, 2017, at 23:54 , Glen Huang <[email protected]> wrote: > > what do you use instead of Core Data?
I ended up writing my own object graph framework. Interestingly, many parts of the implementation fell naturally into the same mechanisms Core Data uses (such as having client-facing and primitive versions of the same property.) Unfortunately, because it manipulates the class metadata at runtime, this framework is also fatally stuck in the Obj-C world, and I haven’t found an alternative approach for Swift. > Also I don't quite get the "can’t afford the therapy afterwards" part I used Core Data for a major project — years ago, around the time Leopard came out — and it was incredibly painful: 6 months of utter misery. It’s one of those magical Apple technology solutions that’s clever as all get-out, but totally inscrutable. Core Data doesn’t fulfill a design that’s documented somewhere, its design is … whatever its implementation does. Sometimes that makes sense, sometimes it doesn’t. I think Core Data is great for Apple’s internal use (e.g. in older versions of iTunes/iPhoto/Photos), and perhaps feasible for 3rd party developers if you’re dealing with tens of thousands of objects (for performance reasons). It may have become more usable over the years, but I promised myself I’d never go near it again. _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
