> I am still pretty upset and maybe even somewhat traumatized about all the previous times they've fucked me over in scenarios like this. It starts out great and then gets ruined.
I haven't done much development using Apple frameworks. I'm curious, where has this happened to you before?
The threading model is poorly written. It is very hard to setup. Keeping legacy model data and writing transformers for said data is painful (person upgrades the app, schema changed). There are lots of crashes we've seen at scale. Also, its often really poorly performant, and the IO is completely synchronous. Most apps do not need this wrapper around SQLite (or SQLite at all) and in fact should just use simple file writes. Easier to debug, maintain, and scale, with fewer bugs.
I haven't done much development using Apple frameworks. I'm curious, where has this happened to you before?