The site appears to be down. Here is the cached version: http://webcache.googleusercontent.com/search?q=cache:rOWlIup...
Inside Swift
21–25 of 25 posts
Re: Inside Swift
#22What's _really_ going to be interesting going forward is whether Apple introduces new features in the runtime that are only available to Swift code, or whether it starts making change to the runtime that favour Swift over Objective-C—and that's probably going to tell us when the latter is to be considered a legacy language.
Re: Inside Swift
#23The site appears to be down. Here is the cached version: http://webcache.googleusercontent.com/search?q=cache:rOWlIup...
Re: Inside Swift
#24Earlier quoted context omitted.
Grandparent was probably out of line (saurik's comment provided useful information that went beyond me too-ism), but I can understand why one would be wary. Its hard to keep up with who is legit, and there has been a lot of me tooism lately. At least no one has started writing any horrible books on Swift yet.
I am not certain I understand the problem with "me too-ism". Hacker News is a discussion forum: if I go into the comments on a post, what I am expecting to find is more information about the topic written by other people... if someone links to a related project or an article with more detail, I don't see how that's a problem. In this case, I am actually featured prominently in this article--it isn't just that I know…
Re: Inside Swift
#25Earlier quoted context omitted.
I am not certain I understand the problem with "me too-ism". Hacker News is a discussion forum: if I go into the comments on a post, what I am expecting to find is more information about the topic written by other people... if someone links to a related project or an article with more detail, I don't see how that's a problem. In this case, I am actually featured prominently in this article--it isn't just that I know…
Pleas not I wasn't accusing you of me too-ism, I realize what I wrote was ambiguous.