[LeoNatan25]

> a language developed entirely by and for writing Apple ecosystem products

So, apparently you didn't even read the article, as it is explicitly stated that this was not the intention or direction of Swift.

> Among other things, there's no way to disable objective-c interop, even though it complicates the language and feels like someone merged smalltalk, C++, and ML—not a pretty combination. But—literally the only reason you'd enable that would be to work with Cocoa/UIKit.

Swift on Linux does not use any of the ObjC runtime features that are used on Apple platforms.

[wulfklaue]

> So, apparently you didn't even read the article, as it is explicitly stated that this was not the intention or direction of Swift.

It might actually help that there is a real commitment in that direction. The issue being that it was IBM that mostly pushed for changes in foundation and without there initial blue socket support, even the most basic tasks did not even succeed.

Let alone the none existing windows support. It may not have been Chris his intention but one now ex-employee intention does not mean a lot when the company determines the direction after his release.

[LeoNatan25]

While I agree that the state of the Foundation frameworks should be better, I would not go as far as saying Apple is disinterested. Just lower priority. Also, seeing how Swift has evolved, the community has a very large impact on the direct Swift is taking.