Conversation

Interested in complex and concurrent Core Data setups? We just added a chapter about this to our early access book.

objc.io

Core Data

Core Data best practices by example, from persistency to multithreading and syncing.

I would love a chapter about "designing an app with core data without passing mutable objects everywhere" 😛

oh ask

about that we’ve got that worked out pretty well basically you just construct a huge wall around core data

Yeah I did that on the Pebble app. It was so much boilerplate though and I only had two entities...

interested. we do that. at the end you just use CD for persistence. at this point is worth it?

Replying to

often not, no. it depends on your data set’s requirements.

3:47 PM · Sep 8, 2015Tweetbot for Mac

Replying to

for me the problem is that to really profit CD I don’t think you can build a wall in front of it. but then

polluting your codebase with it… risky risky. i’m at that point that I wold rather not use it at all xD

Show replies