@leebennett That’s what I’m suggesting.
@argon I’m not when/how the encryption works, but the Facebook binary that iTunes downloaded to my Mac was not encrypted.
Lots of good Swift stuff in Xcode 7 beta 6.
@grynspan Yeah, I never quite understood the old system. Always found myself hardcoding latest version since didn't have access to constant.
@danielpunkass Future Daniel will thank you.
@grynspan Yeah, that’s what I use if the other version says it’s at least 10.10. Much more readable.
@gte It doesn’t solve the same problem. There’s a reason why even Lisp has a formatting micro language even though it has great quoting.
@rob_rix So it doesn't work if f takes an array instead of a SequenceType?
@rosyna Interesting that they added hash ivar for NSIndexPath. NSStringDrawing is a category so not sure what you are referring to there.
@rob_rix How can you do that if the sequence you receive is not final?
@rob_rix Yes, that is nice.
@rob_rix Wonder how often that is. I would think you’re usually passed in a collection and don’t know its type.
@rob_rix Right, I meant how NSFastEnumeration was designed to avoid message sends.
@rob_rix that slow or that the batching isn’t that worth it.
@rob_rix Yeah, just seems like an odd omission given the focus on performance. Seems like conclusion is either that message sending was not
@rosyna So, again, this is not (yet) an actual performance improvement resulting from Objective-C 2.
@rob_rix So no batching.
@rosyna But it didn’t break compatibility, and in fact NSEnumerator conforms to NSFastEnumeration (though probably not very fast).
Is there any optimization like NSFastEnumeration (batch fetching, detecting mutations) in Swift? SequenceType doesn’t seem to do that.
@rosyna So why are they still using it now that we have Objective-C 2?
@rosyna I kind of doubt removing old ivars from view classes makes up for slowing down every ivar access with extra indirection.
@rosyna Non-fragile is great for other reasons, but if we're talking about optimization…
@rosyna Compiler support, yes. But I thought we were talking about breaking backward compatibility.
@rosyna Why wouldn't fast enumeration have been possible before? Were there really a lot of unused ivars removed?
@rosyna That's a good one.
@mpweiher So when is your book coming out? :-)
@landonfuller Could LINQ work well in Xcode without special support (just Swift auto-complete)?
@landonfuller Right. Do you see Apple making Swift-only APIs any time soon? Or could a third-party LINQ gain traction?
@landonfuller LINQ looks great. Lots of issues with Core Data, but it does have traction.
@landonfuller Not sure what your “it’s” refers to. But I agree that it’s a good thing to move beyond OO as the solution to everything.
@mergesort Looks like they did. Thanks!
@leebennett To me, Schmitz wasn’t saying that; he was saying that the ads will be there even with payment.
@marczak Yeah, I have no idea whether this is a good move. Will be interesting to watch what happens.
@marczak On Page’s motivations or on whether this is good for shareholders?
@soryu2 :) I only added it a few weeks ago. Not sure I like it there. May move to the sidebar.
@soryu2 Thanks for your support. Were you expecting it to say “donate”?
@warwick Do you sell maintenance for your own work or for others’? Maybe the latter is easier?
@steveharris And then want a refund from the MAS because they unintentionally overpaid.
@steveharris I wonder how many people will not initially know about the direct version because you aren’t allowed to mention it.
@iljawascoding The docs say it has been KVO-compliant since 10.6.
@OvercastFM Would be nice to be able to sort a playlist by when I most recently listed to the episode, so I can easily finish what started.