News for hackers. Stuff that matters.
Re:A taste of CoreData – A graph framework by mpweiher on Tuesday February 20, 2018 @02:09AM (#16418374)
Since about 20003, I have made a bit of a career of removing CoreData and its predecessor EOF from applications.

Every time it has been a huge success in terms of simplicity, performance and reliability.

Replacing EOF happened in a feed-processing application[1]. We just processed everything in memory and persisted the incoming feed, which we wanted to do anyway for auditing. In that instance it wasn't so much a planned removal, but rather that we never came around to implementing the DB component.

Next up was a desktop application, Livescribe Desktop. It was using an atomic store, so there wasn't really any point to CoreData. Chucking it meant removing a lot of code and crash-sites.

For Wunderlist 3, we rewrote the storage layer to simply use a bunch of JSON files (our CTO used to shock people at conferences with that little nugget), and the "In-Process REST" ideas from [1]. So our persistence solution was essential [NSJSONSerialization dataWith...]. The day after we launched, I was shocked at the number of crash reports, but my colleagues informed me that they had 10x the amount the last time. With millions of users, you get into a lot of edge cases. Oh, ours was also the fastest of the clients.

Oh, I also gave a talk at UIKonf '17 about making a public transport data (sample) application 1000x faster by moving from CoreData/sqlite to a custom data representation.[2]

[1] https://link.springer.com/chapter/10.1007/978-1-4614-9299-3_...

[2] https://www.youtube.com/watch?v=kHG_zw75SjE&feature=youtu.be

Re:A taste of CoreData – A graph framework by yageek on Tuesday February 20, 2018 @05:35AM (#16419266)
The purpose of the post is just to provide some general information about the different concepts provided by CoreData. The framework first lacks of a clear documentation I would say. Regarding reliability, if the rules are respected, I would consider CoreData as a reliable framework.

Regarding speed, I would say that CoreData is far lower than other low level approach. It is up to the developer to estimate the needs in term of speed/performance.

The biggest advantage of CoreData, according to me, would be the integration with the UI libraries, but this is only my opinion :)

I guess you gave the same talk at appbuilders last year right?