> it still requires conditional compilation to import either Darwin or Glibc, instead of Foundation Well, swift-corelibs-foundation has made a lot of progress,

> it still requires conditional compilation to import either Darwin or Glibc, instead of Foundation Well, swift-corelibs-foundation has made a lot of progress, and strictly speaking, to a certain point you don't actually want to hide some of the implementation details from the developer. This isn't Java - natively calling out to C is a thing that Swift can and will do. > I don't see any Windows there. Look harder. Swift for Windows: https://github.com/compnerd/windows-swift https://github.com/compnerd/windows-swift > no Playgrounds Swift Playgrounds: https://github.com/save-buffer/swift-repl https://github.com/save-buffer/swift-repl > no IDE official VSCode work: https://github.com/apple/sourcekit-lsp/ https://github.com/apple/sourcekit-lsp/ + https://github.com/apple/sourcekit-lsp/tree/master/Editors/vscode https://github.com/apple/sourcekit-lsp/tree/master/Editors/v... > and so on Do tell. What other concerns do you have? You seem deeply misinformed. While Swift may not yet have an ecosystem outside of Apple, it is factually incorrect to say that it is not usable outside of it.