The below is an off-site archive of all tweets posted by @mjtsai ever

October 15th, 2013

@nriley I was using the side. Do you think there’s a benefit to deleting and re-adding a finger, rather than just adding it again?

via Tweetbot for Mac in reply to nriley

@mpweiher Right. Core Data is probably at least an order of magnitude slower, and its objects are heavier.

via Tweetbot for Mac in reply to mpweiher

@nriley Yeah, at this point I routinely fail with four different fingers in a row. It doesn’t like lotion, either, so I’m stuck.

via Tweetbot for Mac in reply to nriley

@atomicbird Right. You have to bring the objects into memory to modify them; then, until you save, you get slow in-memory filtering.

via Tweetbot for Mac in reply to atomicbird

@drewmccormack And an SQLite index on disk can be way faster than Core Data’s in-memory predicate filtering.

via Tweetbot for Mac in reply to drewmccormack

@drewmccormack Not for batch updates like Brent’s “corner case.”

via Tweetbot for Mac in reply to drewmccormack

@drewmccormack Would be fun to see those massive schemas as NSManagedObjectModels.

via Tweetbot for Mac in reply to drewmccormack

@drewmccormack It’s possibly convenient, but not high perf, to bring all objects into RAM before operating on them.

via Tweetbot for Mac in reply to drewmccormack

@mikeabdullah @drewmccormack It still doesn’t work properly with NSDocument, right?

via Tweetbot for Mac in reply to mikeabdullah

@drewmccormack You think that, absent the history, Core Data would make a better word processing/spreadsheet document format than XML?

via Tweetbot for Mac in reply to drewmccormack

@milend @drewmccormack Exactly. Core Data is not bad, but it can paint you into a corner. The article way oversells it.

via Tweetbot for Mac in reply to milend

@drewmccormack Notes and iBooks don’t use it for syncing, either. Nor for storing large amounts of data. No iWork or iLife apps (AFAIK).

via Tweetbot for Mac in reply to drewmccormack

@mikeabdullah They do, but basically as a cache layer. Not for primary data storage or for syncing.

via Tweetbot for Mac in reply to mikeabdullah

@drewmccormack Article says that you should use Core Data because Apple uses it for apps, and Apple knows best. But where are said apps?

via Tweetbot for Mac in reply to drewmccormack

@drewmccormack Aperture used to use Core Data, switched away from it, and got faster.

via Tweetbot for Mac in reply to drewmccormack

@drewmccormack They use SQLite and other syncing infrastructure for, from what I can tell, are good reasons.

via Tweetbot for Mac in reply to drewmccormack

@mikeabdullah @apontious Docs say that -stringWithFormat: uses the “canonical locale” and that %@ calls -descriptionWithLocale:.

via Tweetbot for Mac in reply to mikeabdullah

@drdrang I must have been thinking of Amazon. Seems like such a basic feature. I guess you could add a unique campaign to each link…

via Tweetbot for Mac in reply to drdrang

@mpweiher @drewmccormack For evidence, you can look at what Apple does vs says. Are Mail, Aperture, Contacts sync, etc. all “corner cases”?

via Tweetbot for Mac in reply to mpweiher

Finding Apple’s new PHG affiliate reporting inscrutable. Is there really no way to see which apps/songs were clicked on, or from where?

via Tweetbot for Mac

@willco007 It’s still not even documented how various APIs behave in the sandbox, and this is still changing from version to version.

via Tweetbot for Mac in reply to willco007