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

March 7th, 2008

@schwa Yeah, I'm not saying the apps shouldn't do it; I'm saying it would be easier and smaller, too, if it were built-in.

via Twitterrific in reply to schwa

So instead of Apple using space for one copy of NSXML in the OS, now every app's going to include a copy of its own wrapper?

via Twitterrific

@huperniketes Mostly memory overhead, probably. My point is that NSArchiver lets *you* choose the tradeoff between being efficient and lazy.

via Twitterrific in reply to Huperniketes

@huperniketes NSArchiver handles byte ordering for you. Field order independence is just a convenience. Use versioning or store a dict.

via Twitterrific in reply to Huperniketes

@danielpunkass NSArchiver can do all the same things, but much faster, in less memory, and with smaller files/blobs.

via Twitterrific in reply to danielpunkass

I still prefer NSArchiver to NSKeyedArchiver.

via Twitterrific

Not that I don't like the SDK, and I can't be specific due to NDA, but these APIs are very limited compared to what built-in apps can do.

via Twitterrific