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

March 17th, 2017

Netflix to Replace Star Ratings With Thumbs Up/Down: mjtsai.com/blog/2017/03/1…

via IFTTT

Making an External Display a Monitor, Not a TV: mjtsai.com/blog/2017/03/1…

via IFTTT

@NSExceptional I realize that’s the current plan, but that doesn’t mean it will only be used for that purpose.

via Tweetbot for Mac in reply to NSExceptional

@ameaijou @jckarter @lapcatsoftware Exactly. Same with, say, NSKeyedArchiver. My point is that rewrite is happening.

via Tweetbot for Mac in reply to ameaijou

@jckarter @lapcatsoftware NSFileManager looks more like a rewrite than a wrapper to me: github.com/apple/swift-co…

via Tweetbot for Mac in reply to jckarter

@jckarter @lapcatsoftware Right, but in this case the rewrite is already happening. It’s just a question of whether you’ll use it.

via Tweetbot for Mac in reply to jckarter

@lapcatsoftware It was necessary to have different spellings, not necessary to have different implementations.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware Yep. There will probably never be more parity than there is now.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware But presumably the APIs will diverge unless they want to forever limit SwiftFoundation to what Objective-C can do.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware It could if they wanted to vend an Objective-C API.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware And I thought we were taking about implementations, not API.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware “Not all data types are toll-free bridged, even though their names might suggest that they are.” developer.apple.com/library/conten…

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware Agreed, but only because one appends “Ref”, and I’m not sure how this is relevant…

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware Maybe at some point they’ll re-unify by having the Objective-C version wrap the Swift.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware And it’s not as though the CF and NS stuff was fully unified, anyway. One has wrapped the other, switched. Duplicate imples.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware Yeah, not ideal. But if they really are serious about Swift, it *should* be used to write this stuff, not wrapping ObjC.

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware How would you introduce the parallel structs without removing the NS?

via Tweetbot for Mac in reply to lapcatsoftware

@lapcatsoftware Yes, but it’s better than having a totally separate solution for Swift on other platforms.

via Tweetbot for Mac in reply to lapcatsoftware