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

Recent tweets

@nriley For me, it does remember the scroll position per mailbox, but it reset each mailbox to the top once.

via Tweetbot for Mac in reply to nriley

@dnanian As I recall it was more like 300 MB total under Mavericks.

via Tweetbot for Mac in reply to dnanian

@dnanian Yosemite Mail is using about 489 MB of RAM for me, plus 280 MB for Mail Web Content, without a single message open for viewing.

via Tweetbot for Mac in reply to dnanian

@nuoji Incidentally, this also means that a hypothetical second implementation of the language would need to do all the same optimizations…

via Tweetbot for Mac in reply to nuoji

@nuoji Seems like you have to hope that the compiler never regresses and also that you can figure out what it's doing in pathological cases.

via Tweetbot for Mac in reply to nuoji

@nuoji Yes, that is the part that worries me. The compiler will get better, but there will always be things it can’t figure out.

via Tweetbot for Mac in reply to nuoji

@nuoji I guess this is what happens when you move functionality from the libraries into the language.

via Tweetbot for Mac in reply to nuoji

@nuoji Agreed. Do you think this is fixable?

via Tweetbot for Mac in reply to nuoji

@nuoji ObjC only copies when you say, and even then sometimes it's a no-op. Swift copies all the time, implicitly—and, again, often a no-op.

via Tweetbot for Mac in reply to nuoji

@nuoji Tricky implementations of NSData and NSString to link to other immutable objects when you split/join instead of copying data.

via Tweetbot for Mac in reply to nuoji

@nuoji Right. BTW, my understanding is that this sort of thing was once a (lesser) issue in ObjC as well.

via Tweetbot for Mac in reply to nuoji

@nuoji But ObjC is *more* explicit because you send different messages to immutable vs. mutable arrays.

via Tweetbot for Mac in reply to nuoji

@nuoji Aren't "var" and "inout" just different ways of spelling "mutable"? That's explicit.

via Tweetbot for Mac in reply to nuoji

@nuoji Yes, agreed about the perf being more hidden. I thought you were talking about "explicit" when reading the code.

via Tweetbot for Mac in reply to nuoji

@nuoji Yeah, one thing I've noticed is that it seems to be harder to read other people's Swift code than other people's Objective-C.

via Tweetbot for Mac in reply to nuoji

@nuoji Why do you say "not explicit"? Because the "var" may be textually far away?

via Tweetbot for Mac in reply to nuoji

@nuoji Yep. To me, the questions are 1. How much does the perf difference usually matter, and 2. Is there an escape hatch when it bites you.

via Tweetbot for Mac in reply to nuoji

@leebennett Doesn't it need more modern Bluetooth now?

via Tweetbot for Mac in reply to leebennett

So nice to be able to AirDrop files from my Mac to iPad.

via Tweetbot for Mac

Goodbye red progress bar stop lights.

via Tweetbot for Mac