4 ms·

>This will allow Swift developers, regardless of the platform on which they deploy their applications, to access these APIs for a common set of cryptographic op

• ajconway 7y ago
  Not too often, yet. But it could potentially become a more user-friendly alternative to Rust.
  • skohan 7y ago
    Swift seems to be evolving towards something which lives between Rust and Python.
    • monoideism 7y ago
      I'd say more like something between Rust and Scala, or Rust and Java. That's not a bad thing. I really like Swift.
      • monadic2 7y ago
        What rust features does it have?
        • favorited 7y ago
          To name a few: generics, pattern matching, memory safety by default (though not concurrent yet), no untyped-nil, the capability for C-like performance, deterministic memory management. Protocols are pretty similar to traits as well. Though the way all of those work is substantially different. Swift doesn't monomorphize generics like Rust does[0], for example. Swift doesn't have a concurrency story yet, so it is possible to have data races if you share data between threads. An ownership system[1] is in the works, but it is not complete yet. [0]https://www.reddit.com/r/rust/comments/7gkiie/implementing_swift_generics_video/dqkfkvh/ https://www.reddit.com/r/rust/comments/7gkiie/implementing_s... [1]https://github.com/apple/swift/blob/master/docs/OwnershipManifesto.md https://github.com/apple/swift/blob/master/docs/OwnershipMan...
          • monoideism 7y ago
            Good summary. Also algebraic data types, although that typically accompanies the pattern matching you mentioned. Protocols are fairly close to traits, and I much prefer that approach (and Scala's traits), to traditional OOP.
          • skohan 7y ago
            > Swift doesn't monomorphize generics like Rust does[0], for example. Swift can monomorphize generics, but it doesn't do so by default. Normally this is left up to the compiler, but it's possible to force monomorphization using inlining attributes.
      • skohan 7y ago
        Me too. I think "higher level rust" is a very good and useful niche. Sometimes convenience is more important than performance.
• xkemp 7y ago
  There's some momentum for Swift on servers. It has at least the potential for C-like performance, although the last time I tried it wasn't quite there yet. Might also be useful for having a second stack that works on the client as well as the server. Then, there's a big push for Swift+Tensorflow and other ML. The hope here appears to be the ability to implement "automatic differentiation" (or was it "integration"?). I don't remember enough math to fully understand, let alone try to explain that. But I can attest that even without being implemented, it has the power to get ML people salivating.
  • Smoosh 7y ago
    An example for zOS as a server: https://www.kitura.io/ https://www.kitura.io/
    • ChrisMarshallNY 7y ago
      Kimura is cool, but not sure what its future is: https://www.theregister.co.uk/2019/12/17/swift_ibm_pulls_back_open_source_priorities/ https://www.theregister.co.uk/2019/12/17/swift_ibm_pulls_bac...
      • ChrisMarshallNY 7y ago
        Whoops. Autocorrect typo. "Kitura." (I have "Kimura" in my dictionary).
    • pjmlp 7y ago
      IBM is no longer interested in Kitura and Swift. https://www.infoq.com/news/2020/01/ibm-stop-work-swift-server/ https://www.infoq.com/news/2020/01/ibm-stop-work-swift-serve...
• ryuukk_ 7y ago
  every companies i worked with got their backend running on linux using Swift why Swift? because you can then share code base with your mobile apps ;)