5 ms·

not true https://github.com/tensorflow/swift/blob/master/Installation.md https://github.com/tensorflow/swift/blob/master/Installation...

pjmlp 7y ago
Having a package available for a specific OS doesn't mean it is usable, specially when it still requires conditional compilation to import either Darwin or Glibc, instead of Foundation. And I don't see any Windows there. Then there is the whole set of libraries that only compile on Apple platforms, no IDE, no Playgrounds and so on.
- throwlaplace 7y ago
  >specially when it still requires conditional compilation to import either Darwin or Glibc, instead of Foundation. you don't need to compile from source - binaries are distributed (if you actually read my link instead of assuming it was just github source you would see that). >And I don't see any Windows there. yes they're aware of this and it's being worked on >Then there is the whole set of libraries that only compile on Apple platforms, no IDE, no Playgrounds and so on. you're moving goal posts in order to be able to have an axe to grind. your comment was >For Mac OS only apparently. the fact that there's a runtime that runs on linux shows that that was incorrect. >set of libraries that only compile on Apple platforms i don't know what you're talking about here - s4tf libraries compile on all platforms e.g. https://github.com/eaplatanios/swift-rl https://github.com/eaplatanios/swift-rl >no IDE, no Playgrounds and so on. i don't see how xcode being developed by apple (not the s4tf team) has anything to do with whether s4tf is multiplatform.
  - pjmlp 7y ago
    Not moving goalposts at all. Swift is only usable in Apple OSes. Making a tiny subject of its ecosystem available outside of Apple platform doesn't make it usable for something that pretends to replace Python ecosystem on data science.
- ynx 7y ago
  > 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.

pjmlp 7y ago

Having a package available for a specific OS doesn't mean it is usable, specially when it still requires conditional compilation to import either Darwin or Glibc, instead of Foundation. And I don't see any Windows there. Then there is the whole set of libraries that only compile on Apple platforms, no IDE, no Playgrounds and so on.

throwlaplace 7y ago
>specially when it still requires conditional compilation to import either Darwin or Glibc, instead of Foundation. you don't need to compile from source - binaries are distributed (if you actually read my link instead of assuming it was just github source you would see that). >And I don't see any Windows there. yes they're aware of this and it's being worked on >Then there is the whole set of libraries that only compile on Apple platforms, no IDE, no Playgrounds and so on. you're moving goal posts in order to be able to have an axe to grind. your comment was >For Mac OS only apparently. the fact that there's a runtime that runs on linux shows that that was incorrect. >set of libraries that only compile on Apple platforms i don't know what you're talking about here - s4tf libraries compile on all platforms e.g. https://github.com/eaplatanios/swift-rl https://github.com/eaplatanios/swift-rl >no IDE, no Playgrounds and so on. i don't see how xcode being developed by apple (not the s4tf team) has anything to do with whether s4tf is multiplatform.
- pjmlp 7y ago
  Not moving goalposts at all. Swift is only usable in Apple OSes. Making a tiny subject of its ecosystem available outside of Apple platform doesn't make it usable for something that pretends to replace Python ecosystem on data science.
ynx 7y ago
> 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.